seniorza

Thanks for the assistance. We've opted to reinstall the agents where this problem occurred and things are back in working order.

Thanks for the help! Works perfectly!

Many thanks!

Thanks - I've posted a new feature request for SAM.

Thanks - I think it's one of the new nodes that's causing the issue so I've been going through a process of elimination. Has SAM 6.2.2 been released yet? I'm going to apply Hotfix 3 now.

Hi tdanner​, I'm trying to execute the following via the Powershell cmdlet to clear an alert with AlertObjectID 28071: $alertid = [int]28071 Invoke-SwisVerb $swis Orion.AlertActive ClearAlert $alertid I'm then met with this: Invoke-SwisVerb : Verb Orion.AlertActive.ClearAlert cannot unpackage parameter 0 of type…

Hi aLTeReGo, Thanks for the reply. The server disk space is fine. An instruction was sent to the node via the service control manager to restart the SolarWinds Agent Service after job scheduler errors were reported. Is it possible that there is a queued action for the service restart that is causing this behaviour? Thanks,…

Thanks for this option aLTeReGo. Is there no way I can create a report data source for appinsight databases and then graph multiple databases total sizes in one graph?

Hi chrispaap, Thanks for the reply. No, nothing new has been installed on the servers.

Thanks - I was afraid of that. So there's no possible workaround for my scenario? Is it not possible to change the polling IP for the SW node to the VIP of the SQL resource and assign AppInsight for SQL?

Hey mwb, It was definitely load-based. I first increased the polling intervals (to 600s) for the appinsight for SQL application monitors. I also enhanced the disk performance (through striping) on the SQL Server instance hosting the Orion database. I've got 70 SQL instances monitored at present and I've found that it's…

I spoke too soon! There are over 2000 messages in queue this morning Any ideas?

Thanks for the idea. What I'm trying to do is clear the instance of the alert that is triggered when the related incident is closed in the SD. So if the incident is marked as resolved in the SD and the underlying issue has actually not resolved, a new instance of the alert is triggered along with a new incident in SD.

It seems that my patience level was too low :-P I've solved this by waiting!

Feedback from support case: This is a known issue for core 2016.1.This will be potentially addressed in a future release.However, we're unable commit to time frame for delivery at the moment. Currently, the workaround is to delay each report schedules by 5 minutes. You may refer to the following article for more…

Here are the events:

I've managed to get this working by enabling smtp services on the local orion server and configuring relay to the smtp.office365.com smtp address. I read up on how to enable TLS and relay with IIS.

Thanks clubjuggle. I assumed that the APE would work with only TCP traffic open from the APE to the Orion server rather than bi-directional. This makes my scenario more complicated - looks like I'm going to need to investigate use of a VPN.

I've got a request open with support to investigate. Closing off this question.

After updating the server via Windows Update, patching SQL Server and rebooting several times, all seems to be in order once again