Abstract: On your Windows 2012 R2 server you see the event 2017 (Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.) inside the eventlog and wish to solve that.
The full message looks like the following:
Log Name: Application
Source: Microsoft-Windows-PerfOS
Date: 08.10.2016 12:42:23
Event ID: 2017
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: server01.int.contoso.com
Description:
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PerfOS" Guid="{F82FB576-E941-4956-A2C7-A0CF83F6450A}" EventSourceName="PerfOS" />
<EventID Qualifiers="32768">2017</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-10-08T10:42:23.000000000Z" />
<EventRecordID>660656</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>server01.int.contoso.com</Computer>
<Security />
</System>
<EventData>
<Binary>05000080</Binary>
</EventData>
</Event>
Solution 1:
A possible solution might be to rebuild the performance counter via lodctr (run inside a “run as admin” CMD):
lodctr /R
If this caused the error message:
Error: Unable to rebuild performance counter setting from system backup store, error code is 2
run it a 2nd time until it shows:
Info: Successfully rebuilt performance counter setting from system backup store
Solution 2:
Another possible solution might be to check the page file (it shouldn´t be fully disabled) on the affected server and re-adjust that if needed.
Cross reference:
https://social.technet.microsoft.com/Forums/en-US/51b39ba4-efbd-42f1-a254-07b22050e4cf/2012-r2-numa-warning?forum=winservergen
