Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
After OS is upgraded to any version between 2000.2.7SR8 to 2000.4.2, the Cisco CallManager service (ccm.exe) fails to start when the server is rebooted. The "at least one service or drive fail during system startup" error message appears on server bootup.
After OS is upgraded to any version between 2000.2.7SR8 to 2000.4.2, the Cisco CallManager service (ccm.exe) fails to start when the server is rebooted. The "at least one service or drive fail during system startup" error message appears on server bootup. In application event log, the "The Cisco Call Manager service did not respond to the start or control request in a timely fashion" and "Timeout (45000) miliseconds waiting for the Cisco Call Manager service to connect" error messages appear
When you check the event viewer, you see these error messages in the application log:
Type : error , with description : Timeout (30000 miliseconds) waiting for the cisco callmanager service to connect.
The Cisco Call Manager service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Once the OS is booted completely and you are logged on, you can start the ccm.exe service manually from control center page, but it does not start automatically when you reboot the server.
This issue is observed on the low end servers that have CPU typically less than 3.0 Gig and memory less than 2 Gigs. This issue does not happen on High end servers like the 7835 and 7845 line of servers.
This problem is tracked in Cisco bug ID CSCsb88052.
As a workaround, you need to manually start Cisco CallManager from the service control manager or the Cisco CallManager admin pages.
You can also try this other option. In the registry, if the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 60000 in the Control key.
Complete these steps in order to do so:
Locate and then choose this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
Choose the Control subkey.
In Edit, point to New, and then click DWORD Value.
Type ServicesPipeTimeout, and then choose ENTER.
Right-click the ServicesPipeTimeout DWORD value, and then choose Modify.
Type a value of 60000, and then click OK.
The value is 60000 milliseconds and is equivalent to 60 seconds or to one minute.
Note: This change does not take effect until the computer is restarted.