You cannot use the Service Control snap-in to stop the SMS_Executive service (886130)


The information in this article applies to:

  • Microsoft Systems Management Server 2003
  • Microsoft Systems Management Server 2003 SP1

SYMPTOMS

If you try use the Service Control snap-in to stop the SMS_Executive service, the SMS_Executive service does not stop, and you receive the following error message:
Could not stop the SMS_EXECUTIVE service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
This symptom occurs after you have stopped the MSSQLSERVER service.

CAUSE

This issue occurs because the SMS_Executive service relies on the MSSQLSERVER service. Therefore, you cannot stop the SMS_Executive service if the MSSQLSERVER service has been stopped.

WORKAROUND

To work around this issue, restart the MSSQLSERVER service to stop the SMS_Executive service.

Important We recommend that you always stop the following services before you stop the MSSQLSERVER service or perform a Microsoft SQL Server upgrade:
  • SMS_SITE_COMPONENT_MANAGER
  • SMS_Executive
  • SMS_SQL_MONITOR

MORE INFORMATION

When you issue a stop command with the Microsoft Management Console (MMC) Service Control snap-in, the pop-up window starts a timer that is hard-coded at 125 seconds. If the service has not stopped in 125 seconds, the user interface generates the error message that is listed earlier in this article, but the service continues to stop. After the service has stopped, the status for the service in the Service Control snap-in updates from stopping to blank, and blank represents stopped.
Modification Type:MinorLast Reviewed:6/14/2005
Keywords:kbsmsAdmin kbSMS2003spfix kbSMS2003bug KB886130 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.