SSIS 2008 Connection Error

Question

SSIS 2008 Connection Error

asdsfssd

Old Hand

Points: 384
More actions
February 11, 2013 at 10:25 am

#289085

Client: Windows 7
Server: Windows Server R2
SQL: SQL Server 2008
Trying to connect to Integration Services via SSMS2008. I'm getting the following error:
Connect to SSIS Service on machine "{ServerName}" failed: The RPC server is unavailable
I have tried the following (per the following http://www.kodyaz.com/articles/ssis-integration-services-remote-connection-rpc-server-unavailable.aspx)
1) Verified Server is accepting TCP - local port 135 and remote port 135 (added to Inbound Rules)
2) Client Outbound Rules is allowing TCP - local port 135 and remote port 135.
3) Disable client firewall
None of that didn't work.
I have also tried
1) Server - Added Outbound Rules, Programs and Services, Program Files\Microsoft SQL Server\100\DTS\Binn\MSDTSSrvr.exe (SSIS - Test)
This will allow me to connect from the client.
However, issuing
netstat -a -n -o
shows all kinds of ports open. I think this is a security hole - and probably unacceptable to server admins. However if the moment I restrict SSIS - Test rule to ports 135; I'm not able to connect from the client.
Any help is much appreciated.
So

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

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

AlexSQLForums SSChampion Points: 14277 More actions · Answer 1

try this http://www.sqlservercentral.com/blogs/robert_davis/2008/08/13/How-do-I-grant-access-permissions-for-SSIS-to-users/[/url]

Alex S

asdsfssd Old Hand Points: 384 More actions · Answer 2

Thanks for responding ... checked your link.

My username is in the Administrators group on the server and the client. On both the server and client, the following are verified:

1) On MsDtsServer, Launch and Activation Permission, Administrators group is allowed for Local Launch, Remote Launch, Local Activation, Remote Activation.

2) On MsDtsServer, Access Permission, Administrators group is allowed for Local Access, Remote Access.

3) Added my username to DCOM group on both the client and server.

4) Restarted SSIS service on both client and server.

Error. Message is

Cannot connect to <servername>.
Additional Information: Failed to retrieve data for this request (Microsoft.SqlServer.Management.Sdk.Sfc)
Connect to SSIS Service on machine "<servername>" failed:
The RPC server is unavailable.

Query Shepherd SSCrazy Points: 2988 More actions · Answer 3

Have you got a firewall enabled. If yes, the try to allow the Process C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe and open TCP Port 135. You could also pretest if you can telnet port 135 on the remote machine.

Greetz
Query Shepherd

asdsfssd Old Hand Points: 384 More actions · Answer 4

Yes, firewall is enabled.

And yes, I have also tried

1) Server - Added Outbound Rules, Programs and Services, Program Files\Microsoft SQL Server\100\DTS\Binn\MSDTSSrvr.exe

This will allow me to connect from the client. However, issuing

netstat -a -n -o

shows all kinds of ports open. I think this might be a security concern - and probably unacceptable to network and server admins.

And the moment I add port 135 to that same Outbound Rule, I cannot connect from my client.