Applies to:
Siebel Insurance CRM Service, SPE - Version: 7.8.2.4 [19224] and later [Release: V7 and later ]Information in this document applies to any platform.
Symptoms
When stopping Siebel Server, many error happened as follows,SBL-SMI-00049 Gateway connection error when shutting down the Siebel Server.
Cause
When stopping Siebel Server, siebctl directs the components to be shutdown and waits for the end for 2 min(default). But some components don't stop in time. Then, siebctl kills them.
At this time, the connection to the Gateway Server from the component is closed, and as the result the error SBL-SMI-00049 situation is happened and is written in the enterprise log.
Solution
This error is harmless, you can ignore this error.Or before stopping the Siebel Server, stop the components via srvrmgr and check the component status if they are changed into "Shutdown".
This symptom is registered as CR# 10643122.
References
BUG:10643122 - [CR#12-1RUP03P][FR#12-1RUP04C] SBL-SMI-00049 GATEWAY CONNECTION ERROR WHEN SHUTTApplies to:
Siebel System Software - Version: 7.7.1 [18306] and later [Release: V7 and later ]Information in this document applies to any platform.
Error Message Area:Server Management Infrastructure - SMI
Version:Siebel 7.7
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SMI-00049: Internal: There is no connection to the gateway serverScope
This document is informational and intended for any user.SBL-SMI-00049: Internal: There is no connection to the gateway server
Explanation
The connection to Siebel Gateway Server has been lost. This can be caused by the Siebel Gateway Server process being stopped, the machine hosting the Siebel Gateway Server being shutdown, or a network problem between the Siebel Gateway Server machine and the machine that hosts the component that throws this error message.Corrective Action
Verify that the machine where the error appears can connect to the Siebel Gateway Server machine over the network by pinging it. Also verify that the Siebel Gateway Server process is running and that each part of the infrastructure is using the same build and version of the application software. This error may be expected if the Siebel Server and Siebel Gateway Server are stopped in rapid succession where some components on the Siebel Server are not stopped before the Siebel Gateway Server is stopped. In this case, no action is required.Applies to:
Siebel System Software - Version: 7.8.2 [19213] and later [Release: V7 and later ]Information in this document applies to any platform.
Error Message Area:Server Management Infrastructure - SMI
Version:Siebel 7.8
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SMI-00049: Internal: There is no connection to the gateway serverScope
This document is informational and intended for any user.SBL-SMI-00049: Internal: There is no connection to the gateway server
Explanation
Connection to Siebel Gateway is lost.Corrective Action
Check to see if the Siebel Gateway is running and configured properly.Applies to:
Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]Information in this document applies to any platform.
Error Message Area:Server Management Infrastructure - SMI
Version:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SMI-00049: Internal: There is no connection to the gateway serverScope
This document is informational and intended for any user.SBL-SMI-00049: Internal: There is no connection to the gateway server
Explanation
The connection to Siebel Gateway Server has been lost. This can be caused by the Siebel Gateway Server process being stopped, the machine hosting the Siebel Gateway Server being shutdown, or a network problem between the Siebel Gateway Server machine and the machine that hosts the component that throws this error message.Corrective Action
Verify that the machine where the error appears can connect to the Siebel Gateway Server machine over the network by pinging it. Also verify that the Siebel Gateway Server process is running and that each part of the infrastructure is using the same build and version of the application software. This error may be expected if the Siebel Server and Siebel Gateway Server are stopped in rapid succession where some components on the Siebel Server are not stopped before the Siebel Gateway Server is stopped. In this case, no action is required.Applies to:
Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]Information in this document applies to any platform.
Error Message Area:Server Management Infrastructure - SMI
Version:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SMI-00046: The port %1 is already in useScope
This document is informational and intended for any user.SBL-SMI-00046: The port %1 is already in use
Explanation
The Siebel Server is unable to create the configured listening port. This can happen when multiple server components have the same value specified for the Static Port Number parameter.Corrective Action
If there is a specific server component that encounters this error message, check the value for the Static Port Number parameter and make sure that it is not the same value specified by any other component. Also, validate that the port is not in use by another application.Applies to:
Product Release: V7 (Enterprise)Version: 7.5.2.217 [16085]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1142460547.
Symptoms
SBL-SVR-01004, SBL-SMI-00049But we do notice whenever we stop the Siebel service, the service took a long time (1~2 minutes) to stop and most of cases we got the following message“Could not stop the Siebel Server from local Computer, Error 1053: The service did not respond to the start or control request in a timely fashion.”
We have FINSOBJMGR_ENU and FINSOBJMGR_FRA running on each OM server. The min and max MT server for ENU are 7 and for FRA are 3. Each server has 8GB physical memory and 16GB paging size.
Is that possible the Siebel service cannot stop in certain time and then fail to remove the component rules from Resonate?
Solution
Message 1
For the benefit of other users:If the object managers are busy at shutdown they cannot gracefully terminate and remove their corresponding rules from Resonate (e.g. under UNIX if you force the shutdown this will almost always be the case). Here are some guidelines to reduce the time necessary to stop the Siebel servers
1) Before shutting down the Siebel application server shutdown web servers first. If the seb servers are shutdown there will be no further traffic to the object managers during shutdown.
2) Define a process that deletes all rules from Resonate each time you bring down your environment (fail safe procedure). This is done automatically at startup by the Siebel server, but you will not run into issues with having this in place (e.g. import an empty rules file, see below).
Probably the easiest way to remove all rules from Resonate during restart is importing an empty rule file from command line e.g.:
CDAction -p 2101 localhost <PASSWORD> load_rules empty.dat
CDAction is located in the Resonate bin folder and this should be performed on the primary scheduler. Please keep in mind that this will delete all rules and should not be done on a site that is in use.
The empty rules (empty.dat) file will look like this:
-----
VERSION(3.2)
COMMENT(DATE 12/08/2003 02:30:06 PM)
-----
[..]
Message 2
You can create such a file by starting Central Dispatch (GUI) > Scheduling Rules > Management > Save Scheduling Rules. Then deletes everything apart from the first two lines so that the file looks like the above sample.Thanks
No comments:
Post a Comment