Discussion Locked

Service manager and NtLmSsp not running

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I get a serive or driver failed during start up and this tis the error reported in Event Viewer: The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.

7 replies

by jkrowiak

This happened to me with several services after applying service packs or loading software. You need to make the service that failed dependent on NtLmSsp (search for article Q268009 at www.microsoft.com/technet.)
Here's the basic steps: Find out what serice failed, then

1. Start Registry Editor (Regedt32.exe).

2. Locate and click the key for the service name indicated in the Event Viewer
error messages:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
NOTE: Match the .exe file listed in the Type field of the Event Viewer message to
the ImagePath value of the registry key.

3. Add the following value:

Value Name: DependOnService
Data Type: REG_MULTI_SZ
Value: NtLmSsp

4. Click OK to save the values.

When you add this value, the service waits until the NTLMSSP service starts. If
the NTLMSSP service has not started, this configuration starts the NTLMSSP
service before it starts the other services.

by james_randy

That was a very thoughtful and thorough first answer. Why don't you go ahead and accept that answer and close the question.

by james_randy

That was a very thoughtful and thorough first answer. Why don't you go ahead and accept that answer and close the question.

This discussion is closed to new replies.