I have this odd issue that started sometime after I upgraded to NPM 12.1 and SAM 6.3 that after speaking to a colleague who is also in a SolarWinds shop on the same versions is seeing the same behavior. Randomly always in the early AM hours, (not associated with database maintenance or anything else that I've found) SAM Polling will stop or essentially die on a polling engine. I've had this happen now on two different polling engines. My System event logs are flooded with DCOM errors indicating communication failures on all protocols, which I know is SAM related. Applications start going into unknown status in mass. Stopping and restarting services does not solve this issue. Only a full reboot of the polling engine seems to resolve the problem.
I've opened a couple of tickets with support over the last few months and most recently have been told its due to too many SAM components. Which *could* I guess be the case, although, my polling engines seem healthy otherwise, SAM Polling %'s are low etc. Now after verifying with my colleague, his numbers are certainly lower than the capacity marks, yet he see's the same problem. I'm wondering if anyone else has also experienced this or has come up with a solution for this issue.
