Problem with Windows 8 Remote desktop service

Windows 8   version: 6.2.9200.16384

1)First time ,  RDP connection will login and then  disappear  after  2 seconds.

2)Try again  few seconds later , the RDP connection will be OK and it's a new login process.

3) Event Viewer shows  System Errors 10010   [The server {AAC1009F-AB33-48F9-9A21-7F5B88426A2E} did not register with DCOM within the required timeout.]

as follows:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10010</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-22T11:32:45.383172400Z" />
    <EventRecordID>7532</EventRecordID>
    <Correlation />
    <Execution ProcessID="1020" ThreadID="20740" />
    <Channel>System</Channel>
    <Computer>just-pc</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="param1">{AAC1009F-AB33-48F9-9A21-7F5B88426A2E}</Data>
  </EventData>
</Event>

Is there any suggestion for me to solve this problem.

August 22nd, 2013 8:32am

Hi,

FOR DCOM Event ID 10010

POSSIBLE CAUSES:

1. NTFS permissions have been locked down.

2. Dll's have become unregistered (check to see if they are corrupted).

3. The service failed to start or is at either starting/Stopping state (hung).

4. An application tries to restart the service repeatedly.

5. Bug in the 3rd party or custom application.

6. A dependent service starts before the service throwing the error.

Permission of application is set incorrectly.

Description :- The server {639F725F-1B2D-4831-A9FD-874847682010} did not register with DCOM within the required timeout.

We can find the assisted file directory from the below registry location.

HKEY_CLASSES_ROOT\CLSID

File extension end with .EXE files we need to go to that file location and reregister the affected file.

Command:-  <filename> /regserver

File extension end with .DLL files we can reregister with below command

Command:- regsvr32 <filename>

Please follow the above steps and monitor the server for some time. If we get new AppGUID please do the same steps and monitor.

NOTE : The errors that are listed above are very generic errors and can come in a lot of situations. The purpose of this step is to eliminate one basic cause which we come across a lot of times. Doesn't fix the issue for us, then we need to look further.

Free Windows Admin Tool Kit Click here and download it now
August 25th, 2013 9:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics