![]() ![]() Left-click on Diagnostic to view the logging captured. Note: The debug tracing will be generated to the Diagnostic channel and viewable only after you disable logging. Debug tracing can be turned on with the following steps:Īpplications and Services Logs \ Microsoft \ Windows \ FailoverClustering-Client \ Diagnostic ![]() If you are unable to pinpoint the root cause of the failure by neither the Validate report nor the Create Cluster log, then verbose debug logging can be enabled. Step 3: Turn on Cluster API Debug Tracing For example in the CreateCluster.mht snippet below you can infer that there was a problem with configuring a Cluster Name Object for the cluster. The admin level logging in the CreateCluster.mht file can help you determine the step at which the cluster creation process failed. Note: In Windows Server 2016 the report is changed from. The file can be found in the following location:Ĭ:\Windows\Cluster\Reports\CreateCluster.mht This file is created during the cluster creation process through the “Create Cluster” wizard in Failover Cluster Manager or the Create-Cluster Failover Clustering Windows PowerShell® cmdlet. If you cannot successfully create a cluster after all your validation tests are passing, the next step is to examine the CreateCluster.mht file. For example, the Active Directory Configuration test warning below flags a potential cluster creation problem: It is also useful to investigate the warnings flagged by validate. For instance, in the example below we can detect an invalid Windows Firewall Configuration. The validation summary provides a starting point to drill down further into the failure. Note: You can also use the Failover Clustering Windows PowerShell® cmdlet,ĭirectory and open the Validation Report. Open the Failover Cluster Manager snap-in ( The first thing to do when troubleshooting, and something you should do every time you create a cluster is to run the Validate tool. The cluster validation tool runs a suite of tests to verify that your hardware and settings are compatible with failover clustering. In this blog, I will outline the steps in order to troubleshoot “Create Cluster” failures with Windows Server 2012 or later Failover Clustering. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |