Quantcast
Channel: Windows 8.1 Performance forum
Viewing all articles
Browse latest Browse all 1658

DCOM Error: Local Launch for a (potentially nonexistant) account

$
0
0

*I was directed here from Microsoft Answers due to the complexity of the situation

since the start of win8.1, I been having a yellow warning about a  DCOM launch error, and normally like the other DCOM error I would be a be to add the permission to what needs its. the problem is that it is for "NT Authority\SYSTEM" and when I try to add, and tried a advanced search for the name, it came up empty. in the end I had to give up, after fixing a problem with RAID driver that caused my hard drive, running AHCI, to be "resetting by request", I noticed that the yellow is now red error with same write-up. the only name that came close to the account was "SYSTEM" and it has all allowed. the problem only gets in event viewer when the computer is started up. is there something missing that could probably add the"NT Authority\SYSTEM"?

SMS Agent Host is what the application ID (APPID) leads to

-------------------------------------------------------------------------------------------------------------------------------------------------

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          4/1/2015 10:09:56 PM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      ShnookCenter
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{1CCB96F4-B8AD-4B43-9688-B273F58E0910}
 and APPID
{AD65A69D-3831-40D7-9629-9B0B50A93843}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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="2015-04-02T05:09:56.637326500Z" />
    <EventRecordID>31008</EventRecordID>
    <Correlation />
    <Execution ProcessID="960" ThreadID="2248" />
    <Channel>System</Channel>
    <Computer>ShnookCenter</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Launch</Data>
    <Data Name="param4">{1CCB96F4-B8AD-4B43-9688-B273F58E0910}</Data>
    <Data Name="param5">{AD65A69D-3831-40D7-9629-9B0B50A93843}</Data>
    <Data Name="param6">NT AUTHORITY</Data>
    <Data Name="param7">SYSTEM</Data>
    <Data Name="param8">S-1-5-18</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
< /Event>


Viewing all articles
Browse latest Browse all 1658

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>