Created:
11/4/2009 1:59:08 PM

Author:
Przemek Radzikowski

permalink [Permalink]





International Careers & Jobs - An international employment directory, reviewing world-wide top job sites




  • Home  ›
  • Articles  ›
  • Failover Cluster Validation Error 80070005 on Windows Server 2008 R2 x64



| More

Failover Cluster Validation Error 80070005 on Windows Server 2008 R2 x64

A few unlucky people out there may have decided to create a clean Microsoft Windows Server 2008 R2 x64 Failover Cluster and inadvertently run into the 80070005 error when creating the server side agent (CPrepSrv) COM component from IClassFactory. This article outlines a possible solution to the problem.


 

 

Introduction to Error 80070005

Since the release of Windows Server 2008 x64, I’d created many failover clusters, both in my test lab as well as for clients in production environments. I know the whole process well enough to execute in my sleep and this time was working to create a cluster for my Exchange 2010 deployment. So it came to me as a bit of a surprise that I couldn’t make the R2 version of Windows Server 2008 work quite so easily and kept coming up against the Failover Cluster validation error 80070005.

The following two errors would show up in the Failover Cluster Validation Report:

Validate the cluster networks that would be created for these servers.

An error occurred while executing the test.
There was an error initializing the network tests.
There was an error creating the server side agent (CPrepSrv).
Creating an instance of the COM component with CLSID {E1568352-586D-43E4-933F-8E6DC4DE317A} from the IClassFactory failed due to the following error: 80070005.


Validate that IP addresses are unique and subnets configured correctly.

An error occurred while executing the test.
There was an error initializing the network tests.
There was an error creating the server side agent (CPrepSrv).
Creating an instance of the COM component with CLSID {E1568352-586D-43E4-933F-8E6DC4DE317A} from the IClassFactory failed due to the following error: 80070005.

Out of frustration I tried to form the cluster without running the validation tests. Even with this approach I would receive an error: The operation has failedAn error was encountered while loading the network topology. Error Code: 0x80070005, Access is denied.

The Operation has failed 80070005

Resolving the 80070005 Failover Cluster Error

At first I didn’t know where to start so I double checked the basics, such as my Private and Public network settings. DNS resolution and whether I was able to ping the Domain Controller (also a Windows Server 2008 R2 server). Of course, the Cluster Validation tool does many of these tests for us so some of the tests were a stab in the dark.

The following list outlines what I tried in order to get the cluster validation process to work:

  1. IP Address of the network cards - Check network configuration of your Public and Private Network interfaces on the failover cluster nodes, making sure you haven't made any silly mistakes.
  2. Firewall configuration – temporarily, I completely disabled the firewall on both the failover cluste nodes as well as the domain controller. In my case, it did not fix the problem.
  3. Default gateway – because I was building the environment in a test lab, I hadn’t specified a default gateway because the failover cluster nodes were all on a single subnet. In the end I added in a default gateway of 10.0.0.254 (your may be different depending on your subnet).
  4. Network Binding – I double checked the network binding order making sure that the Public network card is at the top, above the Private network card.
  5. Rejoin domain - Take the failover cluster nodes out of the domain and rejoin again. Some reports have shown this to also fix the problem.
  6. Use a Windows Server 2003 Domain Controller – out of desperation and needing the environment up and running, I commissioned a Windows Server 2003 based domain controller, joined both nodes to the new domain and run the validation test again. This last one worked for me.

Not having enough time to troubleshoot this completely – I suspect that it may be a COM authentication error. Somewhere on my internet travels I remember it being mentioned that reapplying permissions on the COM object would also do the trick. But my Windows Server 2003 domain controller had by that stage fixed my problem.

If I ever get to the bottom of this problem I’ll update the page – feel free to contact me if one of you has found another workaround or solution to the problem. I’ll be happy to include it in this article.

Conclusion

The Failover Cluster Validation tool is a great step forward in analyzing server components for anomalies before creating the cluster. Overall, the Failover Cluster validation tool manages to point out many of the common mistakes which would otherwise plague the deployment – if not immediately, perhaps in the future. Some error messages however, are rather vague and do not lend themselves to easy diagnosis. This article did at least try to suggest some reasons behind the 80070005 error when creating the Failover Cluster.

References

Failover Cluster Step-by-Step Guide: Validating Hardware for a Failover Cluster
http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx

 

permalink [Permalink] - Updated: Monday, October 28, 2013





| More

 

Articles of Interest


International Careers & Jobs - An international employment directory, reviewing world-wide top job sites


 
 
(c) Capitalhead Pty Ltd
Contact Capitalhead About Us Articles & Publications Partners Solutions & Services Products Valid XHTML Valid CSS