Microsoft KB Archive/313329

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:45, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Lsass Access Violation When You Audit Account Log Off Events

Article ID: 313329

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition



This article was previously published under Q313329

SYMPTOMS

When you use a Windows NT 4.0-based computer as a member of a domain and you audit account log off events, Lsass.exe may experience an access violation that causes the computer to be unusable.

CAUSE

This problem occurs because the component does not properly handle the string for the account name.

RESOLUTION

A 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-language version of this fix should have the following file attributes or later:

   Date         Time   Version        Size     File name   Platform
   ----------------------------------------------------------------
   06-Dec-2001  02:16  4.0.1381.7114  155,920  Lsasrv.dll  Intel
                

NOTE: Due to file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a (SP6a).


STATUS

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

Keywords: kbhotfixserver kbqfe kbbug kberrmsg kbfix kbqfe KB313329