SQL Server 2012: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {FDC3723D-1588-4BA3-92D4-42C430735D7D}

Problem

You review the server's Application log on the server hosting your SharePoint 2013 farm's SQL Server backend, and you see the following application error occuring at 2-hour intervals:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          [time/date stamp]
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          [DOMAIN\spSQL]
Computer:      [server name]
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 DOMAIN\spSQL SID (S-1-5-21-1258338518-4216542334-3912338986-3766) 
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:
...

Solution

1. Launch RegEdit and perform a search on the APPID presented in the error message.  You will find this APPID associated with the Microsoft SQL Server Integration Services 11.0 service.
   
   Resolving this error follows pretty much the same steps undertaken to resolve other DCOM errors.  Namely, you need to enable the local launch and local activation permission.
2. Launch the Component Services applet, navigate to Console Root > Component Services > Computers > My Computer > DCOM Config.
3. Scroll down to Microsoft SQL Server Integration Services 11.0.
4. Right-click and choose Properties.  A dialog appears.
   
   .
5. In the Launch and Activation Permissions group, click the Edit button.  
6. Add the SQL Server service account (eg, spSQL), allow it both the Local Launch and Local Activation permissions,
   
   and then click OK.

   If you experience an error after clicking OK, to the affect that you don't have permissions to do this, you will need to return to the registry key you looked at earlier, take ownership of it, and then grant full control over this key to the SQL Server service account identified in the error message.  Don't worry: this is a common problem.  

7. The resolution is implemented immediately.

References

• Event 10016
• DistributedCOM Event 10016
• SQL server getting Event ID 10016 every hour
• The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

Notes

• I continued to monitor for this event for up to one week afterwards and did not observe this error to return.