Errors in Event Log from servers with > 32 logical CPUs

This does appear to be an issue with WMI-based polling and >32 CPUs. Unfortunately I don't have a 40-core box to test with off hand- if you switch to SNMP polling, are we able to to return data for all CPUs?

Good idea.  I have another 40-core server that was using SNMP already, but I hadn't thought to check.  Indeed I do see data on all 40 cores for it in Manage Nodes.  Strange though, that server also has all the 2006 entries filling up the App Event Log.  Maybe they're coming from somewhere else after all?  

Next I will unmanage the node and see if the messages are still logged on that machine.  If they are, then I guess I can't blame SAM.

It may be possible that these EventIDs are being generated by Windows Service or Process component monitors in SAM. You may want to try changing the applications assigned to that node to use the 64bit Job Engine and see if the Windows Events no longer continue to appear. Another option might be to change the fetching method for those process and service monitors to use RPC instead of WMI.

Hey, interesting.  I knew about the 32/64bit polling option a long time ago when writing a bunch of PowerShell components, but forgot all about it.    I'll give that a shot.

Hello,

Just one note: The node properties like CPU, memory, volumes, interfaces, hardware health information, asset inventory information are polled through 32-bit process. You can switch to use 64-bit process only for SAM applications. We will consider the possibility to use 64-bit process also for node properties (it is tracked internally under FB275825).

Lukas Belza (SolarWinds development)

Thank you for the information.  My test of unmanaging the node did prove that the events were coming from SAM polling.  I also ran the same test with our Nagios server and found that Nagios's check_nt plugin causes the same issue, so it's not like this is uncommon.

I see this post is a year old now but is it still the case that you cannot upgrade the node properties like CPU, memory, volumes, interfaces, hardware health information, asset inventory information to 64-bit?

I'm having the same problem as the original poster but with just the basic node properties from NPM.  The host that is being polled has 40 logical processors so the 32-bit process is returning the above error every 5 minutes.

MS released the following patch for the 64-bit processes if you have more then 64 logical processors but I don't see one for 32-bit. http://support.microsoft.com/kb/2733563

I am seeing a lot of these as well. Wondering what a fix might be?

You may consider changing the node polling method from WMI to SNMP for nodes that exhibit this behavior.

The problem is even when you use SNMP it still access WMI after it connects to the node.  So SNMP connects and then uses WMI to grab performance data which generates the error.