Invalid FPNW Parameters May Cause Access Violations in Lsass.exe and Usrmgr.exe

ID: Q216035

The information in this article applies to:

SYMPTOMS

Lsass.exe and Usrmgr.exe may fail if one or more of the user parameters for the File and Print Services for NetWare (FPNW) service are invalid or corrupted.


CAUSE

When FPNW is installed on a domain controller and the "Maintain NetWare Compatible Login" option is selected in a user's profile, various parameters are enabled such as Grace Login Limit, Concurrent Connections, among others, for the user. If any of the parameters become corrupted, both Lsass.exe and Usrmgr.exe may fail.

Lsass.exe is the service responsible for all domain related functions, such as user logon validation and user account management. If Lsass.exe fails, all domain related requests to the server will fail. When an account with corrupted or invalid data is processed, Lsass.exe may have an access violation or it may enter an invalid state and be unable to process any requests. A Drwtsn32.log file will be generated if Lsass.exe has an access violation. When Usrmgr.exe fails, it will terminate immediately and generate a Drwtsn32.log file.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual fix. For information on obtaining the latest service pack, please go to:

For information on obtaining the individual fix, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/support/supportnet/default.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Windows NT Server 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Additional query words: 4.00 


Keywords          : kbbug4.00 kbfix4.00 nt4sp5fix 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: May 5, 1999