Siebel server process exiting with SBL-GEN error code due to Mainwin regss crash
(Doc ID 1543544.1)
Last updated on SEPTEMBER 22, 2017
Applies to:Siebel CRM - Version 8.1  and later
All of a sudden Siebel component processes terminating with a random SBL-GEN- codes.
The enterprise log slows a slew of process exits and process errors leading to shared memory errors. Below are the errors:
(scirkey.cpp (1142) err=1310772 sys=0) SBL-SVR-00052: Internal: Invalid proc handle SBL-GEN-00001 Process ***** exited with error -
SBL-GEN-00001 Process 31889 exited with error -
SBL-GEN-00007 Process 8962 exited with error -
SBL-SMI-00062 Process 25198 exited with error - Internal: No more process (multithreaded server) slots available
SBL-SVR-09127 Process 31150 exited with error - Internal: Fail to initialize the shared memory resource for the process.
- Siebel Application Server seems to have crashed.
- No core files were created in the Siebel server/bin directory
- No fdr files were created.
*** Server recovered without any action/restarts.
This crash usually happens after a few weeks uptime of regss.
This behavior has only been observed for the Linux platform.
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