The RPC server is unavailable.
I am receiving following error "The RPC server is unavailable." when click on TestDirector link on homepage. What could be the reason for this error?
Does anyone come across this kind of scenario, I would appreciate if you could share your advises/thoughts.
Re: The RPC server is unavailable.
Here is the solution from MI.
Error: "Error in Parameter [TDsrvURL], Error : The RPC Server is unavailable"
When trying to log into TestDirector 7.5 or 7.6, the user gets the error message:
"Error in Parameter [TDsvrURL]
Error : The RPC Server is unavailable
Press OK to continue or CANCEL to close the application."
If you have a previous installation of TestDirector and do not uninstall before installing TestDirector 7.5, you will also get this issue. Please refer to this article for directions on how to install TestDirector 7.5 : Problem ID 15167 - How to upgrade from TestDirector 7.2 to 7.5.
Problem ID 18546 - How to upgrade from TestDirector 7.x to 7.6.
Solution: Troubleshooting the RPC error
1. One of the reasons why this may happen, is if the Client browser is going through a Proxy Server or the the communication to the TestDirector Server requires either a Proxy or IIS Authentication. If this is the case, please run WebGateCustomization.exe on the Client machine(s) to properly configure the TestDirector Client. Please refer to the following article on how to use the WebGateCustomization application: Problem ID 19221 - How to make TD Integrations/Client use proxy settings or IIS Authentication .
2. The second step in troubleshooting this problem is to run the "TestDirector Checker." In most cases, the "TestDirector Checker" will accurately determine what the problem is and suggest a solution. For more information about the "TestDirector Checker" please refer to Problem ID 15212 - What is the TestDirector Checker and what does it do.
3. If the "TestDirector Checker" does not give any errors, or gives an error on the "Domain Repository," or gives an error on the DCOM Configuration, then change the DCOM user to be a Local Administrator and make sure you are using the correct password. For more information about this please refer to Problem ID 14730 - How to use ChangeRunAsUser.exe to modify the DCOM user account for TD service.
4. If you have installed other Mercury Interactive products on the TestDirector web server, then some components may have changed. Try running the TestDirector Connectivity from the TestDirector Add-ins page. Please refer to this article for more information : Problem ID 8668 - What is the "TestDirector Connectivity Add-On" used for.
5. If you are still having problems after the steps above, please run the Client Diagnostic Utility on the TestDirector web server and check only the DCOM connection. If DCOM returns the project list from the Default Domain, TestDirector is OK. If you do not get an error, it means that the Default domain does not have any projects. You can find the Client Diagnostic Utility and how to use it here: Problem ID 13144 - Client Diagnostic Utility: troubleshooting tool for TestDirector client machine.
6. This time, run Client Diagnostic Utility on the TestDirector server, with all the TestDirector connection options checked. If all the TestDirector HTTP and webtdclient connection fails, or returns RPC error, then the problem might be caused from an IIS configuration issue. Check the following configurations for the TDBin virtual directory.
For Windows 2000
a. Go to Start -> Settings -> Control Panel -> Administrative Tools -> Internet Services Manager and expand the Internet Information Services -> "HOST NAME" -> Default Web Site.
b. Right-click on the TDBIN virtual directory and select Properties.
c. In the Properties, under the Virtual Directory tab, set the Execute Permissions to Scripts and Executables.
d. Check the Application Protection and if it is set to "High (Isolated)", then change it to "Low (IIS Process)". If it is set to "Low (IIS Process)", then change it to "High (Isolated)".
If this works, there may be a problem with the way that your IIS is loading the TestDirector dll. "High (Isolated)" is preferred since it will create a new process, but if IIS has trouble using this method, then it is OK to change to another method. In some cases, changing it back to "High (Isolated)" after a few days will work again.
e. Click <Apply>, then <OK>. Now you should be able to log into the Full TestDirector.
For Windows NT
a. Go to Start -> Programs -> Windows NT 4.0 Option Pack -> Microsoft Internet Information Server and invoke the Internet Service Manager.
b. Expand Console Root -> Internet Information Server -> branch -> Default Web Site -> TDBIN (or any other TestDirector virtual directory name).
c. Select "Properties" for TDBIN.
d. In the Virtual Directory tab, make sure the Application Settings Permission is set to Execute (including scripts).
e. If "Run in separate memory space (isolated process)" is checked, then uncheck it. If it is not checked, then check it. Checking this is the preferred method, but there may be an issue with the way that IIS is loading the TestDirector dll.
f. Click <Apply>, then <OK>. Now you should be able to log into Full TestDirector.
7. If you still have the same issue, then again, for the TDBin virtual directory properties, go to the Directory Security tab and do the following:
a. Click Edit on Anonymous Access, and make sure Anonymous Access is checked.
b. Click Edit again, and re-enter the local account and password for anonymous access. It is usually IUSR_machinename, or TD_IUSER_LOCAL. It is very important that you put in the correct password in this section, if not, set a new password for the TD_IUSER_LOCAL (not IUSR_machinename) in Computer Management and use that account for anonymous access.
c. Click OK, OK, Apply. Upon clicking Apply, if a window pops up requesting for child nodes inheritance, do NOT select any child nodes and click OK.
d. Reboot the TestDirector Server.
Re: The RPC server is unavailable.
If you tried all mentioned above and if you still have the same issue - tried to do what I did after a week of cracking this problem. After successful installation and using TD 8.0 to my suprise I found running exactly the same error message. I rushed through the whole internet in searching for the solution of the mystique when finaly began to run TD in the way it should be: "http://Computer_Name/TDBIN/default.html" instead of "C:\Inetpub\TDBIN\default.htm". Yes of course Computer_Name must be your computer name and maybe some paths different, but you see the idea. Would be glad if I helped someone, if not - please do not blame me. Just your case is really different.
Re: The RPC server is unavailable.
Not sure what the resolution was, but the error is no longer occurring. Magic? I don't know...All I know is one afternoon it wasn't working, and the next morning I had no issues. Was broken for a week or so, and has been fine for the last few days...
Thanks to all who offered assistance!