Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS 2008 Connection Error Expand / Collapse
Author
Message
Posted Monday, February 11, 2013 10:25 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 1:35 PM
Points: 6, Visits: 29
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
Post #1418547
Posted Monday, February 11, 2013 1:22 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, August 25, 2014 9:55 AM
Points: 1,288, Visits: 1,863
try this http://www.sqlservercentral.com/blogs/robert_davis/2008/08/13/How-do-I-grant-access-permissions-for-SSIS-to-users/

Alex S
Post #1418619
Posted Tuesday, February 12, 2013 7:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 1:35 PM
Points: 6, Visits: 29
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.

Post #1418979
Posted Thursday, February 14, 2013 2:21 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:41 AM
Points: 118, Visits: 355
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
SQL Pizza



sometimes you dont see the pizza for the toppings...
seek and ya shall find...
Post #1419884
Posted Thursday, February 14, 2013 2:53 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 1:35 PM
Points: 6, Visits: 29
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.
Post #1420314
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse