user with non sys admin to the box can not connect toSSIS

  • Hello,

    We are using Sqlserver 2005 and people with no sys admin privilege  can not access from their workstation using SQL server management studio to SSIS.

    They are getting the following message :

    Failed to Retrieve data for this request(Miscrosoft.sqlserver.SMoEnum)

    Connect to SSIS Service on Machine "MachineName" Failed

    Access is denied

    Connect to SSIS Service on machine " ASCENDER_SQL" failed:

    Access is denied.

    This has to do with some Security issue and I do not know where this can be modified,so it can be fixed.

    Any idea would be appreciated.

    Thanks Farhad

  • Hi Farhad,

    I had a similar problem and resolved it with J Foushee's final post on this TechNet forum:

    http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=701058&SiteID=17

    Best of luck

    Cath

     

  • This article should help you out.  There are additional permissions on the Server OS that you have to grant in order for non-sysadmin users to launch SSIS.

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

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Do you happend to know what other security permissions we need to setup? on local server?

    Thanks all

     

  • Did you follow the instructions in the Microsoft KB Article? 

    If so, are you saying they are still having problems?  What sort of errors are they getting?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • My customer currently has an open case with Microsoft.  Their problem may differ some from yours, as the Integration Services Service actually stops responding to connections at some unknown time of running idle.  Users get the same error message you are getting.  We "jump start" the SSIS service on the server by stopping/restarting the service.  Takes care of the issue until later when the service has been running without connections for n-number of days/hours/etc.

    Will update if/when solution is reached.

Viewing 6 posts - 1 through 5 (of 5 total)

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