SBL-NET-01218: The connection was refused by server %1. No component is listening on port %sysError.

Applies to:

Siebel System Software - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-NET-01218Hi,

     Have managed to change DSConnectString from "SiebSrvr_css77hkes" to "siebel" but still not working until I went to update the passwords again for both sadmin and siebel from the Administration screen. Now all the services are running from GUI. Refer to attachment. captured by using delicated web client. 20040816screen.doc

     However, I still can't login via web client.(http://[Server Name]/fins_enu) It gives me the familiar 'sys busy message'. Refer to 20040816screen.doc
      a) I have checked the swse log, it complains about login failed for GUESTCST. I have tried to login via sqlplus without problem. Result shown in 20040816screen.doc. I have also launched "Siebel Web server extension configuration" to re-configure it again but still with no luck. Have used: i) employment anonymous login name/password=GUESTCST/GUESTCST; ii) Contact Login/Password=GUESTCST/GUESTCST; web update projection key=GUESTCST.

      b) Had checked the siebsrvr logs, have found a raft of errors on SBL-NET-01218 and SBL-SVR-01051. Tried to sync the Components per stated in SR38-1358013887 but still in vain.

     Attached are the logs and screen shot. In the zip file of 20040816, you will find
     1) 20040816screen.doc : the screen capture.
     2) eapps: contain eapps.cfg and eapps_sia.cfg. I can't find eapps_fins.cfg and
eapps_sis.cfg as it stated in eapps.cfg.
     3) siebns: the siebns.dat.
     4) siebsrvr-log: the sibsrvr logs
     5) swse-log: the swse log.

regards,

Cause

Change Request 12-O6HYF2

Solution

Message 1

For the benefit of the other,

Description:
Based on reviewing this behavior, there is incorrect port number in ConnectString parameter in eapps_sia.cfg and there are some error messages in FINSObjMgr_enu_26640.log.

Resolution:
1/ As per your ConnectString for fins_enu in eapps._sia.cfg, the port number is different from SCBroker port number (default 2321). Therefore, the unexpected behavior on connecting to Siebel Server with Web Client is resolved after changing to port number 2321 same to SCBroker port number.

ex)eapps_sia.cfg
[/fins_enu]
ConnectString = siebel.TCPIP.None.None://[Server Name]:2320/css77hke/FINSObjMgr_enu

For more information, please refer to Siebel Installation Guide for Microsoft Windows:Servers, Mobile Web Clients, Tools Version 7.7, Chapter 8. Installing the Siebel Web Server Extension, Configuring the Siebel Web Server Extension, Configuring the Siebel Web Server Extension;

“3. Enter the hostname for the Siebel Server and the port number (default 2321) for the SCBroker component. Click Next and proceed to Step 6."

For some incorrect port number examples on ConnectString parameter in eapps.cfg file, Change Request 12-O1FMXZ has been raised to address the Documentation Defect.

2/ As per error messages (SBL-NET-01218 and SBL-SVR-01051) in OM log files, these are benign error messages. Change Request 12-O6HYF2 has been raised to address these error messages.

Regards,

Applies to:

Siebel System Software - Version: 7.7.1 SIA [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] Cons Goods
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

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

Symptoms

SBL-NET-01218I'm currently trying to install a second Siebel server withing our test environment (to test so that I can ultimately do the same in our production environment). The installation seems to go OK, without errors. After installing, I can manually reassign component groups to the new server in the Server Config Admin views. But after restarting the Siebel services on both servers and synching the enterprise settings, I can't log in using the web client anymore (I've assigned the object managers to the new server). I'm attaching the log files to this SR.

Some specs:

SASN132 is our existing server, which runs the gateway server and the first siebel server. SASN142 is our new server which runs our second siebel server.

I already went through Troubleshooting steps 24, but that didn't help me any further.

Regards,

Cause

Configuration/ Setup

Solution

Message 1

For the benefits of other users:

Customer installed a second server and tried to assign the component group to the second server. However, after restarting the servers, the customer was not even able to login to the first server and it was found that the reassignment of component group did not really succeed.

Resolution:

Review of the siebns.dat file showed that a server that was supposed to be uninstalled still exists in the siebns.dat. After this uninstalled server was removed from the siebns.dat by Siebel Technical Support and was used to replace the existing siebns.dat, the customer was able to connect to the first server. Please note that the siebns.dat file should not be edited manually in a text editor.

However, the assignment of the components groups did not succeed. The customer was then advised not to unassign the Component Group While the Components are still running as indicated in Alert 1042 “Do Not Delete Component Definitions or Unassign Component Groups While Components Are Still Running”. In addition, the customer was also advised to restart the Siebel Server System Service after assigning.

After restarting the service, the assignment of component group was successful and the customer was able to establish connection to the second server after making modifications to the eapps.cfg file.


Siebel Technical Support.

Applies to:

Siebel System Software - Version: 7.7.1 SIA [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] Life Sci
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

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

Symptoms

After we rebooted the server, we could not longer to access to siebel thru browser.
Here is the error we got:
"The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.[10:03:02] "

Web server and app server are on the same machine.
We increased the log level on the SWEAPP, but we did not get any log files. Obviously we cannot establish the connection between siebel server and web servber.

I checked the permissions on the SWEAPP, and prior to reboot, we could login to siebel.

Please call me as there are no people who can wok with siebel, and install dedicated web client is not the option for us now.

Cause

Configuration/ Setup

Solution

Message 1

For the benefit of the reader:

The users were not able to login using thin client. The siebel web server log file has following errors:

*********
SessMgr    ConnOpen    3    0    2004-10-15 10:41:45     2536: [SESSMGR] Open(siebel.TCPIP.None.None://usdfswdsbl1:2321/SiebelDev/eMedicalObjMgr_enu, 60, 300) SisnTcpIp    SisnSockWarning    2    0    2004-10-15 10:41:46     2536: [TCPIP-client] connect() to usdfswdsbl1:2321 failed (err=10061 | Connection refused.) SessMgr    ConnOpen    3    0    2004-10-15 10:41:46     2536: [SMCONN] Failed to open connection to (siebel.TCPIP.None.None://usdfswdsbl1:2321/SiebelDev/eMedicalObjMgr_enu) in 1 sec(s) GenericLog    GenericError    1    0    2004-10-15 10:41:46    (smconn.cpp (271) err=1801218 sys=2321) SBL-NET-01218: The connection was refused by server usdfswdsbl1. No component is listening on port 2321.
            *************

Also this log file has error
            ***************
GenericLog    GenericError    1    0    2004-10-15 11:18:34    (ssmsismgr.cpp (627) err=5600003 sys=0) SBL-SSM-00003: Error opening SISNAPI connection.
SessMgr    ConnOpen    3    0    2004-10-15 11:18:34     2076: [SESSMGR] Open(siebel.TCPIP.None.None://usdfswdsbl1:2321/SiebelDev/eMedicalObjMgr_enu, 60, 300) = [NULL, 5600003]
ObjMgrSessionLog    Error    1    0    2004-10-15 11:18:34    Login failed for Login name : sadmin
            *************

The root case of this behavior was determined as component “Siebel Connection Broker” which was not running. After we enabled the component and re-cycled the environment users were able to connect.

Applies to:

Siebel Life Sciences CRM - Version: 8.0.0.2 [20412] to 8.1.1.4 [21225] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 22-Mar-2011***

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:

Siebel CRM - Version: 8.1 [21039] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Server busy error with custom OM -ACSWMTObjMgr_enu

Symptoms

When try get the Siebel login by using custom component - customer Object Manager -ACSWMTObjMgr_enu ,we get following error

http://10.203.168.143/acswmt_enu/start.swe?" URL getting the following error message:
The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.[23:24:13]

In OM logs, these errors were found

 2009-10-11 23:07:37 Login failed for Login name : anonemp
 2009-10-11 23:07:39 (ctxtmgr.cpp (4504)) SBL-SVC-00208: Please login first

In SWSE logs, these errors where found

2009-10-11 22:53:16 ( (0) err=4653071 sys=0) SBL-SCB-00015: The component is down or not available on this server

2009-10-11 22:56:21 (smconn.cpp (283) err=1180866 sys=2321) SBL-NET-01218: The connection was refused by server hcmblysun004a. No component is listening on port 2321.

 2009-10-11 22:56:21 (ssmsismgr.cpp (773) err=3670019 sys=0) SBL-SSM-00003: Error opening SISNAPI connection.
 2009-10-11 22:56:21 (ssmsismgr.cpp (1761) err=3670022 sys=0) SBL-SSM-00006: Error while sending message to server.
 2009-10-11 22:56:21 (smconn.cpp (283) err=1180866 sys=2321) SBL-NET-01218: The connection was refused by server hcmblysun004a. No component is listening on port 2321.

Changes

Created custom Object manager -ACSWMTObjMgr_enu

Cause

Incorrect value for Siebel Repository File parameter


.

Solution

Setting the correct value for Siebel Repository File parameter resolved this issue. 

Applies to:

Siebel CRM - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 17-Feb-2012***

Symptoms

The Gateway daemon for Siebel Industry Applications version 8.1.1 running on IBM AIX 5.3 against Oracle 11g shows high CPU. This can be observed after starting a Siebel server, which has a duration of 2-3 minutes. After the Siebel server has started the CPU of the Gateway daemon reduces and stabilizes, however the Siebel Workflow components fail after startup. If these failed components are restarted manually via Siebel Server Manager then the CPU increases on the Gateway as before.

ERROR MESSAGES

1. SBL-DAT-00173: An invalid key was entered.
2. SBL-NET-01218: The connection was refused by server %1. No component is listening on port %2.
3. SBL-SRB-00040: Cannot open asynchronous SISNAPI connection.
4. SBL-GEN-05009: Unable to connect to the gateway server.
5. SBL-SVR-00052: Internal: Invalid proc handle

Cause

Issue caused by extremely large SIEBNS.DAT which can be seen by the high CPU in the gateway process originating from the reads performed by the NSClient.

Bug 10643323 has been logged to address a Product Enhancement Request so that the size of the SIEBNS.DAT does not grow excessively and if it does then to provide means to reduce the size - in particular removing event log level entries.

The large amounts of reads being performed by the NSClient are directly related to the high CPU observed on the gateway

Solution

To reduce the size of the SIEBNS.DAT, the following can be employed to resolve the issue:
1. Restore backup of SIEBNS.DAT after changing event log levels for large amount of server components
2. Remove unnessary component definitions

Applies to:

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

Symptoms

On : 8.1.1.3[21219] version, System Admin

When attempting to access the sales application after performing new installation of the siebel server on an existing enterprise, the connection to the application was unsuccessful. The login to the application was displaying the following error message:

The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.

The SWSE log displayed the following error message:

GenericLog GenericError 1 000000024d371324:0 2011-01-19 13:11:24 (smconn.cpp (283) err=1180866 sys=2320) SBL-NET-01218: The connection was refused by server hqsblt05. No component is listening on port 2320.
GenericLog GenericError 1 000000024d371324:0 2011-01-19 13:11:24 (ssmsismgr.cpp (626) err=3670019 sys=0) SBL-SSM-00003: Error opening SISNAPI connection.
ObjMgrSessionLog Error 1 000000024d371324:0 2011-01-19 13:11:24 Login failed for Login name : SADMIN

The eSales Object Manager (OM) displayed the following error message:

ObjMgrLog Error 1 0000000a4d2e0ad0:0 2011-01-13 07:17:54 (oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.
GenericLog GenericError 1 0000000a4d2e0ad0:0 2011-01-13 07:17:54 (secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00107) ORA-12154: TNS:could not resolve the connect identifier specified

The issue can be reproduced at will with the following steps:
1. Perform the siebel server configuration by adding a new server to an existing enterprise. Make sure that the existing siebel server in the enterprise was configured with a different DSN name.
2. Complete the installation and configuration of the siebel server using the configuration wizard.
3. Try to access the eSales application OM

Cause

The cause of the issue was determined to be with the DSN name entry for the Siebel enterprise which was pointing to the incorrect TNS names entry.

The original siebel server in the customer environment was first configured with sblt_internal and then changed. However, when the second siebel server was configured in the same enterprise, the default value during the siebel server configuration was taken which was "sblt_internal" and this was causing the problem. Once the DSN value was changed "SBA_81_TEST_DSN", the connection was successful and the application was accessible. The following error in the log justifies the fact that the issue was with the database connection and TNS names file:

ObjMgrLog Error 1 0000000a4d2e0ad0:0 2011-01-13 07:17:54 (oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.
GenericLog GenericError 1 0000000a4d2e0ad0:0 2011-01-13 07:17:54 (secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00107) ORA-12154: TNS:could not resolve the connect identifier specified

Also, looking into the siebns.dat file, the DSN name was incorrect as the value was pointing to "sblt_internal" which is an incorrect DSN pointing to a non-existent TNS names entry.

[/enterprises/SBA_81_TEST/parameters/Connect]
Persistence=full
Type=string
Value="sblt_internal"

Solution

The solution action plan for the issue is as below:

1. Perform the installation/configuration of the siebel server on the existing enterprise.
2. Make sure that the DSN name for the new siebel server configuration is the same as the existing siebel server on the enterprise.
3. Make sure that the tnsnames.ora file has the correct information pointing to the correct value pertaining to the DSN name that has been defined in the siebel configuration.
4. Once the configuration is completed, try to access the eSales application and make sure that the connection is established.

References

NOTE:476703.1 - What Are the Steps To Troubleshoot the Error Message: The Server You Are Accessing is Either Busy or Experiencing Difficulties...in a Siebel Web Client User Browser?
NOTE:507612.1 - ORA-12154: TNS:could not resolve service name