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

Fri Aug 26 10:39:24 EDT 2005

Agreed.  The real question appears to be why DTC is not available when SQL
attempts to connect.  Does it have all OS patches to avoid all virus fun?
Either troubleshoot that or rebuild from the OS up and restore from backup.

/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: Friday, August 26, 2005 10:15 AM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM service not starting on server
bootup,30000 timeout

Erick, your co-worker is absolutely right about the restart options.
I glazed over the fact that the service was never actually starting
even once.

On the note about the SQL start-up taking too long, I think Wes has
you in the right direction with SQL. If you can find out what is
taking SQL so long to start you'll likely have your answer.

If the root cause of the SQL start-up delay can not be resolved then
here is an alternative.  I have to stress that although this alternate
course of action does not pose any real danger...you should never
*need* to do this on a properly working CM server.

With that said, going back to service dependencies: If CCM simply will
not start w/o being able to successfully log into SQL *and* you are
certain that the CM service can log into SQL and start successfully
once SQL is properly started then... You could set the SQL Server
Service as a dependency for the CM service.  This is done by issuing
the following command:

sc config "Cisco CallManager" depend= rpcss/MSSQLSERVER

The SC command is located in the Windows 2000 Resource Kit. The link
below explains the SC command. You co-worker likely already has this
in his arsenal of tools.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/tools
/service_control_utility.asp

If all else fails...have the server shot...

HTH,

-Eric

On 8/25/05, Erick Bergquist <erickbe at yahoo.com> wrote:
> I will check out these files also, thanks.
>
> Eric, The auto-restart/failure (3 options)
> configuration on the service properties tab is for if
> the service were to fail/terminate unexpectedly. They
> are set to restart 3 times, but since the service is
> not starting to begin with the failure options are not
> used I'm being told by a co-worker with MCSE.
>
> I've already disabled all optional-type services
> (TAPS,  CRA, IPMA, WebDialer) and same problem. I'll
> have to check the DBL traces and SQL logs and reboot
> again if they weren't set.
>
> I think it's more of a general windows issue also,
> because they had the Utility Manager service set to
> automatic and it failed to start also. Comparing
> against other ccm servers this service was disabled on
> all others I've looked at so not sure why it was set
> to automatic.
>
>
> --- Wes Sisk <wsisk at cisco.com> wrote:
>
> > 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
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
>
>
> ____________________________________________________
> 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