An enabled computer account (object) for was found.ġ. “Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory”ĭid you really review the links above? Here’s a quick test… How would you fix the following “Create Cluster” errors?ġ. “How to Create a Cluster in a Restrictive Active Directory Environment” The number one reason for create cluster failures is due to misconfigured permissions in Active Directory environments resulting in failures while creating the Cluster Name Object (CNO).
EVENT ID 1146 MICROSOFT WINDOWS FAILOVER CLUSTERING TOOLS WINDOWS
The cluster log can be generated in local time using Failover Clustering Windows PowerShell®: This generates significant spew so the default level should be restored once the troubleshooting is completed. However, if this verbosity level is not capturing the data you need, you can increase the verbosity level. This proves to be sufficient for most debugging purposes. Note: The default verbosity level for the cluster log is 3. You can generate the cluster log using the Failover Clustering Windows PowerShell® cmdlet The cluster log can be generated even when the cluster creation fails by specifying the node to collect the log on. The cluster log provides verbose logging for the cluster service and allows advanced troubleshooting. Msg: Failed to create cluster name test-33 on DC \\.
![event id 1146 microsoft windows failover clustering tools event id 1146 microsoft windows failover clustering tools](https://docs.microsoft.com/th-th/windows-server/troubleshoot/media/troubleshooting-cluster-event-id-1135/18653.png)
"CreateCluster: Create cluster failed with exception. The following are some examples of Cluster API event log traces found for a “create cluster” failure.ĬreateCluster: Create cluster test-33 will be using a Read-Write DCĬreateClusterNameCOIfNotExists: Failed to create computer object test-33 on DC \\ with OU ou=clusterou Note that the ‘-o’ parameter determines where the CSV dump file is generated.
![event id 1146 microsoft windows failover clustering tools event id 1146 microsoft windows failover clustering tools](https://image.slideserve.com/447972/cluster-debug-logging-l.jpg)
Open the generated Comma Separated Value (CSV) dump file and examine the User Data column for potential issues. Tracerpt clusapi.etl -of CSV –o c:\report.csv Logman start clusapiLogs -p -o clusapi.etl -ets The following are the steps to configure: The debug information obtained will be the same as Step 3 but you are able to set this up using a script. You can also turn on the Cluster API event log tracing programmatically. Step 3b: Turn on Cluster API Event Log Tracing Programmatically
![event id 1146 microsoft windows failover clustering tools event id 1146 microsoft windows failover clustering tools](https://www.lansweeper.com/wp-content/uploads/2019/07/scanning-windows-failover-cluster-details-and-logs-4.jpg)
Permission on the organizational unit (OU) in Active Directory. In this case, the cluster administrator does not have the The following are examples of events generated to the Diagnostic channel when cluster creation fails when the Cluster Name Object cannot be added to the clusterou container. 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
![event id 1146 microsoft windows failover clustering tools event id 1146 microsoft windows failover clustering tools](https://i2.wp.com/lokna.no/wp-content/uploads/2012/10/SNAGHTMLafd29c7.png)
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.