Server Manager problem: Online - Data retrieval failures occurred

Martinik 

I rebuilt a 3-node cluster with Server 2022 Data Canter over a dozen times, I even rebuilt the DC on each occasion to reduce the chance of left over or invalid settings in the metadata.  Every time, I was able to get a perfect cluster with no errors or warnings on the cluster diagnostic tests however as soon as the first server rebooted after creating the cluster, these errors started on all nodes and they even applied to the local server, ie. server1 couldn’t access its own logs according to the warnings.   Even leaving the systems for 24 hours in case the errors went away had no effect.

I am not sure if ignoring these warnings would have any long-term effect on the running of the system, I couldn’t find anything online about the repercussions of doing this and I didn’t want to take a chance since this will be a production environment hosting my customers VMs and data.

The final straw was that I changed from using Server 2022 to Server 2019 Datacentre (just as a test), leaving everything else identical down to the server names, procedures I used and the order in which I performed them, the passwords and user accounts, everything identical other than the version of Server I installed and I didn’t get ANY of these data retrieval warnings, everything worked perfectly first go.  I can only assume that there is a major bug in Server 2022 or at least a bug that happens when using my combination of hardware, all desktop 12th gen i9-12900K CPU, 128GB DDR4, and Z690 motherboards. and Dell / Intel dual copper 10GB ethernet adapters, 4 x 9tb HDDs, 3 x 2TB NVMe SSDs and OS drive on each server node and a smart 10GB switch and brand new cat7 cables.

I made sure to install all available updates and drivers at each stage of the setup on each node, made sure the hardware and software was exactly the same on all nodes, I followed all the various online suggestions like changing registry keys, changing permissions on the winevt folder and winevt\data folder, wiping the logs and starting fresh, giving all cluster nodes and objects permissions as domain, local and enterprise admins, and nothing worked for me.   I did come across a few "fixes" online that simply supressed the warnings but none of them actually fixed the cause of the warnings.  I can only assume the warnings are correct and there were issues with accessing logs so supressing the warning messages was not a proper solution since the problem isn’t fixed, its just hidden from view.

My advice to anyone who can, is to change to Server 2019 if you aren’t able to get things working with 2022 - perhaps MS will create a patch to fix this problem but as of writing this, June 12 2023, I found it impossible to setup a stable working cluster on server 2022 despite over a dozen tries, each time with a completely clean slate, wiped drives and fresh DC.