SQL Server 2005 Notification Services does not start successfully when you restart the computer (910892)
The information in this article applies to:
- Microsoft SQL Server 2005 Notification Services
- Microsoft SQL Server 2000 Notification Services
Bug #: 397119 (SQLBUDT) Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows registry SYMPTOMSConsider the following scenario. You set the Start Mode option for Microsoft SQL Server
2005 Notification Services to Automatic. You restart a computer that has SQL Server Notification Services
installed. In this scenario, SQL Server Notification Services does not start
successfully as expected, and the following messages are logged in the Application event log: Event Source: Service
Control Manager
Event Category: None
Event ID: 7000
Date:
Date
Time:
Time
Type: Error
User: N/A
Computer:
ComputerName
Description: The InstanceName
service failed to start due to the following error: The service did not respond
to the start or control request in a timely fashion. Event Source: Service Control Manager
Event Category:
None
Event ID: 7009
Date: Date
Time:
Time
Type: Error
User: N/A
Computer:
ComputerName
Description: Timeout (30000
milliseconds) waiting for the InstanceName service to connect.
This problem occurs when you configure SQL Server Notification Services to
use a local instance of the SQL Server service. CAUSEThis problem occurs because a required dependency is not
established automatically when you install SQL Server Notification Services. The startup
of SQL Server Notification Services depends on the SQL Server service. If the SQL Server
service is installed on the same computer, SQL Server Notification Services may start
before the SQL Server service is prepared. Therefore, Notification Services
cannot start successfully.WORKAROUNDTo work around this problem, use one of the following methods:
- Manually configure the dependency of SQL Server Notification Services
by running the following command at a command prompt:
sc config
NS$InstanceName depend =
SQLServiceName - NS$InstanceName represents the service name of SQL Server Notification Services.
SQLServiceName represents the service name
of the SQL Server service.
- On a computer that is running Microsoft Windows XP or Microsoft Windows Server 2003, the Service Configuration tool (Sc.exe) is included with the operating system. On a Windows 2000-based computer, the Service Configuration tool is not installed as a part of the operating system by default.
- Manually modify registry entries to create the dependency
of SQL Server Notification Services. To do this, follow these steps:
Warning Serious problems might occur if you modify the registry
incorrectly by using Registry Editor or by using another method. These problems
might require that you reinstall your operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at your own
risk.- Start Registry Editor.
- Locate the following
registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NS$InstanceName
- If a DependOnService registry entry already exists, double-click the DependOnService registry entry. Otherwise, create a DependOnService registry entry that has the REG_MULTI_SZ type, and then double-click the registry entry.
- Type the name of the SQL Server service in the
Value data box. For example, type MSSQLServer.
- Exit Registry Editor.
- Manually start SQL Server Notification Services after you restart the
computer.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 12/20/2005 |
|---|
| Keywords: | kbExpertiseAdvanced kbsql2005ns kbprb KB910892 kbAudDeveloper kbAudITPRO |
|---|
|