Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Callmanager 4.1.2 After reboot the Callmanager Service Fails to Start

Hi, I upgraded the callmanager servers to the latest os release 2000.4.3a.sr5 and since then the callmanager service fails to start automatically i have to start the service manually after every reboot.Can anyone help

3 REPLIES
New Member

Re: Callmanager 4.1.2 After reboot the Callmanager Service Fails

I think this is related to CCM entries not getting DNS lookup replies quickly enough. Try entering the host names and all possibilities of dns suffixes into the hosts file.

Euan

New Member

Re: Callmanager 4.1.2 After reboot the Callmanager Service Fails

Hi,

If you still have this problem. You can try deactivating the "Callmanager" and then reactivate it again. By using the serviceability page in callmanager.

Also do you have CSA installed?

Hope this helps.

Robert

Green

Re: Callmanager 4.1.2 After reboot the Callmanager Service Fails

Hi Dave,

The service account for the CallManager service should be ".\CCMServiceRW" (under the "Log On" tab in the Properties for "Cisco CallManager" in services.msc).

Could you try the following on the PUBLISHER and check if it helps ...

Open registry editor and see if the key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout exists.

If the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 60000 in the Control key. To do so, follow these steps:

a. Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet

b. Click the Control subkey.

c. On the Edit menu, point to New, and then click DWORD Value.

d. Type ServicesPipeTimeout, and then press ENTER.

e. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.

f. Click Decimal.

g. 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.

This issue was generally seen with 2000.2.7 and 2000.4.1 and I suspect that this is a

symptom of the same issue in 2000.4.3a ....

CSCsb88052 -- CM service failed to start on boot with 2000.2.7SR8 or 2000.4.1

You can view this defect at the following link below ...

http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl

Please let me know if this resolves the issue

149
Views
15
Helpful
3
Replies