Microsoft KB Archive/811683

= SMS: Access Violation in WUSER32 When the Service Is Shutting Down. =

Article ID: 811683

Article Last Modified on 10/25/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition
 * Microsoft Systems Management Server 2.0 Service Pack 1
 * Microsoft Systems Management Server 2.0 Service Pack 2
 * Microsoft Systems Management Server 2.0 Service Pack 3
 * Microsoft Systems Management Server 2.0 Service Pack 4

-





SYMPTOMS
The Systems Management Server (SMS) Remote Tools Client Agent service (Wuser32.EXE) may occasionally cause an access violation exception to occur when the service or threads in the service are stopped. For example, you may receive an access violation exception when the Client Configuration Installation Manager (CCIM) component cycle occurs. If you have followed the Microsoft Knowledge Base article 195859 to turn on logging for WUSER32, the following sequence of log entries is typically recorded in the Wuser32.log file:   Desktop change Thread terminating from event 1 ** TCPStreamViewee Thread terminating ** Threads gone** NOT IsWindow: ghwndDlg (x00030058) NOT IsWindow: ghwndParent (x00000000) Destroying ghwndInvisible Destroying ghwndVisWndParent Clean up security FreeSecurityInfoList Desktop change thread 1560 terminating The order of the various log entries may vary, but the last line is always the same.

Note: There is an exception to this rule. In the last line, the actual thread ID may vary. In this example, it is 1560.



CAUSE
This problem occurs because the SMS Remote Tools Client Agent service (Remote Control component) cannot correctly stop all of its threads.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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. To resolve this problem, use one of the following methods:  Install the SMS Service Pack 4 hotfix that is described in Microsoft Knowledge Base article 329079.

For additional information about how to obtain this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

329079 SMS: User32.dll Initialization Error When Screen Saver Activates

-or- Install SMS Service Pack 5. To resolve this problem, obtain the latest service pack for Systems Management Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

288239 How to Obtain the Latest Systems Management Server 2.0 Service Pack





STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
If you are experiencing this problem, if you analyze a user dump file from Dr. Watson, you receive a stack trace similar to the following stack trace:  ntdll!RtlpWaitForCriticalSection+0x8a ntdll!RtlEnterCriticalSection+0x46 Wuser32!AquireDesktopSyncAccess+0xe Wuser32!DesktopChangeThread+0x34e KERNEL32!BaseThreadStart+0x52

Keywords: KB811683

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.