I am trying to connect to Integration Services in Management Studio so I can review deployed packages. I tried the following but still cannot connect nor add deployed packages to SQL Agent jobs: If the user is not a member of the local Administrators group, add the user to the Distributed COM Users group. You can do this in the Computer Management MMC snap-in accessed from the Administrative Tools menu. Open Control Panel, double-click Administrative Tools, and then double-click Component Services to start the Component Services MMC snap-in. Expand the Component Services node in the left pane of the console. Expand the Computers node, expand My Computer , and then click the DCOM Config node. Select the DCOM Config node, and then select MsDtsServer in the list of applications that can be configured. Right-click on MsDtsServer and select Properties . In the MsDtsServer Properties dialog box, select the Security tab. Under Launch and Activation Permissions , select Customize , then click Edit to open the Launch Permission dialog box. In the Launch Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Launch, Remote Launch, Local Activation, and Remote Activation. The Launch rights grant or deny permission to start and stop the service; the Activation rights grant or deny permission to connect to the service. Click OK to close the dialog box. Under Access Permissions , repeat steps 7 and 8 to assign the appropriate permissions to the appropriate users and groups. Close the MMC snap-in. Restart the Integration Services service.

Have you added yourself to the db_ssisadmin role? http://msdn.microsoft.com/en-us/library/ms141053.aspxChuck Pedretti | Magenic North Region | magenic.com

In the MSDB database? I just did so - all three roles mentioned in the link....no change. I don't see where you can add any security or role in integration services.

Can you post the error?MCTS, MCITP - Please mark posts as answered where appropriate.

OK - what OS are you running on? If Win 2003 Server then the last statement in this blog may apply: http://geofforrsyd.wordpress.com/2007/08/10/access-denied-integration-services-remote-users/ This article also mentions the additional step of adding your user to the Distributed Com Users group http://sqlbuzz.wordpress.com/2011/12/07/connecting-to-the-integration-services-service-on-the-computer-mirrorstand-failed-with-the-following-error-access-is-denied/ Chuck Pedretti | Magenic North Region | magenic.com

Cannot connect to Server2. Additional information: --->Failed to retrieve data for this request. (Microsoft.SQLServer.Management.Sdk.Sfc.) ---> Connecting to the Integration Services service on the computer "Server2" failed with the following error: "Access is denied.". This error occurs when the computer has not been configued to allow remote connections through DCOM, or the user does not have permission to access the SQL Server Integration Services service through DCOM. ---> Connecting to the Integration Services serice on the computer "Server2" failed with the following error: "Access is denied.". THis error occurs when the computer has not been configured to allow remote connections through DCOM, or the user does not have permission to access the SQL Server Integration Services service through DCOM. I can RDP to Server2 as domain admin and connect to SSIS through Mgmt Studio locally.

OK - what OS are you running on? If Win 2003 Server then the last statement in this blog may apply: http://geofforrsyd.wordpress.com/2007/08/10/access-denied-integration-services-remote-users/ This article also mentions the additional step of adding your user to the Distributed Com Users group http://sqlbuzz.wordpress.com/2011/12/07/connecting-to-the-integration-services-service-on-the-computer-mirrorstand-failed-with-the-following-error-access-is-denied/ I can confirm that this is usually needed. It's actually listed in the paragraph right before point 1 (posted in the question): If the user is not a member of the local Administrators group, add the user to the Distributed COM Users group.MCTS, MCITP - Please mark posts as answered where appropriate.

Jeeze - I didn't see it there.Chuck Pedretti | Magenic North Region | magenic.com

My bad....I rechecked my work....apparently I hadn't saved the Configuration Permissions property of MsDtsServer100 correctly....I had to add my user again. I also added the user to the Distributed COM Users group on the domain controller but not on the Server hosting SSIS. I thought that would take care of it, apparantly not because my users weren't members of the DCom Users group on Server2. Anyway, I can now connect to Integration Services, hopefully I'll be able to build a SQL Agent task with my pacakge without trouble now. I do wonder why every other SQL application gave itself appropriate permissions upon installation except SSIS....oh well... Thanks!