Every time I start an Sql Server job, I get the following error.I am using SQL Server 2016. Does not anybody know how to fix it?
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2DC39BD2-9CFF-405D-A2FE-D246C976278C} and APPID {DB336D8E-32E5-42B9-B14B-58AAA87CEB06} to the user NT SERVICESQLSERVERAGENT 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.
jmf
jmfjmf
3 Answers
Microsoft have published an article on just this issue. 2014 and 2012 instructions are on the same page.
See https://msdn.microsoft.com/en-us/library/hh213130.aspx.
In previous versions of SQL Server, by default when you installed SQL Server all users in the Users group had access to the Integration Services service. When you install the current release of SQL Server, users do not have access to the Integration Services service. The service is secure by default. After SQL Server is installed, the administrator must grant access to the service.
To grant access to the Integration Services service:
- Run Dcomcnfg.exe. Dcomcnfg.exe provides a user interface for modifying certain settings in the registry.
- In the Component Services dialog, expand the Component Services > Computers > My Computer > DCOM Config node.
- Right-click Microsoft SQL Server Integration Services 13.0, and then click Properties.
- On the Security tab, click Edit in the Launch and Activation Permissions area.
- Add users and assign appropriate permissions, and then click OK.
- Repeat steps 4 to 5 for Access Permissions.
- Restart SQL Server Management Studio.
- Restart the Integration Services Service.
Matty BrownMatty Brown
15c20b67-12e7-4bb6-92bb-7aff07997402
Ltr 450 for sale. Error:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2DC39BD2-9CFF-405D-A2FE-D246C976278C} and APPID {DB336D8E-32E5-42B9-B14B-58AAA87CEB06} to the user NT SERVICESQLSERVERAGENT 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.
Download film kartun dubbing indonesia. Please perform the following steps on the server on which the issue is happening.It should be resolved if you perform the following steps.If any concern, please let me know.
Steps:
- Open Regedit.
- Go to HKEY_Classes_RootCLSID*CLSID*. Note: CLSID stand for the ID that appears in your event viewer error. In your case, it's {2DC39BD2-9CFF-405D-A2FE-D246C976278C}.
- Right click on it then select permission.
- Click Advance and change the owner to administrator. Also click the box that will appear below the owner line.
- Apply full control.
- Close the tab then go to HKEY_LocalMachineSoftwareClassesAppID*APPID*. Note: AppID is the ID that appears in your event viewer. In your case it's {DB336D8E-32E5-42B9-B14B-58AAA87CEB06}.
- Right click on it then select permission.
- Click Advance and change the owner to administrators.
- Click the box that will appear below the owner line.
- Click Apply and grant full control to Administrators.
- Close all tabs and go to Administrative tool.
- Open component services.
- Click Computer, click my computer, then click DCOM.
- Look for the corresponding service that appears on the error viewer.
- Right click on it then click properties.
- Click security tab then click Add User. Add SYSTEM then apply.
- Tick the Activate local box.
Kundan DasangeKundan Dasange
Well I'm not an expert on component services security, but I am someone who has seen similar errors a few times and fixed them according to advice I found on the web. This assumes you are a member of the machine's Administrators group. The idea is to make Administrators the owner of the class and the app, which empowers you in Component Services to grant the needed launch and activate permissions on the components.
- Run RegEdit as administrator
- Go to HKEY_CLASSES_ROOTCLSID
- Find the CLSID noted in your error message, click on it and see what class it is. Right click for properties and see who owns it. (In my case it was a Windows 10 freeze issue, and the CLSID was for Runtime Broker, and it was owned by TrustedInstaller. Following advice I found on the web I clicked Advanced, and changed the owner to Administrators. Then I gave Administrators 'Full Control' while ensuring TrustedInstaller also still had full control.
- Next, go to HKEY_Local_MachineSoftwareClassesAppID and click the AppID from your error message. Note it's name. Make the ownership/permissions changes there as well.
- Next run Component Cervices as administrator and drill down to Console RootComponent ServicesComputersMy ComputerDCOM Config.
- For each of the components whose names you found in the Registry
- right click and choose Properties
- Click the 'Security' tab
- Under 'Launch and Activation Permissions', click 'customize', and 'Edit'
- Add 'LOCAL SERVICE' as a user
- Grant 'local launch' and 'local activation' permissions to LOCAL SERVICE
Good Luck!
user6447622user6447622
Not the answer you're looking for? Browse other questions tagged sql-server-agentsql-server-2016 or ask your own question.
In this post I’ll show you how to fix the error with the EventID 10016 from the DistributedCOM source on a computer running Windows 10 or Windows Server 2012 R2. The DCOM 10016 event is quite common in both client and server Windows versions, starting from Windows XP and you can fix this error in the same way regardless of the Windows version.
The problem shows itself as follows: the following error appears in the Windows Event Viewer in the System section when the computer boots or attempts to start or install some application:
Log Name: System
Source: DistributedCOM
Event ID: 10016
Level: Error
User: SYSTEM
Description: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {000209FF-0000-0000-C000-000000000046} and APPID Unavailable to the user IIS APPPOOLappIISPool SID (S-1-5-82-3351576649-1006875745-771203599-42452693-1279824824) 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.
Source: DistributedCOM
Event ID: 10016
Level: Error
User: SYSTEM
Description: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {000209FF-0000-0000-C000-000000000046} and APPID Unavailable to the user IIS APPPOOLappIISPool SID (S-1-5-82-3351576649-1006875745-771203599-42452693-1279824824) 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.
According to the error description: some user (for example, IIS Apppool) or a system (NT AUTHORITYSYSTEM) tries to start some COM component using DCOM infrastructure and cannot do this due to the missing of the “Local Launch” or “Local Activation” permission. The error code contains only the codes of the classes for the COM component and the application. Let’s try to determine which particular application the identifier belongs to and grant the permissions that are necessary to successfully launch and activate it.
Copy the CLSID and APPID from the event description. In my case it is:
CLSID : {000209FF-0000-0000-C000-000000000046}
APPID: {AD65A69D-3831-40D7-9629-9B0B50A93843}
APPID: {AD65A69D-3831-40D7-9629-9B0B50A93843}
(in some cases, the application identifier may not be specified – APPID Unavailable).
Also note what permissions are missing (Local Activation permission) and for which account (NT AUTHORITYSYSTEM or IIS APPPOOLappIISPool SID — S-1-5-82-3351576649-1006875745-771203599-42452693-1279824824).
In each case the class, application, account identifiers, and access type may differ.
- Run the Registry Editor (regedit.exe);
- Go to the registry key corresponding to your CLSID. In my case it is HKEY_CLASSES_ROOTCLSID{000209FF-0000-0000-C000-000000000046};In some cases, you need to check also the registry key HKEY_CLASSES_ROOTWow6432NodeCLSID. When you remotely connected to the registry, it will be located in the registry section HKEY_LOCAL_MACHINESOFTWAREClassesAppID.
- In the class parameter the app name must be specified (in my case it is Microsoft Word Application);Most often the DCOM error 10016 occurs with the following components: Immersive Shell
CLSID: {C2F03A33-21F5-47FA-B4BB-156362A2F239}
APPID: {316CDED5-E4AE-4B15-9113-7055D84DCC97}
RuntimeBroker
CLSID: {D63B10C5-BB46-4990-A94F-E40B9D520160}
APPID : {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} - Right-click on the registry key and select Permissions;
- Click on the Advanced button;
- NT ServiceTrustedInstaller or SYSTEM will be specified in the Owner section;
- Click the Change button and specify the name of your administrator account. Save the changes;
- Please note that the name of the current registry key owner has changed to your account. Check the box Replace owner on subcontainers and objects and click “OK”;
- Add your administrator account to the permissions list and grant Full Control permissions to it;
- You have granted the permissions to the registry key with CLSID. Now you need to repeat the previous steps and change ownership and permissions for administrator account on the registry key of your APPID from the error description (for example, HKEY_CLASSES_ROOTAppID{AD65A69D-3831-40D7-9629-9B0B50A93843};
- Now run the component management console (dcomcnfg) as administrator (Control Panel -> All Control Panel Items -> Administrative Tools -> Component Services);
- In the component console go to the section Component Services -> Computers -> My computer -> DCOM Config. In the COM component list find the name of the component that you defined in the second step (the value in the Application ID column must match your CLSID from the DCOM 10016 error description); If you cannot find your component in the list, you probably use a 64-bit version of Windows, and the component you want to run is 32-bit one. In this case, you need to start the DCOM console using the command:
mmc comexp.msc /32
. - Click the Security tab. All of the form controls to be accessible to change; If you open the dcomcnfg console before changing permissions on the component registry key, all the settings on the Security tab will be locked (cannot be changed), despite the fact that you started the console as an administrator.
- In my case, the application did not have the permission for Local Activation. In the Launch and Activation Permissions section, select Customize and click the Edit button;
- You need to add to the ACL an account that was specified in the error description. Depending on the text in the DCOM 10016 error, this could be SYSTEM, a specific user, or the account under which the IIS pool runs (in this case, you need to add access for the local IIS_IUSR group);If NT AUTHORITYNETWORK SERVICE was specified in the initial error instead of NT AUTHORITYSYSTEM, you must assign the local launch and activation permissions for the NetworkService account.
- Grant the necessary permissions for the account. For example, Local Launch = Allow and Local Activation = Allow.
- Restart the computer and check the event logs. The error DCOM 10016 should disappear.