Search This Blog

SBL-DAT-00134: Unable to lookup message. Message '%1' of Category '%2' is undefined.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.2 [18356] Cons Goods
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

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

Symptoms

SBL-DAT-00134, SBL-EXL-00151

Hi,

There seems to be an issue with the new scripting engine released in 7.7.2.3 GA (please update Siebel Version on this SR). We extensively use Message Category and User Defined Errors in our scripts. After a full compile (we have set EnableCLIScripting = TRUE on all cfg files), instead of raising the right error we get a generic error -

SBL-EXL-00151: Unable to lookup message. Message 'User Defined Errors' of Category 'User Defined Errors' is undefined.(SBL-DAT-00134)

This happens when the script tries to execute the below code -

TheApplication().LookupMessage("User Defined Errors","BAT_ERR_MSG_0141");

The parameters for LookupMessage are category and key. But, the new script engine is using the category parameter to search the key as well. I tested this by creating a new key called User Defined Errors within the Category called User Defined Errors. Then the above line of code does not return generic error but picks up the text message in the key=User Defined Errors.

This seems to be a major bug in 7.7.2.3. We use Message category extensively with over 200 error messages stored in user Defined Errors.

Solution

Message 1

For the benefit of other readers,

Customer observed that the new scripting engine fails on calling LookupMessage() or RaiseError() properly.


Reasons for the behavior

This defect has already been confirmed, and change request 12-Z0SBOO was raised to address this matter. It has not been published on SupportWeb before since it was raised agains version 7.8.1.1, which had "limited distribution" (LD) status.

The associated Fix Request 12-Z31U1R for 7.7.2.3 (tageted towards a QuickFix) is still in progress (as of this writing).


Resolution

The temporary woraround until the QuickFix is available is to revert back to the old eScript engine.


Christoph Berger
Siebel Technical Support

Additional keywords: new eScript engine, ST engine

No comments:

Post a Comment