How To Troubleshoot Communications Session Manager Component Crashes (Doc ID 477860.1)

Purpose

This document describes how to troubleshoot the behavior where the Communications Session Manager (CommSessionMgr component alias) component process crashes.

When this type of behavior occurs the CommSessionMgr component will exit at the process associated to it can not be seem any more in the machine memory.

This behavior can be verified in Siebel Enterprise Server log file created in Siebel Server log folder with the name <Siebel Enterprise name>.<Siebel Server name>.log. If you inspect the log files you will see the CommSessionMgr component exiting with message similar to bellow:

SBL-OSD-00098 Process exited with error - Internal: The process exited abnormally and the Operating System could not get the exit code

SBL-OSD-01000 Process exited with error - Internal: The process attempted to read from or write to a virtual address for which it does not have the appropriate access

SBL-OSD-01018 Internal: The process/thread used up its stack (exception)

SBL-OSD-01014 Internal: The process attempted to execute an instruction whose operation is not allowed in the current machine mode

As an example, here is an extract from an Enterprise server log file:

ServerLog Startup 1 2004-02-26 09:44:13 Siebel Enterprise Applications Server is starting up
...
ServerLog ProcessCreate 1 2004-02-26 09:44:13 Created multithreaded server process (OS pid = 2428) for Communications Session Manager with task id 47107
...
ServerLog ProcessExit 1 2004-02-26 09:46:16 CommSessionMgr 47107 SBL-OSD-01000 Process exited with error - Internal: The process attempted to read from or write to a virtual address for which it does not have the appropriate access

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.