The RPC Server is unavailable - Tried almost everything!
Hi. Im trying to access Integration Services on a server via SQL Server Management Studio through my local machine, and when I hit connect I get the error 'The RPC Server is unavailable'. I've turned firewalls on my machine and the server off, so I dont think its related to firewalls. Also, 2 users in the office are able to connect with no problem at all, its just my machine. However, if I remote desktop into the server and connect to Integration Services, it works! Im totally confused as to where to go now. I've checked all the RPC services are running, I've turned off firewalls, whats next? Please help!
November 16th, 2011 5:49am
Take a look at this and see if it helps: http://blog.kudosvenue.com/2010/04/19/connect-to-ssis-service-the-rpc-server-is-unavailable/Ed Clarke | www.atheonanalytics.com
November 16th, 2011 7:13am
Try also using IP Address of Server, maybe your NETBIOS settings doesn't work. Or check whether your RPC service is started (on your machine), type services.msc look for Remote Procedure Call (RPC). Randy Aldrich Paulo MCTS(BizTalk 2010/2006,WCF NET4.0), MCPD | My Blog
November 16th, 2011 7:58am
I have tried both of the above, still no joy. I have installed a new image on my pc, and now Im getting a slightly different error. 'Access is denied This error occurs when the computer has not been configured to allow remote connections through DCOM, or the user does not have permission to access the SQL Server Integration Services service through DCOM'. I've checked the DCOM settings in Component services, and I have god like rights. I've even set the permissions in the 'My Computer' level in component services. At a total loss now.
November 17th, 2011 6:30am
Did you look at this to try and resolve the DCOM access denied error? http://msdn.microsoft.com/en-us/library/aa337083.aspx There is a good step by step guide which I found and might help: http://www.schmittdotnet.com/content/SQL_Server_Integration_Services_Remote_Management.pdf Ed Clarke | www.atheonanalytics.com
November 17th, 2011 6:33am
I'm not exactly sure of your setup, but worth noting this as well: SQL Server Integration Services does not support the delegation of credentials, sometimes referred to as a double hop. In this scenario, you are working on a client computer, Integration Services is installed on a second computer, and SQL Server is installed on a third computer. Although SQL Server Management Studio successfully passes your credentials from the client computer to the second computer on which Integration Services is running, Integration Services cannot delegate your credentials from the second computer to the third computer on which SQL Server is running. But it didn't sound like this would be an issue from your first post Ed Clarke | www.atheonanalytics.com
November 17th, 2011 6:34am
Already tried both DCOM solutions edtclarke. I've doubled checked our setup, and both the SQL Server and Integration Services sit on the same box. The thing that confuses me the most is that the guy that sits next to me is able to get in without any problems, so surely it cant be a firewall issue from the server side.
November 17th, 2011 11:08am
Hi MurtzD, Which account you are using to connect the Integration Services? If the account have sufficient SSIS server permissions, here are some related articles about the issue, please refer to: http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/01/28/connecting-to-remote-sql-server-integration-service-from-sql-server-management-studio.aspx http://sharepoint.tejic.com/2011/05/04/how-to-connect-remotely-to-a-remote-sql-server-integration-service/ http://www.sqlservercentral.com/articles/Integration+Services+(SSIS)/73319/ Thanks, Eileen
November 22nd, 2011 4:19am
One other thing to note which I discovered. I was getting an RPC error too despite having ran the reporting services configuration. I saw errors where the URL was invalid or something to that affect. So this led me to realize that IIS needed to be setup. I did but still received the RPC errors. Not until I went back in to reporting services configuration and REAPPLIED the two pages concerning the URL did it work...
November 9th, 2012 8:47am