J
Jay J Aquina
Hi all,
This seems to be an old topic, I found a lot of similar questions around, many for Windows 2008 (R2) and there seems to be a hotfix for that version but none for Windows 2012 R2, not that I could find.
So here is my scenario.
Dell PowerEdge R730xd
Two processors, 24 core each (physical + HT) totaling 48 cores
64 Gb RAM
Windows 2012 R2 standard installed from scratch, added Failover Clustering feature, all updates done with Windows Update (none remaining).
No other software installed, only Windows, nothing else.
Every hour or so, not precisely, I have a group of three identical occurrences of this event on the Application Log.
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.
I've read somewhere that this could be caused by 32 bits application pooling the WMI framework on servers with more then 32 processors. Well, I have no third party software installed on this server, only Microsoft stuff.
I started digging a little bit using Procmon trying to find some clue of what is going on. Added a trigger on the Event viewer to fire Procmon on the first event 2006. A lot of information there, none that I could find useful for my knowledge.
Something very strange is that according to Procmon, the main WMI process is a 32 bit process. Could this be the culprit? Is this information correct?
So here am I, asking what seems to be a very old question and trying to get some new answers.
Thanks a lot for your thoughts!
Jay
Continue reading...
This seems to be an old topic, I found a lot of similar questions around, many for Windows 2008 (R2) and there seems to be a hotfix for that version but none for Windows 2012 R2, not that I could find.
So here is my scenario.
Dell PowerEdge R730xd
Two processors, 24 core each (physical + HT) totaling 48 cores
64 Gb RAM
Windows 2012 R2 standard installed from scratch, added Failover Clustering feature, all updates done with Windows Update (none remaining).
No other software installed, only Windows, nothing else.
Every hour or so, not precisely, I have a group of three identical occurrences of this event on the Application Log.
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.
I've read somewhere that this could be caused by 32 bits application pooling the WMI framework on servers with more then 32 processors. Well, I have no third party software installed on this server, only Microsoft stuff.
I started digging a little bit using Procmon trying to find some clue of what is going on. Added a trigger on the Event viewer to fire Procmon on the first event 2006. A lot of information there, none that I could find useful for my knowledge.
Something very strange is that according to Procmon, the main WMI process is a 32 bit process. Could this be the culprit? Is this information correct?
So here am I, asking what seems to be a very old question and trying to get some new answers.
Thanks a lot for your thoughts!
Jay
Continue reading...