Remote SSIS connection problem

we are trying to remotely adminiter SQL 2005 installed on Server B (actual server names are diferent) from SQL Server Manamagement Studio installed on Server A.

We can connect to everything else except SSIS. When we try to connect to SSIS, it says:

Cannot Connecto to B
Additional Information:
   Failed to retrieve data fro this request. (Microsoft.SqlServer.SmoEnum)
       Conecct to SSIS Server on machine "B" failed: 
          The RPC server is unavailable
          .
              Conecct to SSIS Server on machine "B" failed: 
                  The RPC server is unavailable

from connection dialog on A, we have tried putting FDQN of B.
we are using windows authentication with domain account.

per one of the suggestions, we modified MsDtsSrvr.ini.xml to change the ServerName for MSDB to be one fo the following:
B, .\MSSQLSERVER, B\MSSQLSERVER, .

we also went to DCOM settings of MsDtsServer, under security, Customize for selected for all three Permissions, and under customize settings, B\Administrators was given full access for everything.

also the domain user was added to both machines in the administrators group.

i'll appreciate any ideas.


Answer this question

Remote SSIS connection problem

  • Greggi

    Yes, it creates the same registry key.



  • poriali

    Or, can we configure a static endpoint for the MsDtsServer.exe from the application properties under component services is that same as setting the registry to configure port settings

    Thanks
    Ali

  • Karl Matless

    We are using DCOM, not RPC and port 135 may not be enough.

    This port serves as RPC endpoint for initial service discovery, but then the client should be able to communicate via (randomly assigned) port used by MsDtsSrvr.exe



  • f_haedo

    I have the same problem. Did you find a resolution I can connect from my desktop to Analysis Services and Database Engine, just not to SSIS. I haven't seen a useful answer to this anywhere !!!
  • dicky.sum

    If it always picks a random port, do we have to resort to what is specified in this article (static end points for DCOM ) http://weblogs.asp.net/rhurlbut/archive/2004/03/07/85542.aspx so we can open only 2 ports (or a range of ports in the firewall)

  • Basha

    Might there be a firewall enabled on machine B

  • Peteg

    Hi,

    I dont know exactly why this error comes but i solved it by removing the server name from the named pipes.

    \\.\pipe\sql\query and entered this value in the named pipes field.

    and i started working.

    from

    sufian



  • sasllc

    Both are windows 2003 boxes with no firewalls. there is a firewall in between box b and a, and we requested hosting services to open ports 135, and 3882 which they did. we have emailed them back today to make sure that the ports were indeed opened.

    btw, i am with mcs. i posted it here since i wasnt sure who to direct this question to, since i did not have any internal BI contacts. i am working on this issue with a client.

    Thanks
    Ali

  • Remote SSIS connection problem