Comments
-
Thanks, stopping Solarwinds Agent, Net TCP Port Sharing Service & Message Queuing and killing a Trap Viewer for good measure that someone had left running solved it for me. The other above recommendations did not solve the problem on their own.
-
Thanks, that was very helpful, it seems weird with all of the searches I have done I have never seen Hubble mentioned. The main holdup seems to be in the database query in Orion.HardwareHealth.HardwareItemBase which takes about 30 seconds. When I run the Database Maintenance manually it just hangs when it tries to process…
-
Another tip from our VMware admin is that if you want to exclude specific hosts under a vCenter from VMAN Orion monitoring, set No Access for the solarwinds user for those hosts, that can be set at the folder level for example we have a Maintenance folder. That is to work around the fact that VMAN Orion polling seems to be…
-
Here is the article that confused me Requirements for monitoring ESXi and ESX Servers - SolarWinds Worldwide, LLC. Help and Support I found that while troubleshooting the lack of detailed Volume and Interface information. It says that SNMP is required with ESXi 6.0, but does not explain how you are supposed to configure…
-
Thanks for the suggestion. All of the blades were already set to Basic. On a whim, I deleted all of the blades and left just the vCenter server then was indeed able to switch to VMAN Orion. I believe that my confusion stemmed from a (possibly older) article that said in order to get detailed network statistics from ESXi,…
-
With ProcessExplorer from SysInternals Suite I searched for handles with swdebugMaintenance and found a Database Maintenance process that was still stuck in the background, don't know why I didn't find it with regular Task Manager. I killed that process, then was able to run Database Maintenance manually and it finally…
-
It looks like stopping and disabling the User Access Logging Service (UAL) on the SQL server and all of the SolarWinds servers has resolved the problem. UAL is enabled by default on Windows Server >= 2012. We are not using SQL Server Reporting Services and do not have AppInsight for SQL configured. I speculate that it…
-
The problem seems to involve multiple ESENT processes trying to access C:\Windows\system32\LogFiles\Sum\Api.log simultaneously possibly related to this article. https://support.microsoft.com/en-us/help/2811566/error-1032-messages-in-the-application-log-in-windows-server-2012