Strange errors regarding RPC and WMI after migrating Hyper-V from Windows Server 2008 R2 to Windows Server 2012 cluster...

Hi all;

Suppose I have created a two-node Hyper-V cluster with a fibre channel shared storage in Windows Server 2012. Everything work fine except some issues. One of the is that when I want to configure the cluster to add a VM as its cluster resource, the following error message appears:

An error occurred while determining the state of this clustered role in the cluster. The remote procedure call failed with error 800706BE.

Any ideas?

June 9th, 2013 6:22pm

Hi,

RPC is an interprocess communication (IPC) method that is used by clients and servers to communicate with each other. Simply put, RPC is used by programs, typically on a client computer, to execute a program on a server computer.

Please make sure that the remote procedure call (RPC) services are started on the server computer. You can do this by opening Control Panel, double- clicking Services, and checking to make sure the Remote Procedure Call (RPC) Service and Remote Procedure Call (RPC) Locator services are running and set to start automatically.

You can also refer to following articles to troubleshoot RPC error:

HOWTO: Troubleshoot RPC Errors
http://support.microsoft.com/kb/197814
http://technet.microsoft.com/en-us/magazine/2007.07.howitworks.aspx

Hope this helps!
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

Free Windows Admin Tool Kit Click here and download it now
June 10th, 2013 3:55am

Thanks for your reply

 

I have tested many possible solutions without any success. The actions that I have done so far are mentioned in the following and the results of them have been said, too.

 

  1. When I restart the servers, everything are good but after some times when I reopen Failover Cluster Manager on one of the servers, the snap-in related to my cluster name does not load. Please look at the following figure:

 

 

And when I want to connect to my cluster name, the following error message appears:

 

Note: The above problem appears randomly regarding to servers. In the other hand, after the restart, one of the servers acts as the above statement.

 

  1. The following error message is the result of the DTCPing utility:

 

++++++++++++hosts      ++++++++++++

 

06-11, 10:02:15.346-->Error(0x424) at clutil.cpp @256

06-11, 10:02:15.346-->-->OpenCluster

06-11, 10:02:15.356-->-->1060(The specified service does not exist as an installed service.)

++++++++++++++++++++++++++++++++++++++++++++++

     DTCping 1.9 Report for ADMINISTRATOR1 

++++++++++++++++++++++++++++++++++++++++++++++

RPC server is ready

++++++++++++Validating Remote Computer Name++++++++++++

06-11, 10:02:20.428-->Start DTC connection test

Name Resolution:

            SRV04-->172.16.140.11-->SRV04

06-11, 10:02:32.448-->Start RPC test (ADMINISTRATOR1-->SRV04)

Problem:fail to invoke remote RPC method

Error(0x6D9) at dtcping.cpp @303

-->RPC pinging exception

-->1753(There are no more endpoints available from the endpoint mapper.)

RPC test failed

 

And

 

06-11, 10:26:10.837-->Error(0x424) at clutil.cpp @256

06-11, 10:26:10.837-->-->OpenCluster

06-11, 10:26:10.837-->-->1060(The specified service does not exist as an installed service.)

++++++++++++++++++++++++++++++++++++++++++++++

     DTCping 1.9 Report for ADMINISTRATOR1 

++++++++++++++++++++++++++++++++++++++++++++++

RPC server is ready

++++++++++++Validating Remote Computer Name++++++++++++

06-11, 10:26:14.947-->Start DTC connection test

Name Resolution:

            SRV04-->172.16.140.11-->SRV04

06-11, 10:26:26.967-->Start RPC test (ADMINISTRATOR1-->SRV04)

Problem:fail to invoke remote RPC method

Error(0x6D9) at dtcping.cpp @303

-->RPC pinging exception

-->1753(There are no more endpoints available from the endpoint mapper.)

RPC test failed

 

And

 

++++++++++++hosts      ++++++++++++

 

06-11, 10:47:51.510-->Error(0x424) at clutil.cpp @256

06-11, 10:47:51.510-->-->OpenCluster

06-11, 10:47:51.510-->-->1060(The specified service does not exist as an installed service.)

++++++++++++++++++++++++++++++++++++++++++++++

     DTCping 1.9 Report for ADMINISTRATOR1 

++++++++++++++++++++++++++++++++++++++++++++++

RPC server is ready

++++++++++++Validating Remote Computer Name++++++++++++

06-11, 10:47:55.020-->Start DTC connection test

Name Resolution:

            SRV03-->172.16.140.10-->SRV03

06-11, 10:48:06.830-->Start RPC test (ADMINISTRATOR1-->SRV03)

Problem:fail to invoke remote RPC method

Error(0x6D9) at dtcping.cpp @303

-->RPC pinging exception

-->1753(There are no more endpoints available from the endpoint mapper.)

RPC test failed

 

  1. The following output is the result of running PortQuery on port 135 on both servers:

 

=============================================

 

 Starting portqry.exe -n srv03 -e 135 -p TCP ...

 

 

Querying target system called:

 

 srv03

 

Attempting to resolve name to IP address...

 

Name resolved to 172.16.140.10

 

querying...

 

TCP port 135 (epmap service): LISTENING

 

Using ephemeral source port

Querying Endpoint Mapper Database...

Server's response:

 

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d

ncacn_ip_tcp:srv03[49152]

 

UUID: 906b0ce0-c70b-1067-b317-00dd010662da

ncacn_ip_tcp:srv03[49285]

 

UUID: 906b0ce0-c70b-1067-b317-00dd010662da

ncacn_ip_tcp:srv03[49285]

 

UUID: 906b0ce0-c70b-1067-b317-00dd010662da

ncacn_ip_tcp:srv03[49285]

 

UUID: 367abb81-9844-35f1-ad32-98f038001003

ncacn_ip_tcp:srv03[49159]

 

UUID: b97db8b2-4c63-11cf-bff6-08002be23f2f Microsoft Cluster Server API

ncacn_ip_tcp:srv03[49156]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_np:srv03[\\pipe\\lsass]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_ip_tcp:srv03[49155]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_np:srv03[\\pipe\\lsass]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_ip_tcp:srv03[49155]

 

UUID: 12345778-1234-abcd-ef00-0123456789ac

ncacn_np:srv03[\\pipe\\lsass]

 

UUID: 12345778-1234-abcd-ef00-0123456789ac

ncacn_ip_tcp:srv03[49155]

 

UUID: 12345778-1234-abcd-ef00-0123456789ac

ncacn_ip_tcp:srv03[49157]

 

UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service

ncacn_np:srv03[\\PIPE\\wkssvc]

 

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service

ncacn_np:srv03[\\PIPE\\W32TIME_ALT]

 

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 86d35949-83c9-4044-b424-db363231fd0c

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 86d35949-83c9-4044-b424-db363231fd0c

ncacn_ip_tcp:srv03[49154]

 

UUID: 3a9ef155-691d-4449-8d05-09ad57031823

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 3a9ef155-691d-4449-8d05-09ad57031823

ncacn_ip_tcp:srv03[49154]

 

UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API

ncacn_ip_tcp:srv03[49154]

 

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint

ncacn_ip_tcp:srv03[49154]

 

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint

ncacn_ip_tcp:srv03[49154]

 

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint

ncacn_ip_tcp:srv03[49154]

 

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs

ncacn_ip_tcp:srv03[49154]

 

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service

ncacn_ip_tcp:srv03[49154]

 

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service

ncacn_ip_tcp:srv03[49154]

 

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name

ncacn_ip_tcp:srv03[49154]

 

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name

ncacn_np:srv03[\\PIPE\\srvsvc]

 

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1

ncacn_np:srv03[\\PIPE\\atsvc]

 

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1

ncacn_ip_tcp:srv03[49154]

 

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1

ncacn_np:srv03[\\PIPE\\srvsvc]

 

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP

ncacn_np:srv03[\\pipe\\eventlog]

 

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP

ncacn_ip_tcp:srv03[49153]

 

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint

ncacn_np:srv03[\\pipe\\eventlog]

 

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint

ncacn_ip_tcp:srv03[49153]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint

ncacn_np:srv03[\\pipe\\eventlog]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint

ncacn_ip_tcp:srv03[49153]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint

ncacn_np:srv03[\\pipe\\eventlog]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint

ncacn_ip_tcp:srv03[49153]

 

UUID: 76f226c3-ec14-4325-8a99-6a46348418af

ncacn_np:srv03[\\PIPE\\InitShutdown]

 

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d

ncacn_np:srv03[\\PIPE\\InitShutdown]

 

Total endpoints found: 51

 

 

 

==== End of RPC Endpoint Mapper query response ====

portqry.exe -n srv03 -e 135 -p TCP exits with return code 0x00000000.

 

And

 

=============================================

 

 Starting portqry.exe -n srv04 -e 135 -p TCP ...

 

 

Querying target system called:

 

 srv04

 

Attempting to resolve name to IP address...

 

Name resolved to 172.16.140.11

 

querying...

 

TCP port 135 (epmap service): LISTENING

 

Using ephemeral source port

Querying Endpoint Mapper Database...

Server's response:

 

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d

ncacn_ip_tcp:srv04[1025]

 

UUID: 906b0ce0-c70b-1067-b317-00dd010662da

ncacn_ip_tcp:srv04[1143]

 

UUID: 906b0ce0-c70b-1067-b317-00dd010662da

ncacn_ip_tcp:srv04[1143]

 

UUID: 906b0ce0-c70b-1067-b317-00dd010662da

ncacn_ip_tcp:srv04[1143]

 

UUID: 367abb81-9844-35f1-ad32-98f038001003

ncacn_ip_tcp:srv04[1065]

 

UUID: b97db8b2-4c63-11cf-bff6-08002be23f2f Microsoft Cluster Server API

ncacn_ip_tcp:srv04[1057]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_np:srv04[\\pipe\\lsass]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_ip_tcp:srv04[1028]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_np:srv04[\\pipe\\lsass]

 

UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck

ncacn_ip_tcp:srv04[1028]

 

UUID: 12345778-1234-abcd-ef00-0123456789ac

ncacn_np:srv04[\\pipe\\lsass]

 

UUID: 12345778-1234-abcd-ef00-0123456789ac

ncacn_ip_tcp:srv04[1028]

 

UUID: 12345778-1234-abcd-ef00-0123456789ac

ncacn_ip_tcp:srv04[1084]

 

UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service

ncacn_np:srv04[\\PIPE\\wkssvc]

 

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 86d35949-83c9-4044-b424-db363231fd0c

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 86d35949-83c9-4044-b424-db363231fd0c

ncacn_ip_tcp:srv04[1027]

 

UUID: 3a9ef155-691d-4449-8d05-09ad57031823

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 3a9ef155-691d-4449-8d05-09ad57031823

ncacn_ip_tcp:srv04[1027]

 

UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API

ncacn_ip_tcp:srv04[1027]

 

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint

ncacn_ip_tcp:srv04[1027]

 

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint

ncacn_ip_tcp:srv04[1027]

 

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint

ncacn_ip_tcp:srv04[1027]

 

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs

ncacn_ip_tcp:srv04[1027]

 

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service

ncacn_ip_tcp:srv04[1027]

 

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service

ncacn_ip_tcp:srv04[1027]

 

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name

ncacn_ip_tcp:srv04[1027]

 

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name

ncacn_np:srv04[\\PIPE\\srvsvc]

 

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1

ncacn_np:srv04[\\PIPE\\atsvc]

 

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1

ncacn_ip_tcp:srv04[1027]

 

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1

ncacn_np:srv04[\\PIPE\\srvsvc]

 

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP

ncacn_np:srv04[\\pipe\\eventlog]

 

UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP

ncacn_ip_tcp:srv04[1026]

 

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint

ncacn_np:srv04[\\pipe\\eventlog]

 

UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint

ncacn_ip_tcp:srv04[1026]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint

ncacn_np:srv04[\\pipe\\eventlog]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint

ncacn_ip_tcp:srv04[1026]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint

ncacn_np:srv04[\\pipe\\eventlog]

 

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint

ncacn_ip_tcp:srv04[1026]

 

UUID: 76f226c3-ec14-4325-8a99-6a46348418af

ncacn_np:srv04[\\PIPE\\InitShutdown]

 

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d

ncacn_np:srv04[\\PIPE\\InitShutdown]

 

Total endpoints found: 50

 

 

 

==== End of RPC Endpoint Mapper query response ====

portqry.exe -n srv04 -e 135 -p TCP exits with return code 0x00000000.

 

  1. I have read the KB197814 and did the steps in it, restarted both servers, but the problem did not resolved.

 

  1. I have check both servers for RPC Service status and in both servers it has started.

 

  1. The both servers are alive and can ping each other by their IP address and name.

 

  1. The firewall of both servers is off and I stopped the Windows Firewall service COMPLETELY.

 

  1. Any services and applications that are depending on RPC have problems. For example when I want o remotely manages the services on these servers by using Services.msc console, the following error message appears:

Error 1726: The remote procedure call failed.

June 12th, 2013 12:40pm

Hi,

Thank you for your post.

I am trying to involve someone familiar with this topic to further look at this issue.

Free Windows Admin Tool Kit Click here and download it now
June 13th, 2013 7:44am

Anybody there?

June 21st, 2013 8:37am

have you checked firewall setting?

I also think it will be good to uninstall AV for some time and then see if it helps.. you may have to configure the netmon traces to see why you cant access the PRC related errors.

Mayank

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2013 8:58pm

Thanks for your advices. As I said before I have disabled the Windows Firewall service on both nodes and the nodes do not have any security applications installed, like antiviruses.

June 23rd, 2013 1:43am

Ok, it may sound a little weird but i will suggest you do this, enable the firewall and then create a rule to allow all all the inbound and outbound TCP and UDP connection. Not that i don't have trust on firewall but i have seen it resolving the firewall.

the DTCping output clearly suggest that there is a RPC communication issue which is causing this problem. lets keep on looking on the networking side..

Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2013 11:09am

Hi

We have similiar issue in our enviorment on 2012 server cluster. Everything including firewall, AV, network came clean. We then resolved it after rebuilding WMI on the servers individually.

Pls check this article on how to rebuild WMI: http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx.

Pls let us know if this helps.

Thanks

June 23rd, 2013 2:07pm

Hi ,

1. Run the following PowerShell cmdlet to check which nodes cause the issue.
 
From node 1
Get-WMIIobject -computername <node2> Win32_computerSystem 
 
From node 2
Get-WMIIobject -computername <node1> Win32_computerSystem

2. If you have found out the source and target nodes have the problem, please try to run the following command line to get the current MTU size.
 
Netsh int ipv4 sho int

3. Use Ping to check if you can ping the target node from the source node.
 
ping -l <MTUSize> <TargetIPAddress>

4. If you cant ping the target using this MTU size, please reduce the MTU size to the max value you can ping plus 28.  For example, if you can only ping l with 1472, then please adjust the MTU to 1500 (1472+28).
 
Change MTU via command line:
  
netsh interface ipv4 set subinterface <interfacenumber> mtu=1500 store=persistent

More information:
Recommended TCP/IP settings for WAN links with a MTU size of less than 576
http://support.microsoft.com/kb/900926

MTU
http://technet.microsoft.com/en-us/library/cc938197.aspx

Free Windows Admin Tool Kit Click here and download it now
June 24th, 2013 2:22pm
I did the procedures on the blog, restarted the servers and as mentioned the situation before, the problem still there...
June 25th, 2013 7:17am

I did as your advice. Enabled Windows Firewall service and created two rules: One of them enables all local ports on TCP and another one enabled all local ports on UDP. Although, configured Firewall Logging on both side to see if anything is blocking the traffic. After the problem occurred, verified the logged and saw that nothing has been logged...

As I said before, when I restart both servers, I can connect to two Failover Clustering manager console at the same time without any problems. But after some investigation I found that in one situation the problem occurs!

The problem occurs when I want to add a Virtual Machine role in one of the servers. When I try this action, the following error message appears:

After that, the following error messages appear when I execute the following command at both servers:

And in another server I encounter the following error while executing the same command:

getWmiObject : The RPC server is unavailble. (Exception from HRESULT: 0*800706BA)

Any ideas?

Thanks

Free Windows Admin Tool Kit Click here and download it now
June 25th, 2013 7:41am
I had the same issues when upgrading a cluster from 2008 r2 to 2012. I rebuilt the servers and same problem. eventually narrowed it down to the HP support pack. If i build a fresh physical server, i could validate the cluster from that node, prior to the HP support pack. Once I put the HP support pack on it it cannot join the cluster and all the RPC errors return. Rebuilt again and this time did not put the HP support pack on and it worked. managed to get the cluster working like this. I think it is the Network card driver but not 100% sure at this stage
August 6th, 2013 1:49pm

Hi ,

It is strange. The issue might be network related. Please first apply the hotfixes about cluster.

Recommended hotfixes
and updates for Windows Server 2012-based Failover Clusters

http://support.microsoft.com/kb/2784261

Then please check the NIC issue as smg1966 referred.

Free Windows Admin Tool Kit Click here and download it now
November 1st, 2013 2:32am

Hi, i experienced similar issue with windows 2012 R2 and applied with all latest and recommended update but still no luck. i'm wonder anyone in this forum able to solve this issue.

April 21st, 2015 10:00am

If you are using HP servers make sure you update the firmware of the network card. I have had the same issue multiple times with different models of HP mainly DL360/380 G6 or G7. 

Its to do with problems with the MTU size. you can test it by changing the MTU to lower than 1500 and everything should work.

this command shows the MTU

Netsh int ipv4 sho int

This changes it for interface number 11

netsh int ipv4 set subinterface 11 mtu=1300 store=persistent

but HP fixed it in one of the revisions of the nic firmware so try that and the latest driver first.

Free Windows Admin Tool Kit Click here and download it now
April 21st, 2015 10:08am
We're using dell server. We have updated our 3 servers with latest nic driver but the issue always on server first server while the other 2 servers are working fine. What else shall i check ?
April 21st, 2015 10:14am

i would suggest you change the mtu.

try pinging between the servers with an mtu size of 1500 to see if it fails. If it does try 1472 to see if that works.

ping -l 1500 servername

Free Windows Admin Tool Kit Click here and download it now
April 21st, 2015 10:22am

ping with mtu 1500 giving no issue at all.

I tried wmi connection and testing and everything works well too.

what else shall I do ? shall I go and reset wmi ?

April 22nd, 2015 2:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics