SBL-ADM-02071: Enterprise server %1 not found in gateway server

Applies to:

Siebel CRM - Version: 8.1.1 SIA [21111] - Release: V8

Information in this document applies to any platform.

Symptoms

Error SBL-ADM-02071 during Gateway Configuration while Creating Enterprise in Gateway.

Cause

User didn't run "CreateDbSrvrEnvScript" before configuring the database. This is a required step and it set the variables for the ODBC driver to work properly. There's no need to copy the .odbc.ini file manually as the customer did as workaround.

This script is required when you don't have an existing database, which fits in the customer's case.

What does this script do? It creates (not sure if it creates or updates) the script dbenv.sh, and this script contains the following:

ODBCINI=${SIEBEL_GDIR}/sys/.odbc.ini ; export ODBCINI

${SIEBEL_GDIR} is the variable which stores the Gateway directory, and ODBCINI is the variable read by the Siebel Server to use the proper .odbc.ini. So basically the Enterprise Server installation reads the .odbc.ini from the gateway sys folder.

The .odbc.ini file not getting created on SIEBEL_ROOT/siebsrvr/sys is a "feature" and not a defect.

Solution

To run the CreateDbSrvrEnvScript.

Applies to:

Siebel System Software - Version: 8.0 SIA [20405] to 8.1 [21039] - Release: V8 to V8
Oracle Solaris on SPARC (64-bit)
Linux x86
Linux x86-64
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.2.0.2
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 5.8

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

Symptoms

After a successful install, I'm creating a new Siebel 8.x Enterprise and get the following errors:

Error creating Parameter:MaxEntrTasks for Comp:TxnProc in CompGroup:Remote
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:MaxEntrTasks for Comp:RepAgent in CompGroup:Remote
Strict Flag set to FALSE, continuing with the next Object...

Error creating Component:MsgBroadcastMgr in CompGroup:CommMgmt
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:SearchSpec for Comp:TaskLogCleanup in CompGroup:TaskUI
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:MaxMtServers for Comp:RTSDispatcher in CompGroup:RTSRemote
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:MTInfraTrace for Comp:AdminNotify in CompGroup:SystemAux
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:MaxSubtasks for Comp:AdminNotify in CompGroup:SystemAux
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:MaxWorkerTasks for Comp:AdminNotify in CompGroup:SystemAux
Strict Flag set to FALSE, continuing with the next Object...

Error creating Parameter:AdminRoleName for Comp:ServerMgr in CompGroup:System
Strict Flag set to FALSE, continuing with the next Object...

...

Type "help" for list of commands, "help <topic>" for detailed help
SBL-ADM-02071: Enterprise server <enterprise_name> not found in gateway server

Execution Successful!

Solution

These errors proved to be benign and the customer was able to proceed successfully with configuring and starting the Siebel Server.

Applies to:

Siebel Life Sciences CRM - Version: 8.0.0.2 [20412] - Release: V8
Information in this document applies to any platform.

Symptoms

When trying to enable automation via Server Manager, the following error messages were returned :
srvrmgr> change param EnableAutomation=true for server ent_dev comp sccobjmgr_enu

SBL-ADM-60070: Error reported on server 'Gateway Server' follows:
SBL-SCM-00028: Key not found
SBL-SCC-00005: Internal:No more items found.
SBL-NET-01218: The connection was refused by server ctmsdevapp. No component is listening on port 49168.

SBL-SCM-00028: Key not found
SBL-SSM-00003: Error opening SISNAPI connection.
SBL-NET-01218: The connection was refused by server ctmsdevapp. No component is listening on port 49168.

SBL-SCM-00028: Key not found
SBL-SCC-00005: Internal:No more items found.
SBL-NET-01218: The connection was refused by server ctmsdevapp. No component is listening on port 49168.

SBL-SCM-00028: Key not found
SBL-SSM-00003: Error opening SISNAPI connection.
SBL-NET-01218: The connection was refused by server ctmsdevapp. No component is listening on port 49168.


change param EnableAutomation=true for comp sccobjmgr_enu
SBL-ADM-02077: Server name must be specified for this operation

Cause

A separate license is required for Siebel Test Automation module.

Solution

1. Verify that a Siebel Test Automation license is included as part of the license keys.

Alternatively, a temporary solution is to use the all-inclusive license codes from http://licensecodes.oracle.com/siebel_master.html to eliminate any issues with licensing.

2. Run the following commands in srvrmgr and restart the Siebel Server:

change param EnableAutomation=true for comp <component name>
change param AllowAnonUsers=true for comp <component name>

Restart Siebel Server. 

In Windows, launch using http://hostname/eclinical_enu/start.swe?SWECmd=AutoOn
SiebelAx_Test_Automation_xxxxx.exe process should appeared in Task Manager.

Applies to:

Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.2.0.3
Application Server OS: IBM AIX 5L 5.3
Database Server OS: IBM AIX 5L 5.3

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

Symptoms

We've tried to install a new Siebel instance on another server. But there's a new trouble: we've got a message "SBL-ADM-02071: Enterprise server SBA_80 not found in gateway server ... Execution Successful" while configuring Siebel Enterprise Server. We've tried GUI and console mode as one with the same result. Looks like Siebel Gateway Server installed correctly and works fine, but it's impossible to install Siebel Enterprise. The srvrmgr returns the same error: SBL-ADM-02071.

Solution

Message 1

For the benefit of other users:

The customer tried to install a new Siebel 8 instance on a IBM AIX 5.3 Server, but they encountered error message "SBL-ADM-02071: Enterprise server SBA_80 not found in gateway server ... Execution Successful" while configuring Siebel Enterprise Server. They have tried both GUI and console mode with the same result. Also, the srvrmgr returned the same error: SBL-ADM-02071.

The issue was resolved by activating posix_aio (asynchronous Input/Output) on AIX. Then, the installation was successful.

Thank you,
Siebel Technical Support

Applies to:

Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.2.0.3
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i

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

Symptoms

Received the following error configuring the enterprise after installing and configuring the gateway:
SBL-ADM-02071: Enterprise SBA_80 not found in gateway server

ssincfgw -args LANG=language MODE=mode MODEL_FILE=SIEBEL_ROOT/gtwysrvr/admin/
enterprise_console_sia.scm -console

Solution

Message 1

These are the steps to reproduce:

- on platform HP-UX, install Gateway 8.0
- run configuration and create gateway
- run configuration , in console mode , and choose to create enterprise. It finishes, but gives errors and the code
SBL-ADM-02071: Enterprise server SBA_80 not found in gateway server
- siebns.dat created has missing components in some of the component groups as CallCenter, CRA, Communications, etc.

This issue does not occur if running the configuration in GUI mode.

Change Request 12-1LAVYIB has been logged to address this issue. The workaround for now is using GUI mode only.

Thank you.

Oracle Product Support – Siebel CRM

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Life Sci
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3

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

Symptoms

SBL-ADM-02071

When we run a task from the "component request" view either through thin client or thick client, the component request remains in the "queued" status and does not become "Active"; if we launch the same task using the Line command, it starts correctly and it is executed. I have referenced SR 38-1004860262. There was also an SR that sugguested moving the data source sections above the Local section in the cfg. But all of the above SR have not resolved the problem. Can you recomend a course of action?

Thanks

Solution

Message 1

Issue : Component requests submitted from the GUI, stay in queued State. This happens after certain time. Initially the Component requests are Success, then after some time any new Component requests stay in Queued state. The examples of the Component requests are Generate New DB, DB Extract , EIM. If the Component requests were submitted via srvrmgr command line they were Successful.

Resolution : Please check the following setting at the Enterprise level

Enterprise Configuration > Enterprise Parameters: SISNAPI connection maximum idle time

This should be set to -1 which is the default value.
More information on the parameter SISNAPI maximum connection idle time (ConnIdleTime):
Default value = -1
This parameter should only be set at the component level, and only for application object managers and EAI object managers. It should never be set for batch mode or background mode components, nor should it be set for SRBroker or any other infrastructure related component. Therefore, it should never be set at the enterprise level.

Furthermore, it should only be set only if Resonate Central Dispatch is used to load balance the application servers.

It is recommended where there is a firewall between the application and web server, and firewall timeout is set. The value should be set to a value slightly less than the firewall timeout value.
Therefore, if firewall has a timeout value of 3600 seconds (1 hour), then the ConnIdleTime parameter should be less than 3600.