Article ID: 914048 - View products that this article applies to.
On a Microsoft Windows Server 2003-based computer, Windows Server 2003 Terminal Server client connections and logon tries may sometimes fail. You may also experience one or more of the following symptoms:
Event Type: Error
Event Type: Information
Event Type: Error
This issue occurs when a font package that is not valid is installed on the Windows Server 2003-based server that is running Terminal Server. When you try to log on, the font package that is not valid causes data structure corruption that finally cannot be handled by the Winlogon service. Therefore, a Terminal Server connection session cannot be established.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To work around this issue, rename a registry key so that the Winlogon service does not use these fonts during Terminal Server client connection initialization. To do this, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about a similar problem, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/811769/ )STOP 0x00000050 in error message in Atmfd.dll when you use Type 1 fonts
Article ID: 914048 - Last Review: October 11, 2007 - Revision: 1.4