pstranak ✭✭✭✭✭

That is correct. Starting with 2017.x, HardwareHealth is no longer bound to just nodes. We can also use it with Orion Storage Resource Monitor entities. Hence the change from "NodeId" to something more universal.

Hi, did you try to connect to the SQL server from SQL Server Management studio (or something like that) using the same credentials? Ideally from the Orion poller. It looks like the used account can connect to the SQL server, but it cannot access databases hosted there.

Hi, in that case you need to use "NodeId" instead of "HardwareInfoID" when you create "HardwareHealthItemKey". "HardwareInfoID" is used in newer versions of HardwareHealth. So, your script should look like this: $swis = Connect-Swis -Hostname $hostname -Trusted # you need these three properties from the sensors to disable…

According to Requirements section in Installing the .NET Framework‌, Windows 2003 needs to have Windows Imaging Component (WIC) already installed. Windows XP already has it. If Agent supported Windows 2003, it probably would contain WIC installer as well.

Great! Thank you izzy_g for letting us know.

Hi, I'm not sure why you see such behavior. Especially the part about automatically re-enabled sensors. That should not happen. If you really see such behavior (a sensor, that was manually disabled gets re-enabled again), I'd suggest opening a support ticket. That way it would be easier to troubleshoot the problem and…

Hi, I don't think you can do it with FileSize monitor. But you could use one of the Script monitors and set threshold on its statistic value. For example PowerShell script would look like this: $filename = (Get-Date -format yyyyMMdd) + ".dbf" $path = $args[0] + $filename Write-Host 'Statistic: ' (Get-Item $path).Length and…

Hi The Agent does not download the .Net from internet. It has a copy of an offline .Net instalation package on the Orion server (around 50 MB). If the Agent can comminicate with Orion, there should be no other things to configure. Maybe you have a slow connection between the Agent and its Orion server, so the download…

Maybe you could try a PowerShell or Windows Script monitor. During polling, it would check all files in the directory and return them as one or more statistics/messages. It would be Up or Down, based on whether at least one such file would be found. And then you could set an alert on the component. I'm sure there would be…

Maybe this could be the issue: https://support.microsoft.com/en-us/kb/2015129 ?

Hi, I don't know much about the missing performance counters. But the second error message seems quite descriptive. Are you sure, you can connect from Poller used to monitor the SQL server to the SQL server? Using WBEMTEST.EXE with that credentials?

Hi, you say the two SQL 2012 servers, that are not working are using AllwaysOn. In that case, the problem might be related to Connection Timeouts in Multi-subnet Availability Group - AlwaysOn Professional - Site Home - MSDN Blogs. SAM 6.1.1 is compiled with .Net 4.0 and I doubt it modifies connection strings to support…

Hi, is the command line of the problematic process always the same or different?

Hi, what are you using to monitor the website? AppInsight for IIS, some other SAM template? Or a SolarWinds Web Performance Monitor?

Hi Do you mean that HTTP(S) monitors do not work as you expect? Could you share what the problem is?

Also (and unfortunately), "ComponentPID" in "Orion.APM.CurrentStatistics" always returns "-1" - it's hardcoded, because it was deprecated a few years ago. Currently, there is no way of getting process ID from SWIS. You would need to use SQL queries instead.

Hi, if you want to filter "Top 10 Monitored Processes ..." resources by process name, use filter "MonitorStatus.ProcessName like 'svchost.exe'". Not "pe.Name like 'svchost.exe'". The latter one doesn't work in SAM 6.2.

Hi I don't know why we cannot select any future date in the picker. However, you can type any valid date in the dialog and it will work.