Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Hi,

No, you shouldn't.

Cheers,

fdegrove - all good. Reboot with no errors. sfc /scannow shows no errors.
Tout va bien - merci!

Actually, fdegrove, I have a completely different issue but maybe your skills with regedit and permissions might be helpful.

Please see https://social.technet.microsoft.com...016setupdeploy

It would be very good to have your thoughts.

fdegrove - woops - I have a new issue that's probably related to what we were doing.

One instance of this:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 10/1/2016 10:15:24 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: DESKTOP-3OLB09N\[my user name]
Computer: DESKTOP-3OLB09N
Description:
The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout.
Event Xml:
<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="2016-10-02T02:15:24.420877600Z" />
<EventRecordID>1582</EventRecordID>
<Correlation />
<Execution ProcessID="920" ThreadID="940" />
<Channel>System</Channel>
<Computer>DESKTOP-3OLB09N</Computer>
<Security UserID="S-1-5-21-3591163430-416291016-3566129944-1001" />
</System>
<EventData>
<Data Name="param1">{21F282D1-A881-49E1-9A3A-26E44E39B86C}</Data>
</EventData>
</Event>

I think it might be related because this new {21F282D1-A881-49E1-9A3A-26E44E39B86C} in my registry is for CDP User Service Notifications Host. (Just FYI, it is also for APPID {5E176815-9A63-4A69-810F-62E90D36612A}. ) And my original issue last night was for CDP Activity Store.

Should I do anything? Thanks.

Hi,

glnz said:

Actually, fdegrove, I have a completely different issue but maybe your skills with regedit and permissions might be helpful.

Please see https://social.technet.microsoft.com...016setupdeploy

It would be very good to have your thoughts.

Sounds as if this is something for MS to resolve.
Does this happen on all your machines ?

Cheers,

Hi,

The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout.

I've seen this error before. It went away after a couple restarts.
Other than that I don't see what can be done about it.

Cheers,

fdegrove - I've started a new thread regarding Connected Devices Platform Service-CDP User Service-CDPusersvc at:
ERRORS Connected Devices Platform Service-CDP User Service-CDPusersvc
because what we've done here seems to be only a start with problems related to this CDP, and this thread should be limited to the 10016 issue.
But in that new thread, I describe a THIRD new error with this CDP, so your advice will again be much appreciated.
Merci bien de nouveau.

I experienced a lot of these errors. It took a lot of my time to fix them. Good thing there are folks on this forum that have the knowledge to help us resolve them. You would think MS would deal with them instead of putting it on the users back.

HELP I have tried everything to fix Event ID 10016. I went into RegEdit as Admin and changed ownership like Vaio7 says for CLSID & Appid. But when I go to do "Now open Component Services, Computer, My computer, DCOM config and find ( from the Registry keys above) the Description, it should be Runtime Broker, at least it was for me, if it's other then do it for the exact Component service, right click then Properties then Security tab, then open the Launch and Activation permissions Edit button and depending on the Event Viewer description if it's Local Service or System, click Add, add one of the two and enable the box " Local Activation". The EDIT buttons are Grayed out and nothing I do will change them. Anyone have any ideas.

Hi,

The EDIT buttons are Grayed out and nothing I do will change them.

Both hive keys need to be owned by "Administrators" first as described before in this thread.
Only then you can change permissions in DCOMcnfg.

Also make sure your account is part of the administrators group.

Cheers,