SBL-DAT-00306: Searching is not allowed.

Applies to:

Siebel CRM - Version: 8.0.0.6 [20423] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

If a task is defined to display email offers, and the Verify and Preview button is used, the Email Marking Server (Siebel Email Sending Daemon) is used to display the template in a new window. However after this the Next button in the task causes the following error to occur:

Searching Is Not Allowed (SBL-DAT-00306)

Cause

Product Defect. 12-1YQ378R raised.

Solution

Use of TBUI for this functionality is not recommended as there is no solution for the defect currently.

References

BUG:12-1YQ378R - SEARCHING IS NOT ALLOWED (SBL-DAT-00306) MESSAGE IN TBUI

Applies to:

Siebel Tools - Version: 7.5.3.15 [16279] - Release: V7
Information in this document applies to any platform.

Symptoms

Using Java.DataBean API to query Virtual Business Components like “User Preferences” the following error is returned:

buscomp.clearToQuery(...) throws siebel exception.

25621958Searching is not allowed.(SBL-DAT-00306)Unknown

Cause

Performing additional tests verified that performing similar script on Siebel Application the following errors where seen in the log files, but they were not thrown in the UI.

SBL-DAT-00306: Searching is not allowed.
SBL-DAT-00315: Sorting operations are not available.
SBL-DAT-00315: Sorting operations are not available.

In JavaDataBean it seems that error is caught by catch(SiebelException).

Solution

To workaround this behavior I would suggest you to create a Business Service in siebel application to perform the required query on "User Preferences" UI and invoke the created Business Service in JavaDataBean to retrieve the required information.

For more information on how to invoke the Business Service from JavaDataBean you can refer to Bookshelf> transports and Interfaces: Siebel eBusiness Application Integration Volume III > Integrating with Java >
About the JDB Business Service API

Customer has also verified that by not invoking buscomp.clearToQuery(...) the error was not triggered.

Applies to:

Siebel System Software - Version: 7.8.2.2 SIA [19219] - Release: V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2.2 [19219] Life Sci
Database: Oracle 10.1.0.2
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Professional

This document was previously published as Siebel SR 38-3361188081.

Symptoms

SBL-DAT-00306, SBL-EAI-04376

Customer is testing a web service through a Visual Basic .NET application as the consumer, following :-

How To Use HTTP Session Mode for Stateful Inbound Web Service Integration (with Example in VB.Net) (Doc ID 477749.1)

An integration object was created for the Enterprise Admin Business Object and a Business Service based on CSSEAIDataSyncService class, to allow for query of Enterprise information from a monitoring program.

However, following error is reported :-

Method 'SetSearchSpec' of business component 'Enterprise Server' (integration component 'Enterprise Server') returned the following error:
"Searching is not allowed.(SBL-DAT-00306)"(SBL-EAI-04376)

Note, the BC "Enterprise Server" accepts search operations as by instantiating Siebel through COM.

Cause

This error is raised if an attempt is made call method ‘SetSearchSpec’ or ‘SetSearchExpr’ on Business Component ‘Enterprise Server’ (as is the case when attempting to query via the CSSEAIDataSyncService class).

Solution

As an alternative, it was suggested to write a cusom Business Service, which could extract the required data from the ‘Server Admin’ Business Object, and return these either as output properties, or an integration object instance. Once the Business Service is correctly returning the required data, it can be exposed as a web service, to allow the external application to invoke it.

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-1395583251.

Goal

- We want to limit the View Links available on the home pages based on the language (not just translate view links, but filter them by language).
- We tried adding search spec "Language Code=Language()" to the Public and Private View Link and the applet Public and Private View Link List Applet and this did not work.

In both these cases we get an error in the Siebel.log file saying
ObjMgrBusCompLog Warning 2 0 2004-07-15 14:01:04 (buscomp.cpp (11953)) SBL-DAT-00306: Searching is not allowed.

- We also changed the Join spec S_VWSHRTCT_LANG in the BC Public and Private View Link to an inner join and that did not help either.

Is there a way we can achieve our requirement through configuration/code?

Solution

To meet this requirement, they want to create multiple view links for each language (all pointing to the same view), but with different default queries. So they would like to filter the view links by language in the module specific home pages, like the Opportunities, Activities, and Accounts etc that appear for each entity.

To achieve this requirement a search spec needs to be added for the view link:
1) Select Buscomp 'Public and Private View Link'
2) Expand and select Buscomp User Properties
3) There is a user property called 'Active Public Vlink Searchspec'
The existing value for this user property is [Active Flag] = 'Y' and [Public Flag] = 'Y'

Add the Language Code to this searchspec, this is how it would look like;
[Active Flag] = 'Y' and [Public Flag] = 'Y' and [Language Code] = Language()

4) Compile the srf and launch the application.

Now when you navigate to the module specific home pages, appropriate view links based on the object manager language that you are logged into would be displayed.