- This topic has 1 reply, 2 voices, and was last updated 9 years, 8 months ago by .
-
Posts
-
Most of my Windows 2008 R2 Standard machines work fine. Doesn’t matter if I’m patching or whatever, but I get a handfull that respond with:
“Windows Update Messages
Error 1601: Failed to retrieve WMI info. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) – 13:15:47
OS Version
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) “
Yes, the RPC service on them are running.
Yes, my user account I am running BatchPatch is in the local Admin Group on the machine in question.
I even tried doing it with manually entering ‘alternate credentials’
The machine has its firewall disabled
I do not see anything in the event logs on the target machine.
The BatchPatch directory doesn’t even get created. (I logged on and manually created it…no change)
Any other ideas?
John – “RPC server is unavailable” means that for whatever reason, BatchPatch is not getting a response from the target. Normally this would occur because a firewall is blocking access, but if the firewall is disabled as you mentioned, then I would question what else could be blocking connections. Here are a few thoughts:
1. Some other third-party software, such as host intrusion prevention or anti-virus or some other security software that is essentially providing firewall or similar services without calling itself a firewall.
2. The WMI Windows Management instrumentation service is not running.
3. The TCP/IP NetBIOS Helper service isn’t running
4. The issue is just a straight connectivity problem. If the BatchPatch computer is not able to reach the target machine in question, then you will get the RPC error. So, make sure that from the BatchPatch computer you are definitely able to ping the target machine. Perhaps you have a DNS issue, and you might consider looking at your DNS setup, using a FQDN instead of just a machine name, or trying the IP address instead.
5. Something is hosed up with the OS. Definitely try rebooting if you haven’t already done so. This isn’t really a BatchPatch issue, per se. There is something wrong with WMI or COM or something related to them (or it’s just a connectivity problem). BatchPatch is simply making a standard WMI query, but it’s not getting a response. I would also suggest that you take a look at the results of this google search and see if any of it helps: https://www.google.com/#q=0x800706BA
I hope this helps.
-Doug
- You must be logged in to reply to this topic.