Server service hung on startup.

Issues and Solutions to problems found with Windows Server 2003

Moderator: stephen

Server service hung on startup.

Postby stephen » Fri Mar 05, 2010 5:56 am

I have a Windows 2000 server running in a Hyper-V virtual computer on a Server 2008

When the server 2000 is restarted it stops at a blue screen
Checking the Event Viewer shows the Server service hung on startup
I found this article on Microsoft
http://support.microsoft.com/kb/319127
To set the Dependancy of the Spooler service to be dependent on LanmanServer
My registry entry had the RPCSS as the DependOnService entry

So I am going to remove the RPCSS entry and replace it with LanmanServer


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.

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:

1. Click Start, and then click Run.
2. In the Open box, type regedt32, and then click OK.
3. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler
4. Click Add Value on the Edit menu.
5. Type DependOnService in the Value Name box.
6. Click REG_MULTI_SZ in the Data Type box, and then click OK.
7. Type LanmanServer in the Data box, and then click OK.
8. Click Exit on the Registry menu to quit Registry Editor.
9. Restart your computer.
stephen
 
Posts: 507
Joined: Thu Feb 09, 2006 9:37 am
Location: Brisbane

Return to Windsows Server 2003 Issues

Who is online

Users browsing this forum: No registered users and 2 guests

cron