FIX: The application-specific permission settings do not grant Local Launch permission…   1 comment

This problem occurred on a two node SQL Server 2008 clustered instance running on Windows Server 2008. Everything seemed to be fine, however, System logs was being spammed by these errors:

348106, [Error, EID:10016] Microsoft-Windows-DistributedCOM, 11-07-2012 11:07:15, The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {46063B1E-BE4A-4014-8755-5B377CD462FC} and APPID {FAAFC69C-F4ED-4CCA-8849-7B882279EDBE} to the user domain\user SID (S-1-5-21-xxxx) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Here are the steps as how I troubleshot and resolved this problem.

First, go to registry and find out the AppID and the corresponding program name from the CLSID {46063B1E-BE4A-4014-8755-5B377CD462FC}. The information should be located at HKEY_CLASSES_ROOT\CLSID


"Assembly"="MsDtsSrvr, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91"

Ok, so this appears to be SSIS component. But we do not have SSIS installed on this server. Well, we still install the binaries (e.g. MsDtsServer) to support SSIS package executions. And I do see these logs indicating the same:

Log Name:      Application
Source:        SQLISPackage100
Date:          11/07/2012 11:07:15 AM
Event ID:      12289
Task Category: None
Level:         Information
Keywords:      Classic
User:          domain\user
Computer:      server_name
Package "abc" finished successfully.

Alright, now let’s find out what does AppID {FAAFC69C-F4ED-4CCA-8849-7B882279EDBE} corresponds to by looking at HKEY_CLASSES_ROOT\AppID\


(Default)    REG_SZ    MsDtsServer100
LocalService    REG_SZ    MsDtsServer100
AuthenticationLevel    REG_DWORD    0x3

This confirms that the AppID in question belongs to MsDtsServer100 i.e. SSIS binary as stated before. This means user domain\user doesn’t have enough permissions on MsDtsServer100 DCOM properties. Let’s verify:


Apparently, I don’t see domain\user listed. Obviously we need to add this user and grant appropriate permissions. The outstanding questions is, the user should have had permissions here, how was this reset? The reason is explained here in this KB article:

DCOM Permissions for SSIS service are Reset after applying a service pack or a cumulative update or a hotfix

In conclusion, the resolution is to either follow the “Resolution” section of  the above mentioned KB article (i.e. apply SP2 for SQL 2008) else follow the “Workaround 1” section to grant appropriate permissions in DCOM for MsDtsServer100 domain\user. Please skip the stepRestart the SQL Server Integration Services service.”

Hope this helps!

One response to “FIX: The application-specific permission settings do not grant Local Launch permission…

Subscribe to comments with RSS.

  1. Pingback: Add Your Name (or) Application to right click Of My Computer « COMPUTER DOWNLOADS SPOT

Leave a Comment

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: