PRB: Demand-started Service Causes Machine to Hang

 Last reviewed: December 17, 1996
Article ID: Q152661
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 kb3rdparty kbprb
KBSubcategory: bseService



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 17, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.