Siebel Administration >  SBL-SMI-00033: The client exited without closing the SISNAPI connection

SBL-SMI-00033: The client exited without closing the SISNAPI connection

This is an error reported at times when an established connection with a Siebel application server or server component is abruptly terminated. The error message(s) below are usually reported along side the above error. SVR-01014 : Internal: Could not send the HELLO message: (null)
SMI-00033: The client exited without closing the SISNAPI connection
SRB-00041 : can't do SISNAPI handshake
SRB-00040 : can't open asynchronous SISNAPI connection

Note: SISNAPI is Siebel's internal communication protocol. An error in this layer generally means that communication between the Siebel entities involved failed.

Cause

1. As stated above, the error indicates an abrupt termination of communication channels between two Siebel entities such as an improper/sudden shut down of services, or killing a process outside of the Siebel environment in a non-standard manner. Example – a Siebel administrator ends his command line "srvrmgr" session by simply closing his DOS window (or telnet session in case of UNIX) rather than issuing an "exit" command at the "srvrmgr" prompt for a graceful exit.

2. Incorrect security adapter settings.

3. invalid user credentials.

Diagnostic Steps

1. Since this error is rather generic and reported for all abrupt SISNAPI termination's, its important to identify the context in which it is reported and the accompanying error message(s). These are what should be investigated to troubleshoot the specific problem at hand.

2. Check your Security Adapter settings/parameters.

Solution

1. Not applicable. Nevertheless following appropriate shutdown and graceful application exit procedures should minimize the more generic occurrences of this error message.

2. Correct the credential of your Security Adapter especially Custom and non DB authentication.