Problem
The Failover Cluster validation report shows an error for Inventory, List Operating System Information:
An error occurred while executing the test. There was an error getting information about the operating systems on the node. Culture is not supported. Parameter name: culture 3072 (0x0c00) is an invalid culture identifier.
If you look at the summary for the offending node, you will find that Locale and Pagefiles are missing.
Analysis
Clearly there is something wrong with the locale settings on the offending node. As the sample shows the locale is set to nb-NO for Norwegian, Norway. I immediately suspected that to be the culprit. Most testing is done on en-US, and the rest of us that want to see a sane 24-hour clock without latin abbreviations and a date with the month where it should be located usually have to suffer.
I was unable to determine exactly where the badger was buried, but the solution was simple enough.
Solution
Part 1
- Make sure that the Region & language and Date & Time settings (modern settings) are set correctly on all nodes. Be aware of differences between the offending node and working nodes.
- Make sure that the System Locale is set correctly in the Control Panel, Region, Administrative window.
- Make sure that Windows Update works and is enabled on all nodes.
- Check the Languages list under Region & Language (modern settings). If it flashes “Windows update” under one or more of the languages, you still have a Windows Update problem or an internet access problem.
- Try to validate the cluster again. If the error still appears, go to the next line.
- Run Windows Update and Microsoft Update on all cluster nodes.
- Restart all cluster nodes.
- Try to validate the cluster again. If the error still appears, go to part 2.
Part 2
- Make sure that you have completed part 1.
- Go to Control Panel, Region.
- In the Region dialog, locate Formats, Format.
- Change the format to English (United States). Be sure to select the correct English locale.
- Click OK.
- Run the validation again. It should be successful.
- Change the format back.
- Run the validation again. It should be successful.
If you are still not successful, there is something seriously wrong with you operating system. I have not yet had a case where the above steps does not resolve the problem, but I suspect that running chkdsk, sfc -scannow or a full node re-installation would be next. Look into the rest of the validation report for clues to other problems.
