|
Home > Archive > Voice over IP Cisco > August 2005 > CCM service not starting on server bootup,
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CCM service not starting on server bootup,
|
|
| Erick Bergquist 2005-08-25, 2:45 am |
| 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
| |
| Eric Jones 2005-08-26, 2:45 am |
| 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@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Wes Sisk 2005-08-26, 2:45 am |
| 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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Eric Jones
Sent: Thursday, August 25, 2005 1:37 PM
To: cisco-voip@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@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Erick Bergquist 2005-08-26, 7:45 am |
| 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@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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf
> Of Eric Jones
> Sent: Thursday, August 25, 2005 1:37 PM
> To: cisco-voip@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@yahoo.com>
> wrote:
> of
> off
> 4-5
> up
> between
> start
> in
> timer.
> failure
> restart
> ________________________________________
____________
> page
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@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
| |
| Erick Bergquist 2005-08-26, 7:45 am |
| Wes, Thanks for the SQL tip. I have a SR on this also,
601931327 FYI. This is a single server cluster.
This is SQL related from what I am seeing in SQL
ERRORLOG, SQL is not ready until 5:25:21pm , but the
Call Manager service times out at 5:24:55 per event
logs.
2005-08-24 17:25:21.57 spid3 Recovery complete.
Looks like the MSDTC may not be started right away,
causing SQL to start late maybe -- error in log.
2005-08-24 17:24:24.71 server Attempting to
initialize Distributed Transaction Coordinator.
2005-08-24 17:24:34.51 server Failed to obtain
TransactionDispenserInterface: Result Code =
0x8004d01b
2005-08-24 17:24:35.78 spid3 Starting up database
'master'.
Thats 10 seconds there before it timeouts and starts
up databases...
=== Full SQL ERRORLOG attached
--- Wes Sisk <wsisk@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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf
> Of Eric Jones
> Sent: Thursday, August 25, 2005 1:37 PM
> To: cisco-voip@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@yahoo.com>
> wrote:
> of
> off
> 4-5
> up
> between
> start
> in
> timer.
> failure
> restart
> ________________________________________
____________
> page
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Wes Sisk 2005-08-26, 5:45 pm |
| did you check google or support.microsoft.com for the error message and
error code? groups.google.com appears to offer a few recommendations.
Looks like it could even be security related where a com+ object is failing
login. Any login failures in the security log? are all 'failure' audits
enabled?
/Wes
-----Original Message-----
From: Erick Bergquist [mailto:erickbe@yahoo.com]
Sent: Thursday, August 25, 2005 11:19 PM
To: Wes Sisk; Eric Jones; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] CCM service not starting on server bootup,
30000 timeout
Wes, Thanks for the SQL tip. I have a SR on this also,
601931327 FYI. This is a single server cluster.
This is SQL related from what I am seeing in SQL
ERRORLOG, SQL is not ready until 5:25:21pm , but the
Call Manager service times out at 5:24:55 per event
logs.
2005-08-24 17:25:21.57 spid3 Recovery complete.
Looks like the MSDTC may not be started right away,
causing SQL to start late maybe -- error in log.
2005-08-24 17:24:24.71 server Attempting to
initialize Distributed Transaction Coordinator.
2005-08-24 17:24:34.51 server Failed to obtain
TransactionDispenserInterface: Result Code =
0x8004d01b
2005-08-24 17:24:35.78 spid3 Starting up database
'master'.
Thats 10 seconds there before it timeouts and starts
up databases...
=== Full SQL ERRORLOG attached
--- Wes Sisk <wsisk@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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf
> Of Eric Jones
> Sent: Thursday, August 25, 2005 1:37 PM
> To: cisco-voip@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@yahoo.com>
> wrote:
> of
> off
> 4-5
> up
> between
> start
> in
> timer.
> failure
> restart
> ________________________________________
____________
> page
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Eric Jones 2005-08-26, 5:45 pm |
| 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/d...rol_utility.asp
If all else fails...have the server shot...
HTH,
-Eric
On 8/25/05, Erick Bergquist <erickbe@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@cisco.com> wrote:
>
>
>
>
>
> ________________________________________
____________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
| |
| Wes Sisk 2005-08-26, 5:45 pm |
| 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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Eric Jones
Sent: Friday, August 26, 2005 10:15 AM
To: cisco-voip@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/d...-us/tools/tools
/service_control_utility.asp
If all else fails...have the server shot...
HTH,
-Eric
On 8/25/05, Erick Bergquist <erickbe@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@cisco.com> wrote:
>
>
>
>
>
> ________________________________________
____________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Erick Bergquist 2005-08-26, 5:45 pm |
| Well, turns out the server had a SQL replication set
up that wasn't needed causing that other error it
looks like. We deleted the replication and are
scheduled to reboot the server over lunch to see if
the problem is fixed now.
I thought about adding SQL as a dependency also to CCM
service, but SQL can start up and be started but SQL
not be ready which is the case here so that would not
have helped I don't think. We may need to do that
depending on results of next reboot test.
--- Wes Sisk <wsisk@cisco.com> wrote:
> 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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf
> Of Eric Jones
> Sent: Friday, August 26, 2005 10:15 AM
> To: cisco-voip@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/d...-us/tools/tools
> /service_control_utility.asp
>
> If all else fails...have the server shot...
>
> HTH,
>
> -Eric
>
> On 8/25/05, Erick Bergquist <erickbe@yahoo.com>
> wrote:
> if
> They
> is
> not
> I'll
> reboot
> to
> disabled on
> set
> database
> and
> 12:10:34.26
> Behalf
> starting
> it
> takes
> the
> check
> what
> Keep
> this
> auto-restart
> but
> intervention.
> resolve
> gig
> not
> Have no
> server
> that
> a
> starts
> service
> start
> ________________________________________
____________
> ________________________________________
_______
> https://puck.nether.net/mailman/listinfo/cisco-voip
> https://puck.nether.net/mailman/listinfo/cisco-voip
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
____________
> page
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Erick Bergquist 2005-08-26, 5:45 pm |
| Rebooted and same problem.... same error in SQL
ERRORLOG when replication is gone. Co-worker suspects
soemthing within SQL is messed up and we are thinking
rebuild server now also.
We also discovered someone had done windowsupdate.com
on this awhile ago and download/installed patches that
way.
--- Erick Bergquist <erickbe@yahoo.com> wrote:
> Well, turns out the server had a SQL replication set
> up that wasn't needed causing that other error it
> looks like. We deleted the replication and are
> scheduled to reboot the server over lunch to see if
> the problem is fixed now.
>
> I thought about adding SQL as a dependency also to
> CCM
> service, but SQL can start up and be started but SQL
> not be ready which is the case here so that would
> not
> have helped I don't think. We may need to do that
> depending on results of next reboot test.
>
> --- Wes Sisk <wsisk@cisco.com> wrote:
>
> is
> to
> Behalf
> the
> long,
> find
> your
> not
> danger...you
> dependencies:
> is
> likely
>
http://msdn.microsoft.com/library/d...-us/tools/tools
> for
> service
> are
> also,
> completes
> if
> so
> can't
> scenarios
> <erickbe@yahoo.com>
> 2
> do
> service
> sequence
> traces
> don't
> windows
> to
> ________________________________________
____________
> home
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
_______
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
_______
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
____________
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ________________________________________
__________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Erick Bergquist 2005-08-27, 5:45 pm |
| Found out the full story on this one, server rebuild
is next.
The server was working fine and rebooted fine and
everything started up. Mid-July the customer had done
windowsupdate.com and ever since then the issue with
reboot was there (event log history shows this -
filtered on the errors). When they rebooted first
after windowsupdate.com ccm did not start, said a DLL
was missing. They had opened TAC case at time they
were having problems and were told to rebuild then but
didn't. They found the DLL somewhere else and copied
it over to the server and ccm started but not
automatically at boot. Then someone else had called
our group on this 2-3 weeks after that happened to see
if we could fix it, without telling us what went on
before.
--- Wes Sisk <wsisk@cisco.com> wrote:
> 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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf
> Of Eric Jones
> Sent: Friday, August 26, 2005 10:15 AM
> To: cisco-voip@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/d...-us/tools/tools
> /service_control_utility.asp
>
> If all else fails...have the server shot...
>
> HTH,
>
> -Eric
>
> On 8/25/05, Erick Bergquist <erickbe@yahoo.com>
> wrote:
> if
> They
> is
> not
> I'll
> reboot
> to
> disabled on
> set
> database
> and
> 12:10:34.26
> Behalf
> starting
> it
> takes
> the
> check
> what
> Keep
> this
> auto-restart
> but
> intervention.
> resolve
> gig
> not
> Have no
> server
> that
> a
> starts
> service
> start
> ________________________________________
____________
> ________________________________________
_______
> https://puck.nether.net/mailman/listinfo/cisco-voip
> https://puck.nether.net/mailman/listinfo/cisco-voip
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
____________
> page
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@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
|
|
|
|
|