Search This Blog

SBL-DAT-00228: Unable to load the scripting extension language DLL '%1'! Scripting was enabled in this instance of Siebel, but the DLL which is needed

Applies to:

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

Symptoms

System Preference "Enable ST Script Engine" controls if the Strong Typing (ST) eScript engine is used or not, and it has to match the code in SRF. If they do not match, dedicated web client may see the error when scripting is about to run. Actual error may vary but one case is "The user ID or password that you entered is incorrect." error upon the login operation. If siebel.log file records following error message, please verify the possible scenarios below.

SBL-DAT-00228: Unable to load the scripting extension language DLL 'sscfjs'
Scripting was enabled in this instance of Siebel, but the DLL which is needed to implement it could not be loaded.


Case 1) After SRF was compiled with "Enable ST Script Engine" = TRUE, this value has been changed to FALSE, or vice versa, without re-compilation of SRF.

Case 2) After "Enable ST Script Engine" is changed on Siebel Tools Client, new SRF is compiled "without" re-login to Siebel Tools Client.

Case 3) Using the same SRF and CFG file, the same error occurs on the server database but not on the local database, or vice versa.

Change Request 12-1ERU3YS has been filed for this behavior.

Cause

Case 1) script codes in the SRF and "Enable ST Script Engine" system preference do not match.

Case 2) This setting is reflected at login operation. If new SRF is re-compiled right after change, it still uses the previous setting.

Case 3) Since "Enable ST Script Engine" is set on the database level, the server database and the local database may have different value.

Solution

Case 1) Do one of either operation.
- Change "Enable ST Script Engine" so that it matches to the code in SRF.
- Re-compile SRF with the current "Enable ST Script Engine" setting.

Case 2) Make sure re-login to Siebel Tools Client before SRF compilation.

Case 3) Check System Preferences on both database and make sure they have the same value. If not, determine which value should be used and re-compile SRF if necessary.

References

BUG:12-1ERU3YS - UNABLE TO LOGIN WITH SIEBEL CLIENT IF ST SCRIPT ENGINE FEATURES ARE ENABLED
NOTE:808628.1 - Mobile client cannot login if period sign (.) exists in the installation path.

Applies to:

Siebel CTI - Version: 7.8 [19021] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
getting the following error:
SBL-DAT-00228: Unable to load the scripting extension language DLL 'sscfjs'
Scripting was enabled in this instance of Siebel, but the DLL which is needed to implement it could not be loaded.?

Symptoms

none

Changes

ST eScript engine must be set to "FALSE" to fix this error.

Cause

ST eScript engine parameter

Solution

ST eScript engine must be set to "False".
Note that as per Genesys documentation:
"... in order to install the Gplus adapter 7.5, the Siebel ST eScript engine must be set to "FALSE". .."

Enhancement request has been logged for this:

12-1X1AW2R - Ability to install Gplus adapter 7.5 driver when Siebel ST eScript engine is set to "TRUE"
so you should be able to track it in the future.




Applies to:

Siebel System Software - Version: 7.5.2.211 SIA [16061] - Release: V7
Sun Solaris SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.2.211 [16061] Com/Med
Database: Oracle 9.2.0.2
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00228

We have installed the Siebel Web Server Extension on Sun One Enterprise Edition 6.0 with SP2 and application server is also on Sun Solaris 8. I am unable to connect to siebel server using CUSTOM SRF from a thin web client. I can however, connect to siebel server using a thin web client with the standard siebel_sia.srf.

To replace the custom SRF I shut down the Web Server, siebel server and the gateway server in that order. I then copied my custom srf (renamed to siebel_sia.srf) on the /siebsrvr/objects/enu folder. I started up my gateway server, siebel server and then after verifying that the server component eCommunicationsObjMgr_enu is online, I started my web server. On accessing the siebel server through a browser it gives me an error message in the browser stating "The server you are accessing is either busy ...”

SWE Log shows:
GenericLog    GenericLog    0    2003-06-09 19:43:29    ERROR (8507/23):     23: [SWSE] Impersonate failed. Unable to load the scripting extension language DLL '%1'!\nScripting was enabled in this instance of Siebel, but the DLL which is needed to implement it could not be loaded.

GenericLog    GenericLog    0    2003-06-09 19:43:29    ERROR (8507/23):     23: [SWSE] Set Error Response (User: Session: Error: 00028342 Message: Unable to load the scripting extension language DLL 'sscfbas'! Scripting was enabled in this instance of Siebel, but the DLL which is needed to implement it could not be loaded.)

Also note that I am able to connect to siebel server with a dedicated web client using the same custom srf.

Please advise.

Solution

Message 1

For the benefit of other customers:

The errors were seen due to the reason that there were some Siebel VB scripts in the srf which would not run on the Unix application servers. Temporarily, setting Application Scripting Enabled to FALSE on the object manager parameter for the application, the application should work. Customer were in the process of converting all the Siebel VB script to eScript, and once that was done, the error was eliminated for them.

Additionally, please, refer to the Bookshelf for further information > Siebel Object Interfaces Reference > Siebel Programming Tools > Components of the Siebel Programming Environment, section Siebel eScript Language: “You can use Siebel eScript under UNIX, where Siebel VB is not Supported.” For developing scripted objects that run on Unix platform, you must translate your code into eScript.

-Vineet Goel
Siebel Technical Support


No comments:

Post a Comment