Hi all. I have not posted before and I am new. I realize this is an older thread but I'm pulling my hair out on this one. It is the same type of issue.
DCOM system account has been set according to troubleshooting (all checked) for now. Services restarted. SA password is working and has been verified but MP still has an issue and this DCOM error is still persistent. My clients are almost all inactive but can be pinged and repaired from the management console. MP is not functioning of course. We had a storage failure and all of the virtual machines including my sql and configmgr servers experienced unexpected shutdowns and kernel-power critical errors. CLSid is SMS Agent Host and the APPID is ccmexec
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2/25/2014 1:33:18 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: LOCAL SERVICE
Computer: ADM-V-CM01.Pokagon.local
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{1A9FFCE9-10C1-40BC-9815-B20C1DC2D156}
and APPID
{AD65A69D-3831-40D7-9629-9B0B50A93843}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
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">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2014-02-25T18:33:18.436381700Z" />
<EventRecordID>76531</EventRecordID>
<Correlation />
<Execution ProcessID="768" ThreadID="2688" />
<Channel>System</Channel>
<Computer>SERVER.Domain.local</Computer>
<Security UserID="S-1-5-19" />
I hope someone here can tell me where the client permission disconnect can be located.
Befuddled