New clean install of SQL Server 2012 Standard on Windows 2012 R2 Standard.

Database has been created, application (on a different server) is using the database. Things seem to be working, but I have this annoying error message in the SQL server's Windows System Log:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          8/19/2015 12:05:01 AM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          NT SERVICE\SQLSERVERAGENT
Computer:      DBSERVER.mydomain.com
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{FDC3723D-1588-4BA3-92D4-42C430735D7D}
 and APPID 
{83B33982-693D-4824-B42E-7196AE61BB05}
 to the user NT SERVICE\SQLSERVERAGENT SID (S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430) 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-08-19T07:05:01.698991800Z" />
    <EventRecordID>11162</EventRecordID>
    <Correlation />
    <Execution ProcessID="664" ThreadID="3128" />
    <Channel>System</Channel>
    <Computer>DBSERVER.mydomain.com</Computer>
    <Security UserID="S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{FDC3723D-1588-4BA3-92D4-42C430735D7D}</Data>
    <Data Name="param5">{83B33982-693D-4824-B42E-7196AE61BB05}</Data>
    <Data Name="param6">NT SERVICE</Data>
    <Data Name="param7">SQLSERVERAGENT</Data>
    <Data Name="param8">S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>

How do I get rid of this error?

I think I could do some digging around and add a permission in Windows Component Services, but I don't like mucking with system defaults which cause unexpected issues. I would rather that Microsoft's software work correctly out-of-box. Probably there is a KB with a hotfix to correct this security setting problem, and I'd rather have that and do the right thing.

Searches have left me empty handed. But I do see many hits on many DCOM error messages - Windows Component Services security settings seem to always be in a state of disrepair and few really understand them, including me.

I do not have exp with such errors but this does not seems directly related to SQl Server

This is directly related to SQL Server! The required DCOM security permission is absent for service account "NT SERVICE\SQLSERVERAGENT". Microsoft's installation setup should adjust the permissions during installation of the relevant DCOM application "Microsoft SQL Server Integration Services 11.0".

Thanks Lydia.

No, there are no errors logged in the SQL logs. I see the DCOM System Event ID 10016 error at 8pm every day, which is when a SQL Server Agent index rebuild job runs. But the index rebuild reports success. I do not understand the DCOM dependency, which when it fails, seems to have no effect.

The posts you provided give a nice summary of the steps to manually update DCOM security, and I will try that. I still think this should be reported as a Microsoft SQL Server installation bug - a SQL DCOM application should have the proper permissions set at the time of installation.

George

P.S. Sorry for the delay responding (I don't understand why the "Alert me" box failed to send an e-mail for your reply).