msterling

It was the system clock. It was set to the wrong time, once I set it up to use ntp all rules began firing!

Anyone have any idea about this? I recently put these PCs in after they had been offline for quite some time, could that effect it?

After talking with support, you have to go to the node and make sure the Windows Logging tools are started, then make a filter that uses ServiceWarning.DetectionIP = *<node name>* This works great and logs all warnings and errors from the event log!

I still can't make this work, the tools are started but I can't come up with a filter to show the event log messages...

Restarting the Manager service is definitely the way to solve this problem (for the short term). With our implementation the culprits seem to have been 4-5 internal SolarWinds rules firing almost non-stop (due to the lack of configuration, someone used the default settings). Once I disabled these rules, the lock up seems…