Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, 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:
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.
Prerequisites
Microsoft Windows 2000 Service Pack 4.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
---------------------------------------------------------
06-Jan-2005 05:38 5.0.2195.7018 336,656 Msgina.dll
06-Jan-2005 04:29 5.0.2195.7017 6,278,656 Sp3res.dll
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.After you apply this hotfix, the problem that is described in the "Symptoms" section continues to occur. To finish resolving the problem, follow these steps:
- Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
- Add the following entry:
- Entry name: LogTSSuccess
- Value type: REG_DWORD
- Value : 1
- Locate the following regisry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\TermService
- Add the following value to the EventMessageFile entry:
;%SystemRoot%\System32\Sp3res.dll
When you view the event details in Event Viewer after you install the hotfix and add the LogTSSuccess registry entry, an event that is similar to the following is logged in the Security log:
Terminal Services Remote Logon Success:
User:
UserNameDomain:
DomainNameError Code: 0x0
Source
Network Address:
IPAddressNote The EventMessageFile entry is automatically added when you install Windows 2000 Service Pack 4. The EventMessageFile entry may cause Citrix MetaFrame event logging to stop working. If this issue occurs, contact Citrix to obtain a possible workaround or resolution to this issue.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
265173
The Datacenter Program and Windows 2000 Datacenter Server product
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For additional information about how to turn on the functionality to log IP addresses when an unsuccessful logon attempt occurs, click the following article number to view the article in the Microsoft Knowledge Base:
328478
Security event does not contain an IP address or computer name when an unsuccessful logon attempt occurs
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.