Connect to SSIS Service on machine "miloqadb" failed: Access

Question

Connect to SSIS Service on machine "miloqadb" failed: Access

Ludwig Guevara

SSC Veteran

Points: 225
More actions
October 11, 2006 at 1:29 pm

#169981

I have a SQL-server Enterprise Edition 9.00.2047.00 (SQL 2005 - SP1) with SSIS on Windows 2003 SP1 Box
I have this user, who try to conect to this box using Integration Services, he only get this error:
"Connect to SSIS Service on machine db% failed: Access"
It seams, after apply SP1 for SQL 2005 reset all configuration for application MsDtsServer check http://msdn2.microsoft.com/en-us/library/aa337083.aspx but, I have the same message again
Can someone help, me, please
October 16, 2006 at 8:00 am

This was removed by the editor as SPAM

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

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

Brandie Tarvin SSC Guru Points: 173056 More actions · Answer 1

You have to jump through hoops to grant non-sysadmin users access to launch SSIS on your SQL Servers, and it requires granting them access via the Windows OS and certain objects on the machine.

Here's a Microsoft KB article that describes the steps you have to take before the users can 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.

Brandie Tarvin SSC Guru Points: 173056 More actions · Answer 2

Gregg,

You might want to re-read the article. Step 1. It actually does say "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"

Brandie

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.

Arshad Ali-556241 Say Hey Kid Points: 706 More actions · Answer 3

Hi,

I had similar issue and got resolved after registering dts.dll with following command:

%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll"

Refer to this KB article for more details: http://support.microsoft.com/kb/919224

With Thanks and Regards
Arshad Ali
Microsoft India

My Blog - http://arshadali.blogspot.com/[/url]

BudaCli Hall of Fame Points: 3404 More actions · Answer 4

I added the user as part of the local admin in the machine hosting SSIS and this worked but if you do not want to add the user as an admin you can use the dcomcnfg command to go to the Component services.

What you don't know won't hurt you but what you know will make you plan to know better