DHRMotion
asked on
Connect to SSIS services failed
I am working from a workstation where I have Management Studio installed. I want to connect to the SSIS part of a SQL2005 server. But I get access denied. I can connect to the database engine with the same credentials.(Windows Authentication). My guess, based on the error message, is that I need more access rights. What more do I need?? I do not want to be admin on a production server just to be able to deploy and run packages.
imitchie
you need to find the correct role to add to your user login
ASKER
I forgot to give the information that I already have the db_dtsadmin role in msdb.
ASKER
I have followed this as in your url.
-------
Step 1: Open Object Explorer and Connect to Integration Services
Before you can assign roles to packages by using SQL Server Management Studio, you must open Object Explorer in SQL Server Management Studio and connect to Integration Services.
The Integration Services service must be started before you can connect to Integration Services.
To open Object Explorer and connect to Integration Services
Open SQL Server Management Studio.
Click Object Explorer on the View menu.
On the Object Explorer toolbar, click Connect, and then click Integration Services.
In the Connect to Server dialog box, provide a server name. You can use a period (.), (local), or localhost to indicate the local server.
Click Connect.
----------
Connection fails, access denied.
-------
Step 1: Open Object Explorer and Connect to Integration Services
Before you can assign roles to packages by using SQL Server Management Studio, you must open Object Explorer in SQL Server Management Studio and connect to Integration Services.
The Integration Services service must be started before you can connect to Integration Services.
To open Object Explorer and connect to Integration Services
Open SQL Server Management Studio.
Click Object Explorer on the View menu.
On the Object Explorer toolbar, click Connect, and then click Integration Services.
In the Connect to Server dialog box, provide a server name. You can use a period (.), (local), or localhost to indicate the local server.
Click Connect.
----------
Connection fails, access denied.
Are you connectin to a named instance? By default SSIS is installed against the default instance...
To put it another way, if your server name is:
MyServer\InstanceName
Then you should connect to
MyServer
for SSIS.
To put it another way, if your server name is:
MyServer\InstanceName
Then you should connect to
MyServer
for SSIS.
When you connect to Management Studio, what is the server name showing in the Connect to Server prompt? Is it a named instance?
SSIS does not support multi-instance. It can only be installed onto a server once, in which case I am wondering, does the server you are connecting to have multiple instances of SQL Server? The setup leads me to suspect that it has a different authentication store from normal Database Engine. In which case you are better off finding a Domain Admin login to connect to it, and configure permissions for your normal login
SSIS does not support multi-instance. It can only be installed onto a server once, in which case I am wondering, does the server you are connecting to have multiple instances of SQL Server? The setup leads me to suspect that it has a different authentication store from normal Database Engine. In which case you are better off finding a Domain Admin login to connect to it, and configure permissions for your normal login
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
imitchie:
I am aware of that it works when I am member of the local administrators group. I am that on our test and development server. But now I wanted to deploy packages to our production server and on that server I do not want to be part of the admin group. I had hoped that SSIS would have settled for less.
If not it sucks and you have earned the points for your last comment.
I am aware of that it works when I am member of the local administrators group. I am that on our test and development server. But now I wanted to deploy packages to our production server and on that server I do not want to be part of the admin group. I had hoped that SSIS would have settled for less.
If not it sucks and you have earned the points for your last comment.