Discussion Locked

rpcss.exe Session hangs server

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When I log in to my NT4 standalone server with sp5 on, the rpcss.exe process seems to hang up the server. The event id says: 7022 The RPC service hungs on startup. Need help with this one. Have reinstalled sp5.

5 replies

by brian

I think your problem is a variation of this resolution here. Look over this resolution and see if you can modify it. The RPC service may be trying to start but it needs another service to be up and running first, so it bombs out.
Try and find the service it needs to depend on. E-mail me back if it works or if not or if you need more help.

Event ID: 7022
Source: Service Control Manager
Type: Error
Description: Server service hung on startup.

To correct this problem:

Start the Server (RPC?) service manually and then verify connectivity with your network printers. If connectivity is not an issue, proceed with the following registry modifications.

Run Registry Editor (Regedt32.exe).

From the HKEY_LOCAL_MACHINE subtree, go to the following key:

\SYSTEM\CurrentControlSet\Services\Spooler

From the Edit menu, select Add Value.

Add the following:

Value Name: DependOnService
Data Type: REG_MULTI_SZ
Data: LanmanWorkstationLanmanServerLmHosts

NOTE: Indicates you should press ENTER on the keyboard

From the HKEY_LOCAL_MACHINE subtree, go to the following key:

\SYSTEM\CurrentControlSet\Services\NetLogon

Select the DependOnService entry

From the Edit menu, select Multi String.

Add the necessary services to make your data look like this:

Value Name: DependOnService
Data Type: REG_MULTI_SZ
Data: LanmanServer

Click OK and quit Registry Editor.

Shut down and restart Windows NT.

Addingthese lines holds the spooler service from loading until the LanmanWorkstation, LanmanServer, and LmHosts services have loaded and holds the netlogon service from loading until spooler, LanmanWorkstation, LanmanServer, and LmHosts has loaded.

Brian

This discussion is closed to new replies.