Applies to:Error Message Area:Server Infrastructure - SCB
Version:Siebel 8.0 and later
Applies to:Product Release: V7 (Enterprise)
Version: 18.104.22.168 
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.
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.
Applies to:Siebel CRM - Version: 8.1.1 SIA  and later [Release: V8 and later ]
Information in this document applies to any platform.
Siebel 8.1.1 SIA , 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
1) Launch Internet explorer
2) Enter thin client URL & hit enter
SBL-SCB-00007: Enterprise name ( (null)) in the request is invalid.
Unable to make use of Siebel application
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
NOTE:493180.1 - SBL-SCB-00007