ccm service Unstable on Publisher

Unanswered Question
Jan 10th, 2008
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

We are experiencing a increasing frequency of crashes on our Publisher Call Manager of the Call Manager Service. This requires a manual restart of the service every time, and is becoming a cause of concern.

The system event log message is this:

The Cisco CallManager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

In regards to this I have followed up the advise given in the following article

However, it not resolved the issue.

Please note that the backups are done at 11.30pm. And no drwts32.log are being generated. Please advice how we can make the system more reliable.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
gogasca Wed, 01/16/2008 - 21:59
User Badges:
  • Green, 3000 points or more

For this type of problems please open a case with us to diagnose the issue.

Ayodeji Okanlawon Thu, 01/17/2008 - 09:48
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony


I have opened a TAC case on this.

The issue we have seen now is that the antivirus software running on the server was setup to run between 1am and 2am the time when the ccm service crashes.

This was also setup to use 100% of CPU. Hence CCM service is ben starved of resources.


chris.mann Thu, 01/17/2008 - 11:53
User Badges:

Make sure to setup exclusions in you AV software to not scan the program files/cisco folder. Also the trace directory, if you have moved it to the F: drive.

There is also a setting in Mcafee that will limit the amount of CPU utilized.

nmirzaeva Thu, 01/31/2008 - 01:14
User Badges:


we probably have the same problem but on subscriber.once we have to restart service. the latest record in drwts32.log was made one month earlier.

what about your SR in Cisco TAC? any suggestion from DE engineer?

Thanks in advance.

Ayodeji Okanlawon Thu, 01/31/2008 - 02:50
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony


This problem on our network was resolved using the perfmon....

The perfmon showed that scandisk was scheduled to run at 100% CPU utilization between 1am and 2am. (Hence starving Callmanager of resources and once call manager is starved of CPU for about 15s it crashes) These is usually the time that the crash occurs.

We then changed the setup for scan disk at this hour to use 60%.

This has resolved our problem.

I suggest you use perfmon to see whats running especially if drwts32.log does not show anything

nmirzaeva Mon, 02/04/2008 - 23:08
User Badges:

Hi, Aokanlawon!

Thank you for your reply! Unfortunately, we don't use AV on ccm server and maximum cpu load is up to 50%.

I think we need apply request in Cisco TAC.


This Discussion