SBL-SCB-00007: Enterprise name ( %1) in the request is invalid.

Applies to:

Error Message Area:Server Infrastructure - SCB
Version:Siebel 8.0 and later

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SCB-00007: Enterprise name ( %1) in the request is invalid.

Scope

This document is informational and intended for any user.

SBL-SCB-00007: Enterprise name ( %1) in the request is invalid.

Explanation

Enterprise name in connect string could be wrong.

Corrective Action

Check eapps.cfg configuration - make sure that enterprise name matches that of the server.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: IBM DB2 8.2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 5L 5.2

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

Symptoms

SBL-SCB-00007What is the error code SBL-SCB-00007. I was not able to retrieve anything from the search on this from the knowledge base. In our production environment we get a error GenericLog GenericError 1 0 2007-05-31 13:22:16 (scbcomp.cpp (235) err=7100007 sys=0) SBL-SCB-00007: Enterprise name ( sbldev_ent) in the request is invalid in the scbroker.log file, it is becoming a huge file. sblprod_ent is the enterprise name but not sure why and what is looking for sbldev_ent which is the name for the development enterprise. I have attached the eapps.cfg file for your reference. Please note we modifid the sections we use for production in the eapps.cfg file from Dev environment and placed it in production. We use F5 bigip to load balance the siebel app servers.

Thanks

Solution

Message 1

For the benefit of other readers:


The error code SBL-SCB-00007 means that the Enterprise name in connect string could be wrong. Then you must check eapps.cfg configuration and make sure that enterprise name matches that of the server.

However the eapps.cfg configuration file was configured properly and also any request to sbldev_ent was not found in the Siebel Web Server log files.

Siebel Technical Support suggested customer to install a network trace utility or sniffer tool such as ethereal on the Siebel server and trace the traffic to the SCBroker Port 2321 and after that customer was able identify that even after bringing down the entire qa environment, the port 2321 was getting traffic.

Customer worked with their network team to understand the source of the traffic and they were able to identify that the BigIP health monitor was not setup correctly to look at SBLQA_ENT and hence the errors on SCbroker for invalid enterprise name.

Regards

Applies to:

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

Symptoms

Environment:
-------------------
Siebel 8.1.1 SIA [21111], HP-UX 11.11 Itanium (32-bit), Test environment

Statement of Issue:
-----------------------------
Unable to access the Siebel application using Thin client, giving server busy error message

Steps:
---------
1) Launch Internet explorer
2) Enter thin client URL & hit enter

Error:
------
SBL-SCB-00007: Enterprise name ( (null)) in the request is invalid.

Business Impact:
-------------------------
Unable to make use of Siebel application

Changes

Reconfigured the SWSE with incorrect SC Broker port number

Cause

Incorrect SC Broker port number mentioned while reconfiguring SWSE

Solution

1) Stop Web server
2) Take a back up of existing eapps.cfg & eapps_sia.cfg files
3) Replace the in correct SC Broker port number to correct one [find and replace all incorrect values]
4) Save files
5) Restart the web server

References

NOTE:493180.1 - SBL-SCB-00007