S
Spin
Gurus,
How can I stop these warnings from appearing in my Event Logs? By making
these services depend on NtLmSsp perhaps?
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:17:02 PM
User: N/A
Computer: XP
Description:
Application [alg.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.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:16:56 PM
User: N/A
Computer: XP
Description:
Application [rtvscan.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.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:16:55 PM
User: N/A
Computer: XP
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.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:16:53 PM
User: N/A
Computer: XP
Description:
Application [lsass.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.
--
How can I stop these warnings from appearing in my Event Logs? By making
these services depend on NtLmSsp perhaps?
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:17:02 PM
User: N/A
Computer: XP
Description:
Application [alg.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.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:16:56 PM
User: N/A
Computer: XP
Description:
Application [rtvscan.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.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:16:55 PM
User: N/A
Computer: XP
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.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 9/18/2003
Time: 12:16:53 PM
User: N/A
Computer: XP
Description:
Application [lsass.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.
--