Search This Blog

SBL-GEN-00000 Unable to load message 0xffff

Applies to:

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


Customer reported the following:

In our new Siebel TEST environment, 2 Application Servers failing with Handshake failed error.

This is newly built Siebel environment, we have multiple servers

Ntsydasu304 - gateway and app server

Ntsydasu303 - App Server

Ntsydasu1186 - App Server

Ntsydwbu117 - Web Server

The Siebel gateway is up and running, all the application servers are started. But 2 application servers Ntsydasu304 and Ntsydasu1186 are failing with handshake Failed error


The issue seems to be caused by either port number being used by other non Siebel process, or the mapping between the hostname of the servers and the IP addresses. This analysis was based on the fact that when srvrmgr tried to communicate with the ServerMgr, it threw errors below:

- Handshake(siebel://ntsydasu1186:49162/es_obfstsb1/servermgr/ntsydasu1186) on conn 0x3121330 ok

- connect() to ntsydasu303:49168 failed (err=10060 | Connection timed out.

- connect() to ntsydasu304:49168 failed (err=10060 | Connection timed out.


For the benefit of other readers:

It was suggested to the customer to try the following:

telnet ntsydasu1186 49162
telnet ntsydasu303 49168
telnet ntsydasu304 49168

It is expected that the first one should be successful. If the 2nd and 3rd are also successful, please shutdown the Siebel servers and run the telnet again on the last 2 servers, to verify if other non Siebel process is listening on port 49168.

If the second and third fails or not responding, please try telnet the IP address. If successful, then there seems to be problem with the host-IP mapping, please verify.

By following the above steps, customer was able to identify the cause of the problem, They opened up all the required ports and the problem could be resolved.

Applies to:

Siebel Workflow - Version: [16186] to [18382] - Release: V7 to V7
HP-UX Itanium

Product Release: V7 (Enterprise)

Version: [16186]

Database: Oracle

Application Server OS: HP-UX 11i

Database Server OS: HP-UX 11i

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


Customer was facing a problem with Workflow process manager in the development.  The application is rolled out in many countries. Each country will have a separate process manager. There are many scheduled workflows in the night by using a repeating batch components

Workflow process manager was failed in the development with the following error.
SiebelError: Unable to load message 0xffffSBL-GEN-00000' for one of the scheduled job.

we have changed the 'OM - Model Cache Maximum property' to zero and it was worked fine but performance of the process impacted significantly.

After that we have set the Cache property on the Business Services which are calling by the process to True and OM - Model Cache Maximum property to 10 on workflow process manager.
But the process was failed again with the following error
ObjMgrLog     Error     4     2005-02-09 13:12:34     SBL-GEN-00000 Unable to load message 0xffff ObjMgrLog     Error     4     2005-02-09 13:12:34     (SBL-EXL-00145) User cancel operation interrupted the running extension language script.
But the process is working fine with 'OM - Model Cache Maximum property' of workflow process manager with 0

Can you please suggest a way to resolve workflow process manager errors without impacting the performance?


The problem seems to be related the combination of having eScript in the Application_Start event of the application used by the WfProcMgr, SVB script in a buscomp instantiated in the BS.


For the benefit of other readers the following behavior was encountered.

The execution of workflow process, calling a business service, raises the error below, only at the first execution of the process (just after the restart of the Workflow Process Manager component,WfProcMgr) but not the next times.

SBL-GEN-00000 Unable to load message 0xffff

It does not seem related to the script itself, but just to the presence of the scripts. Here are for instance some steps conducted on top of standard repository that reproduced the problem.

1.    Application "Siebel Sales Enterprise" (used by the Workflow Process Manager component in standard), add following eScript script to Application_Start:

2.    Buscomp "Account", add following Visual Basic script to BusComp_SetFieldValue

3.    Compile SRF, deploy to server.
4.    Create a BS in the database (client), in eScript with following script, cache=True.
function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
case "Method1":

function fn_Method1(Inputs)
var v_boBanner ;
var v_bcBanner ;

v_boBanner = TheApplication().GetBusObject("Account");
v_bcBanner = v_boBanner.GetBusComp("Account");

v_bcBanner = null;
v_boBanner = null;
5.    Create a new workflow process, Start > BS > End, that calls the BS created above. Activate the process.

Just after the restart of the component, the process fails with error SBL-GEN-00000 Unable to load message 0xffff when constructing buscomp "Account" in the BS script. Next executions work correctly.

Change request  BUG 10493326 was created to have this product defect addressed.  The issue was not seen beginning in version 7.8 of the application.

Here are few observations and possible workarounds.

a)    Setting the parameter ModelCacheMax to 0 seems to resolve the error but then the performance was very poor and it is not recommended.
b)    If the BS is defined in Tools (compiled in the SRF) rather than in the Client (stored in the database), the problem does not occur.
c)    In the above example, changing the script in Application_Start from eScript to SVB solved the problem.
d)    In the above case, changing the script in buscomp from SVB to eScript solved the problem.



Applies to:

Siebel System Software - Version: 7.7.2 SIA [18325] and later   [Release: V7 and later ]

Oracle Solaris on SPARC (64-bit)

Product Release: V7 (Enterprise)

Version: 7.7.2 [18325] Pub Sect

Database: Oracle

Application Server OS: Sun Solaris 9

Database Server OS: Sun Solaris 9

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


SBL-GEN-00000, SBL-UIF-00276
We are currently running some performance load tests using Mercury's LoadRunner.
During our run, we have have 1 user being added every 25 seconds for a maximum of 50 users, which
run until completion. At around the 28 minute mark and 35 users have entered the system, Siebel
starts producing errors causing all subsequent users/transactions to fail. Attached is the error
log. Some of the errors that are produced include: "Communication: User is not associated with
any communication configuration in the database", "Unable to load message 0xffff", "Cannot open
file: /opt/siebel/SBLSRVENV14A/siebsrvr/webtempl/CCError.swt".


Configuration/ Setup


Message 1

For the benefit of other users:

Customer was running a load test with Load Runner where the test scenario consisted of a user logging into the Siebel Application, calls a business service/workflow that makes an external call to outside system, and brings data back to be evaluated and used by the user. They had one user login every 25 seconds, and the following errors occured around the 30 user mark or about 25 minutes into the run.

[LOADTEST061] 686d688 Load Script from Attachment: Error: errCode=65535 errorMsg="Unable to load message 0xffff Parameter 1 = (SBL-GEN-00000)"

(parser.cpp (3522)) SBL-UIF-00276: Cannot open file: /opt/siebel/SBLSRVENV14A/siebsrvr/webtempl/CCError.swt

Technical Support on further research found that the SBL-UIF-00276 was occuring due to the fopen limit as per "'Alert 1025: Siebel Server Components That Read or Write to Files on Solaris May Encounter Fopen() Behaviors".

To resolve the behavior following workarounds were suggested:

The workaround is to :

1) Turn off all extra logging for this Siebel Object Manager component (default settings). This will reduce the number of log files opened and written by this component.

2) Decrease the number of tasks for each Siebel Object Manager process by increasing the number of MaxMTServers.

Customer adjusted the Min MT Server and Max MT Servers for the Object Manager component to resolve the behavior.

Applies to:

Siebel Tools - Version: SIA [19221] to - Release: V7 to V8
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: [19221] Life Sci

Database: Oracle

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-3214918831.

""Checked for Relevance on 20-Feb-2012""


Customer tried to add a MVG Applet to a field in Contact Home Add Virtual Form applet in Contacts Home Page view. When adding a text box, it does not display and only the MVG Icon is displayed.

If trying to click on the icon, the following occurs:

Unable to load message 0xffff(SBL-GEN-00000).


The customer had customized standard applet 'Contact Home Add Virtual Form Applet' by exposing a control based on the MVF 'Street Address' and that had a MVG applet associated.

In the UI they noticed there was no text box displayed for this control. Only the label and the MVF icon appeared. Also when the MVF icon was clicked the following error occurred:
- - -
Unable to load message 0xffff(SBL-GEN-00000)
- - -

This behavior is due to the fact it is currently not possible to used MVG applets in "Add" and "Search" screen home page applets. This matter is documented in the Bookshelf:

Configuring Siebel Business Applications > Configuring Screens and Views > Process for Creating Screen Home Page Views >Creating Rapid Search and Rapid Add Virtual Business Components.
- - -
CAUTION: MVGs are not supported on Rapid Search or Rapid Add applets.
- - -

Bug 10501236  has previously been logged asking for the possibility of using multi-value fields in Rapid Add applets. This matter is discussed in Note 534213.1 Hierarchial Picklist on homepage not working properly.


The customer wanted even so being able to select one address when adding contacts via the "Add" applet. It was suggested the following to achieve this requirement:

1 - Add 2 dummy fields in BC 'Contact Home Add Virtual', for example:

- - -

Name: Dummy Address Id

- - -

Name: Dummy Street Address

Pick List: MyPickList

- - -

'MyPickList' would be a pick list based on BC 'Pharma Address' and the 2nd field would have 2 pick maps:

- - -

Field: Dummy Street Address

Picklist Field: Street Address

- - -

Field: Dummy Address Id

Picklist Field: Id

- - -

2 - Add a control mapped to field 'Dummy Street Address' on applet 'Contact Home Add Virtual Form Applet' and expose it on the "Edit" applet web template. Set a pick applet based on BC 'Pharma Address' to this control.

3 - In the WebApplet_PreInvokeMethod event of applet 'Contact Home Add Virtual Form Applet' test if the method invoked is 'Mirror Add GotoView' and if yes set a specific dynamic user profile attribute (Method: SetProfileAttr) with the value of the BC field 'Dummy Address Id' and set the 2 dummy BC fields to NULL.

NOTE: "Mirror Add GotoView" is the method invoked by the "Add & Go" button.

4 - In the BusComp_PreWriteRecord event of BC 'Contact' test if the specific dynamic user profile attribute is set (Method: GetProfileAttr) and if yes, associate the address to the contact by using the address id stored in the profile attribute. For example:

(a) Instantiate the MVG BC associated to the MVF 'Street Address' of the active BC

> Method: GetMVGBusComp

(b) Instantiate the associate BC tied to this MVG BC

> Method: GetAssocBusComp

(c) Query the field 'Id' in the associate BC using the value stored in the local variable

> Methods: SetViewMode, ClearToQuery, SetSearchSpec, ExecuteQuery

(d) If a record is retrieved associate this one

> Methods: FirstRecord, Associate

(e) Set the 2 BC objects to null or nothing to destroy them

NOTE: Do not forget to reset the dynamic user profile attribute.

For further information about the programming possibilities and Siebel interface events and methods, please refer to the Bookshelf:

# Siebel Object Interfaces Reference

- Programming

- Interfaces Reference

Applies to:

Siebel Pharma Handheld - Version: [18385] and later   [Release: V7 and later ]
Information in this document applies to any platform.


We are trying to synchronize our PDA in Companion Sync method against a local DB and a SIA [18385] QF0A08 local client in a machine with a Vista O.S always unsuccesfully. The siebel application in the PDA is installed using a CAB PDA [18385]. The synch process begins as expected:
- Login Complete
- Initialization Complete
- Configuration Updade Not Required
- Setting Filters complete
- Transaction Upload Complete
- No Transaction Errors Reported
And then, at the start of the Extracting Database phase, the following error typically appears:
- Server returned NOTOK. Fatal error etc.
After reviewing the log (attached), the following error appears 3 or 4 times:

(buscomp.cpp (25186)) SBL-GEN-00000: Unable to load message 0xffff

After searching at the metalink I find out a SR with the similar error on PDA synchronization. The solution provided is to set the EnableScripting cfg parameter to FALSE. I tried this solution and the synchronization works fine. The problem is that we use scripting in our application at synchronization level and we can't disable that cfg parameter.

Another important point to notice is that without uninstalling the PDA siebel application, using the same local DB and local client ( SIA [18385] QF8) in a W2000 machine, the synchronization works absolutely fine with the EnableScripting parameter set to TRUE.

Our question is:

- Why the PDA synchronization is not possible in a Vista machine and it is on a W2000 machine on the same conditions?


This behavior is triggered through the introduction of scripting to any of the following methods :
but only affects environments in which Siebel Handheld Clients are synchronizing with Siebel Mobile Clients (Companion Synchronization).


The behavior is caused by changes to the way in which Microsoft Vista handles COM initialization.


In order to resolve the behavior users have a number of options :
1) Set EnableScripting=FALSE on the appropriate .cfg file used for handheld synchronization (e.g. pharmace.cfg, cgce.cfg, etc)
2) Ensure that no scripting is included in the following events :
3) Apply the fix for CR #10560131  "PDA Synchronization in a Vista OS machine failing".
Fixes have been included in the Siebel FixPack and the Siebel FixPack.



No comments:

Post a Comment