Event IDs 1000 and 1004 may be logged in the Application event log, and Windows Server 2003 Terminal Server client connections and logon tries may sometimes fail, when you try to connect to a remote computer

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:

• When you try to connect, the logon prompt for the Terminal Server client connection returns to the Remote Desktop Connection dialog box without any error message.
• After you provide your credentials, the Log On to Windows dialog box appears again.

Additionally, the following error and information messages may be logged in the Application event log on the server side:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Description: Faulting application, version 0.0.0.0, faulting module rpcrt4.dll, version 5.2.3790.137, fault address 0x00028989.

Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Description: Reporting queued error: faulting application winlogon.exe, version 0.0.0.0, faulting module rpcrt4.dll, version 5.2.3790.137, fault address 0x00028989

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Description: Faulting application, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.49, fault address 0x0000234a

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:
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:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Type 1 Installer\Type 1 Fonts
3. Rename the Type 1 Fonts registry entry.

Note All Type 1 fonts will be disabled after you rename the Type 1 Fonts registry entry. After the logon process is complete, you can change the entry back to the original name, and the Type 1 fonts will again be available. If you still experience the problem, contact the font manufacturer of the Type 1 fonts to replace this font package.

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: