SBL-DAT-00501: Invalid search specification '%1'.

Applies to:

Siebel Tools - Version: 7.7.1 SIA [18306] to 7.7.2.12 SIA[18393] - Release: V7 to V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] SVE Fin Svcs
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

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

""Checked for Relevance on 03-Nov-2010""

Symptoms

When launching their Siebel application the customer got the following error:

"We detected an Error which may have occurred for one or more of the following reasons:

Invalid search specification '<?>'. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)"

The startup view was the standard Home Page and the same error was encountered when trying to access "Calendar" and "Activities" screen.

The customer found the following in their Siebel.log file:
- - -
...
ObjMgrQueryLog    Warning    2    0    2004-09-06 11:10:55    (query.cpp (2026)) SBL-DAT-00501: Invalid search specification '

"" + [Type] + ": " + [Description]'.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

ObjMgrBusCompLog    Error    1    0    2004-09-06 11:10:55    (sqlobj.cpp (510)) SBL-DAT-00501: Invalid search specification '<?>'.
...
- - -

Cause

The customer resolved this issue by setting the 'Force Active' property of BC 'Action' to FALSE. This property had been set to TRUE accidentally in their customized environment.

However even if setting BC 'Action' as "Force Active" was not appropriate, that did not explain the behavior observed. By reviewing the BC it was found that this behavior was due to a standard calculated field referencing the character string found in the Siebel.log file, namely:

This standard field is 'Type Description Label' and its calculated value is not immediately visible in Tools. It is needed to use the popup editor to see it:
- - -

"" + [Type] + ": " + [Description]
- - -

The value is on 2 lines. The first line is blank and there is therefore a carriage return

This configuration is not correct since a calculated value, as a validation expression and a search specification, must be all on one line.

This matter is documented in Siebel Developer's Reference > Operators, Expressions, and Conditions > Calculated Field Values and Field Validation.

Bug 12-OM26LH has been logged to address this product defect. Note that this issue is specific to version 7.7 SIA.

Solution

The solution is to correct the calculated value of the standard field 'Type Description Label' by removing the blank line and ensuring the value is all on one line.

References

BUG:12-OM26LH - FIELD 'TYPE DESCRIPTION LABEL' IN BC 'ACTION' HAS AN INCORRECT CALCULATED VALUE (CARRIAGE RETURN)

Applies to:

Siebel Server Sync - Microsoft Exchange Server - Version: 7.8.2.1 SIA [19216] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.1 [19216] Fin Svcs
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.2

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

Symptoms

SSSE does not sync users with email address containing apostrophe.

This is the error we found from the PIMSIEng log:

ObjMgrQueryLog    Warning    2    0    2006-08-25 03:37:13    (query.cpp (2417)) SBL-DAT-00501: Invalid search specification '[PIM User Identifier]='XX.O'YYY@zzz.com' AND [PIM Server Type]='Exchange 2000''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

PIMSIEngSvc    PIMSICompFatal    0    0    2006-08-25 03:37:13    (engmgrsvc.cpp (1375)) EngMgrService: Unable to dispatch extract request message to extract engine. (err: 0x569D).


ObjMgrBusServiceLog    Error    1    0    2006-08-25 03:37:13    (service.cpp (666)) SBL-DAT-00501: Invalid search specification '<?>'.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

GenericLog    GenericError    1    0    2006-08-25 03:37:13    Object manager error: ([0] Invalid search specification '<?>'.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501) (0x569d))

GenericLog    GenericError    1    0    2006-08-25 03:37:13    ( (0) err=4300107 sys=22173) SBL-OMS-00107: Object manager error: ([0] Invalid search specification '<?>'.

Cause

Customer reported that, SSSE does not sync users with email address containing apostrophe.

Comments: Siebel was able to reproduce the behavior internally. Particularly, the sync USERS whose email id contains apostrophe sign (for example “ssse'user04@siebel.com”) fails to synchronize.

Further, the following error message was noticed as well in the PIMSI Engine logs:-

ObjMgrQueryLog Warning 2 0 2006-08-31 17:55:20 (query.cpp (2409)) SBL-DAT-00501: Invalid search specification '[PIM User Identifier]='ssse'user04@siebel.com' AND [PIM Server Type]='Exchange 2000''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

Solution

Please note that currently there is no possible workaround for this reported issue. The only recommendation from Siebel is to not allow the apostrophe sign for the SSSE users email id.

Further, the following change request has been submitted for this issue.

Change Request: "CR # Bug 12-1FWL602  - SSSE fails to sync users with email addresses containing apostrophe sign."

References

BUG:12-1FWL602 - SSSE FAILS TO SYNC USERS WITH EMAIL ADDRESSES CONTAINING APOSTROPHE SIGN.

Applies to:

Siebel Server Sync - Microsoft Exchange Server - Version: 7.7.2.6 [18372] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-MBL-00200, SBL-MBL-02102, SBL-DAT-00225

Hi,

We have 4 users who aren't synching. We know this because the LAST_SYNC_TS column in S_SD_USER_MAP is not being updated and the SBL_ERROR_CODE column is populated.

I've attached logs for the four users:

Xxx.YYY@zzz.com


I looked at the logs but these aren't errors we've encountered before.

Cause

The customer found that 4 of their users were not synching as the LAST_SYNC_TS column in S_SD_USER_MAP was not being updated and the SBL_ERROR_CODE column was populated.

On analysis of the PIMSIEng*.log and the PIMSIExchConnApp*.log files where only PIMSI log events were increased the following error was found for one user Xxx Yyy in the PIMSIEng*.log.

PIMSIEngSvc PIMSIDebug 5 0 2006-10-23 09:58:35 (ssuserinit.cpp (9161)) BatchMgr: Begin DB Transaction for record with PIM Row: b552b481d17bd147ae51f05297c184c700000b859291 for PIM User xxx.yyy@zzz.com on PIM Domain IPM.Appointment.

PIMSIEngSvc PIMSIError 2 0 2006-10-23 09:58:35 (inboundsvc.cpp (723)) InboundDispatcher: User: XYYY, Error: Siebel Inbound Failed to process the message.Message does not have valid data

ObjMgrBusServiceLog Error 1 0 2006-10-23 09:58:35 (service.cpp (659)) SBL-DAT-00501: Invalid search specification '<?>'.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

As there was no detailed indication of why this search specification error was occurring, it was decided to try to synch each user individually to avoid reviewing benign errors from other users and increase ALL the log events including the ObjMgrBusServiceLog event above to 4 for this test as this was set to 1 for the above log file.

After doing so the new log file revealed a more detailed error for the search specification error prior to the sync failing shown below.

ObjMgrSqlObjLog Search 5 0 2006-10-24 15:23:30 Begin: SetSearchSpec for SqlObj 'Employee' at 14431028, Search Spec: '[First Name] ="P. "Xxx"" and [Last Name] ="Yyy" and [Login Name] ="XYYY"'
ObjMgrQueryLog Warning 2 0 2006-10-24 15:23:30 (query.cpp (2121)) SBL-DAT-00501: Invalid search specification '[First Name] ="P. "Xxx"" and [Last Name] ="Yyy" and [Login Name] ="XYYY"'.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
ObjMgrSqlObjLog Search 5 0 2006-10-24 15:23:30 End: SetSearchSpec for SqlObj at 14431028

On reviewing the equivalent PIMSIExchConnApp*.log file it showed the appointment below.
PIMSIEngSvc PIMSIDebug 5 0 2006-10-24 15:23:28
(inboundicalconverter.cpp (789)) Connector: PIM calendar organizer and attendee information:
Syncing PIM User Id: xxx.yyy@zzz.com
PIM Row Id: b552b481d17bd147ae51f05297c184c700000b859291
Meeting Id: 040000008200E00074C5B7101A82E00800000000D0259C08CAEBC6010000000000000000100000009E1FE31DB21C854B862260524013FA44
Owner Appointment Id: -1
URL: http://ExchangeServer:80/exchange/xxx.yyy/Calendar/Updated%3A Gerry - Blackberry training (entire room).EML
Organizer: ,,CRC@zzz.com

Continued in next activity..........
Message 3
Continued from previous activity..........

Required (TO:) Attendees: Xxx,YYY,p.xyyy@zzz.com
Optional (CC:) Attendees:
BCC Attendees:

The p in the appointment was a small p whereas the P in the search specification was a capital.

Solution

The customer was able to resolve the above error by taking the following step. Xxx's first name was P. "Xxx" so the customer changed this to P and moved Xxx (minus the quotes) to the alias name and after making this change the sync was successful for this user.

For the other 3 users it was found that the users was able to sync after increasing the log events, so it was likely a data issue which occurred and had been eliminated.

Applies to:

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

Symptoms

Whilst querying with an apostrophe in the user interface in the Name field the following errors were seen:

The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

Missing quotes around the search criteria or unnecessary punctuation will often cause an error.(SBL-DAT-00403).

Normally if querying for Jack's for example, one would expect to receive an error. The normal way to accommodate such queries including special characters is to surround the query within speech marks, for example "Jack's". However this did not work either.

Cause

The issue related to some custom eScript that was being used to ensure that users populated certain fields in the user interface.

An example exhibiting the same behaviour is shown below. This was used on the Account business component.

function BusComp_PreQuery ()
{
  var sName = GetSearchSpec("Name");
}

Through testing, it was found that the only special character that would not work in the query was the apostrophe. Other characters such as the following worked fine:

; , . @ # \ | + - = [ ] & *

The same behaviour was also seen in 7.7.2.6, so it is likely widespread across the application versions.

Bug 12-1LG178H: "GetSearchSpec on field in BusComp_PreQuery Event with UI query including apostrophe causes error" was raised as a product defect to address this problem for a future product release.

Solution

The following workarounds were suggested to the customer:

1. Instead of querying for "Jack's", try querying for "'Jack''s'". e.g. double quote, single quote, Jack, single quote, single quote, s, single quote, double quote.

2. Take the GetSearchSpec method off the field and utilise it on alternative fields.

3. Use a Try-Catch-Finally statement to catch the error. More details can be found here:
- Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Statements > try Statement

4. Alternatively, use the GetSearchExpr() function and do string manipulation to check that relevant fields are populated. More details of this function can be found here:
- Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > GetSearchExpr Method

The customer decided to use an alternative instead by basically reconstructing the string and replacing the ' with an * on the PreQuery event.

Keywords: SBL-DAT-60236, SBL-DAT-00354, SBL-DAT-00501, SBL-DAT-00403

Applies to:

Siebel Tools - Version: 6.0.1 [2848] to 8.1.1.3[21219] - Release: V6 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: IBM DB2 7.1 FixPack 10
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.2

Checked for Relevance on 17-Nov-2010
This document was previously published as Siebel SR 38-3381949661.

Symptoms

A calculated field with this calculation formula

IIf(([SR Age]>90, 750, IIf([SR Age]<91 AND [SR Age]>60, 500, IIf([SR Age]<61 AND [SR Age]>30, 250, [SR Age]))))

triggered this error message:

"Invalid search specification '<?>'. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)"

Cause

The error message was caused by extra parentheses in the parameter list of the outermost IIf() call. Because of this, the parameter list could not be evaluated correctly. 

Solution

Ensure to not adding too many pairs of parentheses to the parameter list of a function. This might make the interpreter believe that there is only one parameter in the list where it would expect three.

The issue was resolved after changing the formula as follows:

IIf([SR Age]>90, 750, IIf([SR Age]<91 AND [SR Age]>60, 500, IIf([SR Age]<61 AND [SR Age]>30, 250, [SR Age])))