System Log Event Logs
The following event logs relate specifically to the system log.
Cisco CallManager service terminated unexpectedly
The following error may appear if the Cisco CallManager service terminated unexpectedly.
This example shows that it has terminated unexpectedly 1 time(s), and the following corrective action of restarting the service will be taken in 60000 milliseconds.
Make sure that you are running the latest version of CallManager. If you don't have the latest version, view the Open Caveats and Resolved Caveats sections of the Release notes to see if you are experiencing a known problem.
If you need to upgrade the software, go to the Software Center for voice products.
If you need to escalate this issue to Cisco TAC, the following information will be needed:
CCM trace files—Located at C:\Program Files\Cisco\Trace\CCM
Provide trace files from 30 minutes before the crash and 15 minutes after the crash.
SDL (Signal Distribution Layer) trace files—Located at C:\Program Files\Cisco\Trace\SDL\CCM
Provide trace files from 30 minutes before the crash and 15 minutes after the crash. Go to Setting up Cisco CallManager Traces for the TAC for detailed information.
USER.DMP and DRWTSN32.LOG files—Located at C:\Documents and Settings\All Users\Documents\DrWatson
Ensure that the SdlMaxUnhandledExceptions service parameter is set to 0 (zero) for each CallManager.
Event logs—System and Application Event Logs
PerfMon logs—PerfMon counters/logs
Process:
% Processor Time/_Total
% Processor Time/ccm
Virtual Bytes/_Total
Private Bytes/_Total
Virtual Bytes/ccm
Private Bytes/ccm
