SBL-NET-01034: Siebel Environment Stops Responding Abruptly And All Logged In Users Are Kicked Out.
(Doc ID 1107433.1)
Last updated on JULY 31, 2017
Applies to:Siebel Finance Sales - Version 18.104.22.168 SIA  to 22.214.171.124 SIA [Release V8]
Information in this document applies to any platform.
***Checked for relevance on 31-JUL-2017***
The customer upgraded their application from 126.96.36.199 to 188.8.131.52 and experienced the following issues:
a) The OM (Object Manager) stopped responding from time to time.
b) All the logged in users were kicked out and no user could login thereafter. The server busy error message was encountered and the workaround was to restart the OM.
There were no exact sequence of steps to reproduce this issue. The error was intermittent and was happening occasionally and whenever it happened, it kicked out users and then no user could login.
The OM logs showed the following error:
SBL-NET-01034: The SISNAPI connection was closed by the peer
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document