JSI Tip 10330. Your Windows Server 2003 Application event log may record Event IDs 1000 and 1004 AND Windows Server 2003 Terminal Server client connections and logon attempts may fail when connecting to a remote computer?

When Windows Server 2003 Terminal Server client connections and logon attempts fail, you may experience any of the following:

• When you attempt to connect, the logon prompt for the Terminal Server client connection returns to the Remote Desktop Connection dialog without any error message.

• After entering your credentials, the Log On to Windows dialog appears again.

Your Windows Server 2003 Application event log may record:

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 behavior will occur if an invalid font package is installed on the Windows Server 2003 that is running Terminal Server, because the WinLogon service cannot handle the data structure corruption caused by the invalid font package.

To workaround this behavior:

1. Open a CMD.EXE window.

2. Rename the Type 1 Fonts sub-key at "\ using:

set key=\HKLM\SOFTWAREMicrosoftWindows NTCurrentVersionType 1 Installer
REG COPY "%key%Type 1 Fonts" "%key%Old Type 1 Fonts" /F /S
REG DELETE "%key%Type 1 Fonts" /F

NOTE: This will disable all Type 1 fonts.

NOTE: REG.EXE is built into Windows XP, Windows Server 2003, and later operating systems, or installed from the Windows 2000 Support Tools.

After you logon, you can rename the Old Type 1 Fonts sub-key back to Type 1 Fonts and remove the invalid package.

Contact the Type 1 font manufacturer to replace the package.