Services do not start and Event ID 7022 is logged in the System log in Windows NT 4.0, Windows 2000, or Windows Server 2003 (319127)
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows 2000 Server
- Microsoft Windows NT Server 4.0
This article was previously published under Q319127 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 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 SYMPTOMS
You may experience the following symptoms:
- When you start your computer, you may receive a message that states that one or more services did not start.
- If other users try to access your computer over the network, they may not be able to locate your computer.
- The following events may be logged in the System log:Event ID: 7022
Source: Service Control Manager Type: Error Description: Server service hung on startup.Event ID: 26 Source: Application Popup Type: Information Description: Application popup: Service Control Manager: At least one service or driver failed during system startup.Event ID: 7001 Source: Service Control Manager Type: Error Description: The Computer Browser service depends on the Server service which failed to start because of the following error: After starting, the service hung in a start-pending state.Event ID: 7001 Source: Service Control Manager Type: Error Description: The Distributed File System service depends on the Server service which failed to start because of the following error: After starting, the service hung in a start-pending state.
CAUSE
This issue may occur if the Spooler service tries to start before the Server service. This issue may occur if you installed either the Lexmark International Markvision (LexBce) service or the Hewlett-Packard JetAdmin port monitoring software on your computer.
RESOLUTIONWarning 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. To resolve this issue, edit the registry to make the Spooler service dependent on the Server service. If you do so, the Spooler service does not start until the Server service is running. To create this dependency:
- Click Start, and then click Run.
- In the Open box, type regedt32, and then click OK.
- Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler - Click Add Value on the Edit menu.
- Type DependOnService in the Value Name box.
- Click REG_MULTI_SZ in the Data Type box, and then click OK.
- Type LanmanServer in the Data box, and then click OK.
- Click Exit on the Registry menu to quit Registry Editor.
- Restart your computer.
| Modification Type: | Major | Last Reviewed: | 10/26/2005 |
|---|
| Keywords: | kberrmsg kbprb KB319127 |
|---|
|