Access denied when connecting to SSIS

Question

Access denied when connecting to SSIS

Adam Bean

One Orange Chip

Points: 26631
More actions
June 11, 2010 at 1:27 pm

#222015

Hey all,
I've went through many articles at this point and I'm coming up with nothing. I have a single node Windows 2008 cluster running SQL2008 installed as a single node cluster with SSIS. I first had the issue to as where I was getting a "Login timeout expired", but resolved that by editing MsDtsSrvr.ini.xml (http://msdn.microsoft.com/en-us/library/ms137789.aspx).
I have local and SQL admin rights, so this works fine for me. Yet my developers are getting an "Access Denied" when using SSMS to connect to SSIS on this server.
I have added their NT group to the following to no avail:
- db_ssisadmin role in msdb
- The local Distributed COM Users
- The local SQL2005DTS group
- Granted Launch and Activation Permissions (remote launch/remote activation) under COM Security (even though I now see that Distributed COM Users is already here).
What else am I missing?
Thanks

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Ken Jr. SSCommitted Points: 1842 More actions · Answer 1

I saw you have: The local SQL2005DTS group.. If they are on SQL 2005 they won't be able to connect to SSIS in SQL 2008. You would need the 2008 Management studio to connect to it. Not sure if they already have 2008 but just throwing it out there.

Adam Bean One Orange Chip Points: 26631 More actions · Answer 2

Kenneth Langner Jr. (6/11/2010)
I saw you have: The local SQL2005DTS group.. If they are on SQL 2005 they won't be able to connect to SSIS in SQL 2008. You would need the 2008 Management studio to connect to it. Not sure if they already have 2008 but just throwing it out there.

That group was created as part of the SQL2008 install. There is no SQL2008DTS group. I don't think the group really serves a purpose though, but I honestly don't know ... Haven't crawled for its permissions.

Ken Jr. SSCommitted Points: 1842 More actions · Answer 3

Try this out:

http://msdn.microsoft.com/en-us/library/aa337083.aspx

Adam Bean One Orange Chip Points: 26631 More actions · Answer 4

Kenneth Langner Jr. (6/11/2010)

Try this out:

http://msdn.microsoft.com/en-us/library/aa337083.aspx%5B/quote%5D

Thanks Ken, already went through it.

cliffb SSCarpal Tunnel Points: 4598 More actions · Answer 5

This may sound odd, but try adding one of the problem users directly rather than through the group. That will at least tell you if the issue is with the group or not.