Home Dashboard Directory Help
Search

MDW - job on MDW server generates Event 10016 (DistributedCOM-Error) in system log by Kunk


Status: 

Closed


3
0
Sign in
to vote
Type: Bug
ID: 780569
Opened: 3/4/2013 5:20:23 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description



I installed MDW (Mangement Data Warehouse) on a SQL Server 2012. I activate the system data collection on that system too. Since that I found several DistributedCOM-Errors in the system event log ( event ID 10016) every time one of the data collection jobs is running.
Her is the complete error message :

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 NETRTLSRV\SvcSQLServerAgent SID (S-1-5-21-2585614801-172033302-3695164279-1158) from address LocalHost (Using LRPC). This security permission can be modified using the Component S
ervices administrative tool.

I searched the registry for CLSID {FDC3723D-1588-4BA3-92D4-42C430735D7D} an found that it is the service MsDtsServer110 (Microsoft.SqlServer.Dts.Server.DtsServer) and has something to with integrated services.
Furthermore I found some older entries in the internet talking about DCOM-Config in Component Services for MSDTServer100. On other servers running MS SQL Server 2008 R2 I can find a MsDtsServer100 entry in DCOM-Config.
But for SQL Server 2012 there isn't a MsDtsServer110 entry in DCOM-Config.

1. Where is that entry ?
2. What can I do to add the entry ?
3. How can I config DCOM security so that local data collection jobs didn't generate event 10016 entries in the system error log ?


By the way, data collection on other server remotely connecting the MDW-server didn't generate any 10016 event!

Regards
Wolfgang Kunk
Details
Sign in to post a comment.
Posted by Kunk on 4/17/2013 at 12:47 AM
1. In the meantime I opened a regular Case. Mr. Cezar Ionescu [cezari@microsoft.com] handles this case.

2. The workaround you offered seems to solve the problem. I will inform MS Support regarding this workarounf
Posted by Microsoft on 4/16/2013 at 2:59 PM
Please let us know if the posted workaroudn solves your problem

Thanks
Posted by Sethu Srinivasan on 4/16/2013 at 2:58 PM
Let us know if this workaround solves your issue
1)    Run Dcomcnfg.exe
2)    Expand Component Service -> My Computer ->DCOM Config
3)    Locate “Microsoft SQL Server Integration Services 11.0”
4)    Right click and select “Properties”
5)    Select “Security” tab
6)    In Launch and Activate Permissions, click on “Edit”
7)    Grant “Local Launch”, “Local Activation” permissions for SQL Agent Service account
8)    Restart all Data collectors, Check Windows System Event log for any DCOM errors that you were seeing before.

Thanks
Sethu Srinivasan [MSFT]
Posted by Microsoft on 3/4/2013 at 2:31 PM
Hello Kunk. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Sign in to post a workaround.
Posted by Sethu Srinivasan on 4/16/2013 at 2:57 PM
MDW - job on MDW server generates Event 10016 (DistributedCOM-Error) in system log
Issue:
System collection sets run SSIS packages in SQL Agent Service account context. If SQL Agent Service account did not have DCOM launch permissions to launch COM+ component “Microsoft SQL Server Integration Services 11.0”, we would see following entries in Windows System Event Log
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.

Solution:
1)    Run Dcomcnfg.exe
2)    Expand Component Service -> My Computer ->DCOM Config
3)    Locate “Microsoft SQL Server Integration Services 11.0”
4)    Right click and select “Properties”
5)    Select “Security” tab
6)    In Launch and Activate Permissions, click on “Edit”
7)    Grant “Local Launch”, “Local Activation” permissions for SQL Agent Service account
8)    Restart all Data collectors, Check Windows System Event log for any DCOM errors that you were seeing before.