-->![Event Id 1146 Microsoft Windows Failover Clustering Tools Event Id 1146 Microsoft Windows Failover Clustering Tools](https://i.ytimg.com/vi/lAjbIMF1lAE/maxresdefault.jpg)
- Event Id 1146 Microsoft Windows Failover Clustering Tools List
- Windows Server Failover Cluster
- Windows Failover Cluster Best Practices
- Event Id 1146 Microsoft Windows Failover Clustering Tools Free
- Event Id 1146 Microsoft Windows Failover Clustering Tools Download
Applies to: Windows Server 2019, Windows Server 2016, Windows Server
Windows Error Reporting (WER) is a flexible event-based feedback infrastructure designed to help advanced administrators or Tier 3 support gather information about the hardware and software problems that Windows can detect, report the information to Microsoft, and provide users with any available solutions. This reference provides descriptions and syntax for all WindowsErrorReporting cmdlets.
The information on troubleshooting presented below will be helpful for troubleshooting advanced issues that have been escalated and that may require data to be sent to Microsoft for triaging.
To open Event Viewer and view events related to failover clustering: If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. Windows Server 2016 includes site-aware failover clusters that enable group nodes in stretched clusters, based on their physical location (site). Cluster site-awareness enhances key operations during the cluster lifecycle, such as failover behavior, placement policies, heartbeat between the. Event ID 1206 — Active Directory Permissions for Cluster Accounts. Updated: December 5, 2007. Applies To: Windows Server 2008. When you create a new clustered service or application, a computer object (computer account) for that clustered service or application must be created in. The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource vendor.
Enabling event channels
When Windows Server is installed, many event channels are enabled by default. But sometimes when diagnosing an issue, we want to be able to enable some of these event channels since it will help in triaging and diagnosing system issues.
You could enable additional event channels on each server node in your cluster as needed; however, this approach presents two problems:
- You have to remember to enable the same event channels on every new server node that you add to your cluster.
- When diagnosing, it can be tedious to enable specific event channels, reproduce the error, and repeat this process until you root cause.
To avoid these issues, you can enable event channels on cluster startup. The list of enabled event channels on your cluster can be configured using the public property EnabledEventLogs. By default, the following event channels are enabled:
Here's an example of the output:
The EnabledEventLogs property is a multistring, where each string is in the form: channel-name, log-level, keyword-mask. The keyword-mask can be a hexadecimal (prefix 0x), octal (prefix 0), or decimal number (no prefix) number. For instance, to add a new event channel to the list and to configure both log-level and keyword-mask you can run:
If you want to set the log-level but keep the keyword-mask at its default value, you can use either of the following commands:
If you want to keep the log-level at its default value, but set the keyword-mask you can run the following command:
If you want to keep both the log-level and the keyword-mask at their default values, you can run any of the following commands:
These event channels will be enabled on every cluster node when the cluster service starts or whenever the EnabledEventLogs property is changed.
Gathering Logs
After you have enabled event channels, you can use the DumpLogQuery to gather logs. The public resource type property DumpLogQuery is a mutistring value. Each string is an XPATH query as described here.
When troubleshooting, if you need to collect additional event channels, you can a modify the DumpLogQuery property by adding additional queries or modifying the list.
To do this, first test your XPATH query using the get-WinEvent PowerShell cmdlet:
Next, append your query to the DumpLogQuery property of the resource:
And if you want to get a list of queries to use, run:
Gathering Windows Error Reporting reports
Windows Error Reporting Reports are stored in %ProgramData%MicrosoftWindowsWER
Inside the WER folder, the ReportsQueue folder contains reports that are waiting to be uploaded to Watson.
Here's an example of the output:
Inside the WER folder, the ReportsArchive folder contains reports that have already been uploaded to Watson. Data in these reports is deleted, but the Report.wer file persists.
Here's an example of the output:
Windows Error Reporting provides many settings to customize the problem reporting experience. For further information, please refer to the Windows Error Reporting documentation.
Troubleshooting using Windows Error Reporting reports
Physical disk failed to come online
To diagnose this issue, navigate to the WER report folder:
Here's an example of the output:
![Event Id 1146 Microsoft Windows Failover Clustering Tools Event Id 1146 Microsoft Windows Failover Clustering Tools](https://i.ytimg.com/vi/lAjbIMF1lAE/maxresdefault.jpg)
Next, start triaging from the Report.wer file — this will tell you what failed.
Since the resource failed to come online, no dumps were collected, but the Windows Error Reporting report did collect logs. If you open all .evtx files using Microsoft Message Analyzer, you will see all of the information that was collected using the following queries through the system channel, application channel, failover cluster diagnostic channels, and a few other generic channels.
Here's an example of the output:
Event Id 1146 Microsoft Windows Failover Clustering Tools List
Message Analyzer enables you to capture, display, and analyze protocol messaging traffic. It also lets you trace and assess system events and other messages from Windows components. You can download Microsoft Message Analyzer from here. When you load the logs into Message Analyzer, you will see the following providers and messages from the log channels.
You can also group by providers to get the following view:
Windows Server Failover Cluster
To identify why the disk failed, navigate to the events under FailoverClustering/Diagnostic and FailoverClustering/DiagnosticVerbose. Then run the following query: EventLog.EventData['LogString'] contains 'Cluster Disk 10'. This will give you give you the following output:
Physical disk timed out
To diagnose this issue, navigate to the WER report folder. The folder contains log files and dump files for RHS, clussvc.exe, and of the process that hosts the 'smphost' service, as shown below:
Here's an example of the output:
Next, start triaging from the Report.wer file — this will tell you what call or resource is hanging.
Windows Failover Cluster Best Practices
The list of services and processes that we collect in a dump is controlled by the following property: PS C:Windowssystem32> (Get-ClusterResourceType -Name 'Physical Disk').DumpServicesSmphost
Event Id 1146 Microsoft Windows Failover Clustering Tools Free
To identify why the hang happened, open the dum files. Then run the following query: EventLog.EventData['LogString'] contains 'Cluster Disk 10' This will give you give you the following output:
Event Id 1146 Microsoft Windows Failover Clustering Tools Download
We can cross-examine this with the thread from the memory.hdmp file: