Scenario. You have a new SSIS server. All DTS packages migrated and deployed successfully to this new SSIS server. You send email notifications to the development team of the new server and that they can all continue to work on this new SSIS server now. All of them reply back with the image below.
Solution. You need to setup DCOM Config security settings in the server and allow your development team domain account access to remote launch.
In the previous versions of SQL Server, all members of the users group automatically has access to the Integration Services also. From SQL Server 2008 onwards this has changed. This service is secured by default. The administrator must manually add the user groups after installing the integration services.
From the Administrative Tools, click on Component Services or you may run dcomcnfg.exe. In the Component Services, expand Computers, expand My Computer and click on DCOM Config. On the right pane will display all the services running. If you are setting up SQL Server SSIS 2008 R2, scroll down to MsDtsServer100. You should be in the location as below:
Right click on properties, go to Security Tab and click on Edit for the Launch and Activation Permissions.
Enter the user group for your development team and check Allow for Local Launch and Activation. Click OK. Do the same for Access Permissions and click OK.
You will need to restart the SSIS Service after completing the above steps.
SSIS does not support delegation of credentials on a double hop environment. For example, you are working on a client pc, your SSIS is in another server and your SQL Server is on a third server. In this case, SSIS cannot pass your credentials to SQL Server.
For more information on DCOM configuration and SSIS, click here.