Article ID: 234655
Article Last Modified on 1/12/2007
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q234655
SYMPTOMS
When you restart your computer, the Netlogon service may not start and the following error message is displayed when you attempt to log on at the server console:
The server may start successfully after multiple restarts.
CAUSE
This behavior occurs because the Security Accounts Manager (SAM) for the domain does not initialize if the locale for the computer is set to use a code page that uses Unicode double compression. A locale that is known to support this feature is Hungarian. The way that string comparisons are handled for double compression code pages causes the problem.
RESOLUTION
Windows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
- 152734how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, 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:
Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
WORKAROUND
To work around this problem, change the locale to one that does not use double compression (this includes all English language locales).
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB234655
