 |
 |
| Siebel Administration > SBL-NET-01201 Internal: connect() failed: %1
SBL-NET-01201 Internal: connect() failed: %1 This error message is generally reported when a connection attempt fails. This connection could have been between user and component or component and component. "%1" usually contains a more indicative cause for failure. At times, an additional error message is also generated that accompanies it. The supporting error message(s) hold valuable context information that can assist in the troubleshooting process. For example: NET-01201: Internal: connect() failed: Connection timed out. Cause In general, the cause for being unable to connect could range from: Incorrect connect strings maintained in the eapps.cfg (such as wrong hostname, IP address, port # etc.) Connectivity issues between the various Siebel entities (such as if there is any firewall presence in between the entities initiating and responding to the connectivity request that might prevent the request from getting thru (or) referring a machine with its internal IP address from outside of a firewall when Network Address Translation (NAT) is enabled.) If Resonate is in the mix, incorrect settings on Resonate related parameters could affect connection requests (due to timeouts). Diagnostic Steps Identifying the two entities involved is critical to resolving the cause for this error message. Identify the log file in which the error was reported (that would be the request initiator), then work to identify the target component. In the above example, this error was reported in the local client side log (with enhanced tracing). The user was attempting to open a file attachment when he encountered the error. Siebel components are registered with the Siebel Gateway Server when the service starts up. When the Siebel Dedicated Web Client attempts to view an attachment, it connects to the Siebel Gateway Server in order to obtain the Siebel Server connect string where File System Manager (FSM) is running. This connect string is used to contact the FSM on the said Siebel Server. Hence the initiator would be "Siebel Dedicated Web Client", and the target component is the FSM component. Identify the details of the connection, so as to validate them. The SISNAPI connect string for this Siebel Server contained an internal IP address of the Siebel Server. Since the dedicated web client was outside of the firewall, and NAT was in place the request failed on account of an invalid IP address (as the internal IP address is not recognizable outside of the firewall). Solution Validate and correct the connectivity details, this should ensure that the connection attempt is successful.
|
|