Microsoft KB Archive/914052

= Event ID 10000 is logged in the Application log on a Windows Server 2003-based computer that has Terminal Server enabled =

Article ID: 914052

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you try to connect to a Microsoft Windows Server 2003-based computer that has Terminal Server enabled, an event that is similar to the following is logged in the Application log: Event Type: Error Event Source:  DCOM Event Category: None Event ID:  10000 Date:      2/20/2006 Time:      10:04:57 AM User:       N/A Computer:  Computer_Name Description: Unable to start a DCOM Server: {0002DF01-0000-0000-C000-000000000046} The error: &quot;%%233&quot; Happened while starting this command: -Embedding Note  is the name of the Terminal Server computer.



CAUSE
This issue occurs when registry entries that are required for Winlogon notifications are missing from the registry of the Terminal Server computer.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.To resolve this issue, add the following registry entries to the registry of the Terminal Server computer. To do this, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK. Locate the following registry subkey:

 Under this subkey, add the following registry entries:  Restart the Terminal Server computer.

Keywords: kbtshoot kbprb KB914052

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.