[cisco-voip] CCM service not starting on server bootup, 30000 timeout

[Wes Sisk]

nothing in the SDL traces either?

CM has to startup and read database. if SQL database and DBL are not up, CM
cannot start.  Is this the publisher or a subscriber?  turn dbl traces up to
detailed, do you have a dbl_ccm*.txt file in c:\prog\cisco\trace\dbl created
or updated in the time after the reboot?

also check the SQL server logs in C:\Program Files\Microsoft SQL
Server\MSSQL\LOG to see when recovery completes and SQL server is ready to
start accepting connections. "2005-08-24 12:10:34.26 spid3     Recovery
complete."


/Wes
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Eric Jones
Sent: Thursday, August 25, 2005 1:37 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM service not starting on server
bootup,30000 timeout


Sometimes a service times out while starting if it is dependent on
another service for starting and the other one takes too long.  That
may also explain why when you attempt to start the service after the
boot process is complete; it succeeds.

A couple of things you could do would be 1) check the service (if any)
upon which the CCM service depends.  Find out what may be causing that
service to take longer to start than normal.  Keep in mind that you
may find a hierarchy of service dependencies so this process may take
a while. Another thing you could do if you can't find the start-up
problem may be to set the service to auto-restart using the service
manager. This doesn't actually fix the problem but at least the OS
would restart the service w/o manual intervention.  I've used this
process in a number of problem service scenarios where the mystery
persisted or there was insufficient help to resolve the issue.

HTH,

-Eric

On 8/24/05, Erick Bergquist <erickbe at yahoo.com> wrote:
> Hi,
>
> Having issue on a CCM 4.02a SR1a server with 2 gig of
> DRAM recently installed, where the services do not
> start up on boot up reliably all the time. Have no
> problem manually starting the service.
>
> Since I've been working on this, if we shut server off
> then power it on, the ccm.exe is only service that
> doesn't start up. I've done the boot sequence a 4-5
> times or so and call manager service never starts up
> automatically. Nothing in CCM Detailed traces between
> shutdown and reboot, and new ccm traces don't start
> until the service is manually started.
>
> Only thing in event logs is under system, service
> control manager saids call manager did not start in
> timely manner and notes the 30sec (30000 ms) timer.
> Since it never started up on boot, the windows failure
> of service options did not kick in and try to restart
> service.
>
> OS is 2000.2-7sr6
>
> Any ideas?
>
>
>
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip