Using SSMS to Manage SSIS

Using SSMS to Manage SSIS

• Luiz Bicalho

  Hi,
  
  You can modify who has access to SSIS service:
  On service machine, start DCOMCNFG, expand
  Component Services > Computers > My Computer > DCOM Config.
  
  Find MSDtsServer, right-click, select properties.
  Open Security page. You need to grant users
  activation and access permissions to let them
  access service that is already running.
  In addition they need launch permission to be
  able to start the service (if it is set to manual start).
  
  The DTS service should be enabled (in some builds
  the default installation leaves service disabled).
  

  
  
  

• Kashu

  Not sure what the answer is, but can give you some things to check.
  
  Has the DCOM port been shutdown on your network by chance
  Are you able to connect through DTExec or DTUtil
  Has the machine running the SSIS service ever been rebooted since install
  
  I'll ask around and see if someone here has seen this before.
  
  Thanks,
  
  
  
  

• tuhack

  I have the same problem. I'm using windows xp and visual studio 2005. When I ask Visual Studio to print out the class diagram, I get the same error "The RPC Server is unavailable".

  I have a workgroup and the printer is shared on a windows 2000 computer in the kitchen at home.

  Tim

  
  

• Sebastian Paulussen

  Well, I think I have an idea of what the problem is (not quite sure though).
  
  The connection properties in SSMS when connecting to the integration service indicates that the port is 3882, but even though the service is running on the server, that port is not open.  My guess is when it runs locally, it avoids using TCP/IP, but fails for that reason when connecting from another computer.
  
  But I don't have a fix for this problem yet :P
  
  

• Joewee

  Hi Michael,
  
  Applying the security settings within the DCom Config tool did not seem to work.  Any other ideas
  
  Also, I seem to have come across a bit of a pattern regarding the "RPC server is unavailable" and "Access denied" error messages/conditions.  This appears to be the pattern I observe:
  
  1.  Add myself to the local Administrators group on the server.  I can now manage SSIS on the server using SSMS on the client.  Great, but not acceptable.
  
  2.  Remove myself from the local Administrators group.  Regardless of what permission settings I try via DCom or any other route, I get an "Access denied" error message.
  
  3.  "Access denied" continues to be the error message until I either log off of the client or reboot.  At that point, I start getting "RPC server is unavailable" again.
  
  4.  The "RPC server is unavailable" message continues until I put myself back into the local Administrators group on the server.  Then, GoTo #1 above.
  
  Any other suggestions   Thanks for your help btw...
  
  Dave F.
  

• ChiragKhabaria

  FWIW I get the same error.  RPC server is running and everything...
  
  

• Beat_______

  Okay, I have some more (interesting) information on this.
  
  I successfully got around the "RPC server is unavailable" error by using the fully qualified domain name of the server I was trying to connect to.  However, that only got me part of the way there...
  
  If my domain account is listed in the local Administrators group on the server I am trying to manage, I can connect to SSIS on that server using SSMS (on a client machine where I'm logged into the domain).  If my domain account is removed from the local Administrators group, I get an "Access denied" error message.
  
  So, does remote management of SSIS via SSMS require any specific permissions be set on the server   I would hate to think administrative access is require.  Or is this still related to some type of DCOM issue   Or something else
  
  Thanks,
  Dave Fackler
  

• AndreyZ

  Could you check if you have a firewall blocking access to the server (e.g. Windows firewall included in XP or Server 2003)
  
  
  

• Sean F

  I have the same problem. Did you ever find a solution

  
  

• YellOwCN

  Kirk,
  
  Thanks for the reply last week, but I'm still having this issue.  We've upgraded the server we're working on to CTP 15, the same as the client.  The SSIS service is running, as is the RPC service.  But when I try to connect to SSIS via SSMS on my client machine, I still get the "The RPC server is unavialable".
  
  Any other thoughts or things I should try
  
  Dave F.
  

• joelfreak

  I just blogged about this:
  http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/09/15772.aspx
  Basically, with earlier CTP releases you have two options, supply a self signed cert to the server or upgrade to the June CTP.
  Thanks,
  K
  
  

• Shiplu

  It's not.  I'll probably investigate this problem some more during the weekend.
  
  

• DmitriyGorbachev

  Actually, SSIS is using DCOM protocol, the port 3882 indicated by SSMS is a mistake.
  
  

• newbieToVJS

  I've just the same problem and I’ve tried all the options listed above, but I want to add a comment:

  "The same login, in the same machine with only the db_dtsltduser role assigned can deploy succesfully a package from the manifest file to the same SSIS instance".

  I imagine that it’s because It does not use any connection to SSIS when deploying package to msdb.

  It's ok for developers role, but not for operators nor administrators.

  Thanks

  
  
  
• Using SSMS to Manage SSIS