JSI Tip 10237. Your Windows Server 2003 Terminal Server records Event ID 10000 in the Application event log?

When you attempt to connect to a Windows Server 2003 Terminal Server, your Application event log records an event similar to:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10000
Date: MM/DD/YYYY
Time: HH:MM:SS
User: N/A
Computer: <TerminalServer>
Description: Unable to start a DCOM Server: \{0002DF01-0000-0000-C000-000000000046\}
The error: "%%233"
Happened while starting this command: <command> -Embedding

This behavior will occur if there are missing registry Value Names in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\termsrv key on the Windows Server 2003 Terminal Server.

To resolve this behavior:

1. Open a CMD.EXE window on a workstation that has a domain administrator logged on.

2. Using REG.EXE, built into Windows XP, Windows Server 2003, and later operating systems, or installed from the Windows 2000 Support Tools, type the following commands, pressing Enter after each line, where \\<TerminalServer> is the Windows Server 2003 Terminal Server:

REG ADD "\\<TerminalServer>\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\termsrv" /V Logoff /T REG_SZ /F /D TSEventLogoff
REG ADD "\\<TerminalServer>\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\termsrv" /V Logon /T REG_SZ /F /D TSEventLogon
3. Shutdown and restart the Windows Server 2003 Terminal Server.



Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish