Search This Blog

SBL-GEN-00127 Process 1865 exited with error

Applies to:

Siebel CRM - Version [21225] and later
Linux x86-64


 You are running a Siebel version or above on a Linux 64-bit (x86_64) system.

During server startup you will see lots of errors like this in the enterprise log file:

ServerLog    ProcessExit    1    0000fa204f977fee:0    2012-04-24 16:13:00    WfProcMgr     1865     SBL-GEN-00127   Process 1865 exited with error -

This occurs for almost all components and they are shown as unavailable in the srvrmgr.

Core dumps are generated with the following file information:

$ file core.4681
core.4681: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'siebmtshw'

Note the ELF 64-bit signature. Since all siebel binaries are 32-bit, it is clear that this core is caused by the operating system shell, which runs as 64-bit on a 64-bit platform.


 This error message is caused by a core dump of the siebmtshw or siebprocmw shell script. This script is crashing when it is sourcing the setmwruntime sub script. The setmwruntime script sets a few environment variables for the Mainwin subsystem.


 This crash has been observed for some version of Red Hat Linux 64-bit. At the moment it is not clear which particular Linux setup is responsible for this crash. Customers experiencing this crash should send the core dump of the shell script to Red Hat support.

The following workaround will enable the startup on such systems:

Edit the file $SIEBEL_ROOT/mw/setmwruntime:

Comment out the following lines:

Line 131:

#PATH=`echo :$PATH | sed "s,:${MWHOME},:@${MWHOME},g" | sed "s,:\([^@]\),:${new_path}:\1,"|sed -e 's,:@,:,g' -e 's,^:,,'`

Lines 148-150:

#if [ "${MWOS}" = "aix4" -o "${MWOS}" = "linux" ]; then
#    LIBPATH=`echo $LIBPATH |tr ":" "\012"|grep -v '^/usr/lib$'|tr "\012" ":"`

The modification done in these lines is not really necessary in Siebel context.

Then the next startup of the siebel service is successful and no more core dumps are observed.


  1. Thanks so much for the post. This helped me get WfProcMgr working in my setup which was constantly crashing.

  2. Thanks a lot, it saved my day.