An Access Violation Occurs in the Messenger Service During Shutdown (303720)
The information in this article applies to:
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q303720 SYMPTOMS
During shutdown, the Messenger service may generate an access violation or may stop responding (hang). The problem in the Messenger service is typically in Msgsvc.dll, which runs under Services.exe.
CAUSE
When the Messenger service receives a shutdown request (a service stop), resources are deleted as follows:
- DisplayThread termination
- CriticalSection object MsgDisplayCriticalSection (for display thread) deletion
- RPC I/F deletion
If the Messenger API is called between the second and third items by any threads, the Messenger service can call the EnterCriticalSection function with a deleted object. After RPC I/F is deleted, display-related resources (the first two items) should be deleted.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform
------------------------------------------------
01-Aug-2001 15:13 39,184 Msgsvc.dll x86
NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB303720 |
---|
|