Windows NT Fails Because of an Access Violation in WINLOGON

 Last reviewed: October 12, 1995
Article ID: Q136336
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

If an access violation occurs in WINLOGON, an updated DrWtsn32.LOG appears in the %SystemRoot directory and the following symptoms also occur sporadically:

  • A STOP 21a message appears on the server screen.
  • The error message "Error 1723 RPC Server too Busy" is returned to client requests.

CAUSE

Winlogon fails due to an access violation caused by an RPC length pointer that refers beyond the end of a data structure (RPC buffer) referenced during RPC unmarshalling. This occurs if a client program provides an invalid RPC packet length or the length field gets damaged during the delivery to the server process.

The STOP 21a message occurs if the security system fails.

The Error 1723 occurs if threads in the SERVICES.EXE block as a result of the security system failure.

RESOLUTION

To correct this problem, install the latest U.S. Service Pack for Windows NT version 3.51.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 3.51. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

KBCategory: kbnetwork kbbug3.51 kbfix3.51.sp2
KBSubcategory: ntsecurity ntnetserv ntstop
Additional reference words: prodnt 3.51

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: October 12, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.