You may receive an error in the Userinit.exe component when you log on to a Windows Server 2003-based or a Windows 2000-based Terminal Services session

You may receive an error in the Userinit.exe component when you log on to a Microsoft Windows Server 2003-based or a Microsoft Windows 2000-based Terminal Server session. The error message may appear similar to the following: The "Stack Back Trace" section of the DrWtsn32.log file may appear similar to the following: Note The wcscat function should not have zero (0) as the first parameter.

This behavior occurs when one of the following conditions is true:

• The date of the .ini file that is located in the Userprofile\Windows folder is older than the file date in the following registry subkey:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\IniFile Times
  Note By default, the Userprofile folder is located in the Documents and Settings\Username folder on the Windows-based computer that is running the Terminal Services program.
• The CITRIX_COMPAT_INISYNC (0x40) and CITRIX_COMPAT_WIN16 (0x04) .ini file synchronization flags are both set in the following registry subkey:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\Name
  Note Name is the module name. The module name is typically the same as the .ini file name in the Userprofile\Windows folder, but the .ini extension is removed.
• The .ini file that is in the Userprofile\Windows folder has no period (.) in the file name.

Windows 2000 hotfix information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Windows Server 2003 hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to 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.

Windows Server 2003, 32-bit versions

Windows Server 2003, Enterprise Edition for Itanium-based Systems

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: