General discussion

Locked

Win Sock error in Win 2000

By mdessaint ·
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event I 3
Date: 12/18/2000
Time: 2:02:56 PM
User: N/A
Computer: MSD
Description:
Application [svchost.exe]. 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.

The error is showing up on the win 2000 client, the server is running NT 4.0, Proxy 2.0.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Win Sock error in Win 2000

by lemmonr In reply to Win Sock error in Win 200 ...

Found this, see if it helps:

CAUSE
This behavior can occur when a service that requires the NTLM Security Service Provider (NTMLSSP) service to operate is loaded before NTLMSSP has started. To prevent the Service Control Manager from locking, the service is temporarily unable to make remote calls. The service can be manually started without error after the NTLMSSP has loaded.


RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

To resolve this behavior, follow these steps:


Start Registry Editor (Regedt32.exe).


Locate and click the key for the service name indicated in the Event Viewer error messages:


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\FailedServiceName
NOTE: Match the .exe file listed in the Type field of the Event Viewer message to the ImagePath value of the registry key.


Add the following value:

Value Name: DependOnService
Data Type: REG_MULTI_SZ
Value: NtLmSsp

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.

Collapse -

Win Sock error in Win 2000

by mdessaint In reply to Win Sock error in Win 200 ...

Thank You that gave me the missing piece of the puzzle

Collapse -

Win Sock error in Win 2000

by mdessaint In reply to Win Sock error in Win 200 ...

This question was closed by the author

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums