Jul 31 2017 01:22 AM
Has anyone started seeing this on Windows Server 2016?
Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information.
We have this on two of our Cluster at the moment. The same two nodes also end up having issues draining and will lock resources. The other 2 nodes are fine as far as I can see
Aug 24 2017 04:07 AM
Aug 30 2017 11:55 AM
I've gotten this error on most of my Windows 2016 servers for months now, and have never been able to resolve it.
This kind of discussion about 3rd-part apps and 32-bit is typical, but totally unhelpful: https://social.technet.microsoft.com/Forums/ie/en-US/768d88f4-1742-494a-bfc4-a4bf9e228a67/unable-to-...
Oct 04 2017 09:28 AM
Im having the same issue with my hosts in a hyperV cluster. any solution to this issue?
thanks,
Dec 06 2017 12:57 AM
Unfortunately its getting worse and is making certain issues harder to diagnose when Event Viewer doesn't work!
Dec 06 2017 06:24 AM
Mine is on a 2012 r2 HyperV cluster. It even pop up on my newly added host to the cluster. I wonder if anyone talk to microsoft about this?
May 11 2018 11:25 AM
I have the same issue. It bothers me most on my 2016 Hyper-V hosts. Does anyone else have Veeam One running in their environment? I found another forum that suggested it might be triggering this.
May 11 2018 12:07 PM
I do have veeam ONE running on my environment. I use it to monitor my Hyper V Cluster.
Nov 07 2018 02:41 AM
Same problem here. Anyone found a solution?
Nov 07 2018 06:13 AM
if you have veeamOne, uninstall that. that's what i did and no more error.