Deadlock in Service Control Manager During System Shut Down
Last reviewed: February 5, 1999 |
The information in this article applies to:
SYMPTOMSWhen a system with many services shuts down, Windows NT may hang (stop responding) for two minutes and then continue. If the WaitToKillService setting in the registry is less than that, it is possible the system will shut down without sending a shutdown notification to some services. This creates the possibility of corrupted data stores. NOTE: This problem has only been observed with Cheyenne ARCServe, but this is not a problem with ARCServe.
CAUSEService Control Manager (SCM) uses Named Pipes to talk to services. The services report status changes via Remote Procedure Calls (RPC) to SCM. Because of the way SCM uses two synchronization objects, there is a race condition which can cause a deadlock.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT version 4.0. For more information, please see the following article in the Microsoft Knowledge Base.
ARTICLE-ID: Q152734 TITLE : How to Obtain the Latest Windows NT 4.0 Service PackNOTE: The files included with this hotfix are system files. You must use Mv.exe /x /d from the Windows NT Resource Kit to overwrite the files.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.
|
Additional query words: sbs slow shutdown |
Last reviewed: February 5, 1999
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.