ccmcrash - Cisco CallManager Service Crash Document ID:...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Cisco CallManager Service Crash Document ID: 19122 Introduction Prerequisites Requirements Components Used Conventions Cisco CallManager Service Crash Description Determine the Type of Crash Information to Gather and Provide to Cisco Technical Support Unexpected Event Crash Lack of Resource Crash Check Settings on Backup Utility to Avoid High CPU Intercluster Routing Loops Can Cause High CPU Spikes Set Up Performance Monitor Counter Logs Related Information Introduction This document provides information about a Cisco CallManager crash, how to determine if you have experienced a crash, the information to gather and provide to the Cisco Technical Support, and how to search for Cisco CallManager crash bugs that exist. Prerequisites Requirements There are no specific requirements for this document. Components Used This document is not restricted to specific software and hardware versions. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Cisco CallManager Service Crash Description When the Cisco CallManager service (ccm.exe) crashes, you see this message in the System Event log: The Cisco CallManager service terminated unexpectedly. It has done this 1 time. The following corrective action will be taken in 60000 ms. Restart the service. Other messages you can see in the event of a crash are: Cisco - Cisco CallManager Service Crash
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Timeout 3000 milliseconds waiting for Cisco CallManager service to connect. The Cisco CallManager failed to start due to the following error. The service did not respond to the start or control request in a timely fashion. At this time, when devices like Cisco IP Phones and gateways unregister from the Cisco CallManager, users experience delayed dial tone, and/or the Cisco CallManager server freezes due to high CPU. Refer to Cisco CallManager Event Logs for event log messages not included here. The Cisco CallManager service can crash due to one of these reasons: An unexpected event occurs in the Cisco CallManager service. This crash adds an entry to the Dr.Watson log that exists and a User.dmp is generated in the folder C:\Documents and Settings\All Users\Documents\DrWatson. 1. The Cisco CallManager service does not have enough resources like CPU or memory in order to function. Generally, the CPU utilization in the server is at 100 percent at that time. 2. Dependent on the type of crash you experience, you need to gather different data that helps you and Cisco Technical Support determine the root cause of the crash. Determine the Type of Crash If you perform a search on your Cisco CallManager after the crash for a file called Drwtsn32.log and open it, look at the most recent entry in order to see if an entry for the ccm.exe has been added. Open the Dr. Watson log in Notepad, go to the bottom of the file and search for Application exception occurred , which takes you to the latest crash. This is an example of header for a crash entry in drwtsn32.log.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/08/2011 for the course CISCO 1232 taught by Professor Jack during the Spring '11 term at American International.

Page1 / 7

ccmcrash - Cisco CallManager Service Crash Document ID:...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online