PRB: Demand-started Service Causes Machine to Hang

ID: Q152661

3.50 3.51 WINDOWS NT kbprg kbprb

The information in this article applies to:

• Microsoft Win32 Application Programming Interface (API) included with:

      - Microsoft Windows NT versions 3.51 and 4.00
  

SYMPTOMS

A service is specified to start in the security context of a user. When the service is auto-started, it starts correctly. If it is demand-started (by the StartService API), the machine hangs. This state is demonstrated by the operating system becoming unresponsive. If you are starting the service from the service control panel applet, the hour-glass cursor fails to appear or, after a long delay, the "Attempting to Start Service" dialog box appears.

CAUSE

The problem is caused by an incorrectly written third-party network provider. The service control manager must check with each installed network provider in order to authenticate that the user name and password for the service are valid. If a network provider has trouble validating the user's credentials, the service control manager fails to start the service.

RESOLUTION

Remove the third-party network provider from the system. Please refer to your network provider documentation for more information on how to remove it from the system. Contact the network provider vendor for an update that resolves the problem.

STATUS

This behavior is by design.

Additional reference words: 3.50 3.51 KBCategory: kbprg kbprb KBSubcategory: bseService

Keywords          : kb3rdparty kbKernBase kbService kbGrpKernBase 
Version           : 3.50 3.51
Platform          : NT WINDOWS

Last Reviewed: May 14, 1998