aLTeReGo ✭✭✭✭✭

Instead of deleting the component from the assigned application or template, you can simply disable them. This retains the configuration settings and allows you to easily revert the change if needed. Deleting is forever. Hence the ominous warning message.

Sorry about that. I didn't follow the very logic I outlined above. The example below should work as intended.

This criteria should be added to the Trigger Condition and not the alert suppression. The Alert Suppression tab was designed to address dependencies before dependencies were natively added to Orion. As written, your alert would never fire as long as any node name in Orion begins with "UPS". So it's functioning as designed,…

stephen.black is running NPM 10.5 and SAM 5.5 (based on the screenshot provided above). The Web based Report Writer was not introduced until SAM 6.0 and NPM 10.6. stephen.black, you will need to upgrade before the web based report writer will be available to you in your Orion web console.

Without looking through your diagnostics it's very difficult to definitively determine the actual root cause. The suggestions a listed above were simply the most likely/common causes. I would suggest opening a case with support so we can look through your diagnostics and figure out what the issue is.

I believe the log file it is referring to is located under "C:\ProgramData\Solarwinds\Logs\Orion\OrionWeb.log". This error typically means the database has run out of space. In most cases this is when users have hit the limit of the SQL Express database size, but can also occur when the database file has reached the size…

Does anyone know if you can use AAA to authenticate SNMPv3 on a Cisco switch/router?

The following Template(s) may be what you're looking for * Exchange 2013 Mailbox Role Services and Counters (Basic) * Exchange 2013 Mailbox Role Counters (Advanced)

Alternatively you could create a Windows Performance Counter monitor for that processes elapsed time and configure a warning or critical threshold appropriately. This value is report the amount of time in seconds the process has been running.

is correct, depending how and where you have configured these alerts. If you are using the Alert Action "Play a sound" in the Advanced Alert Manager these will only play on the Orion server, provided you have a sound card installed in your Orion server. However, you can optionally configure an "Alert Sound" on a per-user…

Almost forgot to mention.. Place the report file into the "C:\Program Files (x86)\SolarWinds\Orion\Reports" directory for it to show up in the Report Writer and in the Web interface reports section.

Bizarre, but I'm glad to hear the issue is resolved in SAM 6.0. Thank you for updating this post with the resolution.

Thanks for keeping us updated. I look forward to hearing what the cause of this turns out to be.

What I think you're seeing is the Advanced Alerting Engine will not alert you that an application is down if it can't query SNMP on the remote node. This would be the fact if the node was down, SNMP daemon is stopped, or misconfigured. I have many application alerts configured, none with suppression and I only get notified…

Macros can be used in the URLs used in the "User Links" resource to point to unique destinations based on these macros. For Example if you have a node named "AUS-ORACLE", and a sharepoint page URL of something like "http://sharepoint.mydomain.ext/inventory/AUS-ORACLE". If you followed this same convention within Sharepoint…

From what you describe it sounds as if the NOC View you were initially referencing was a subview that was removed.

msawyer wrote:Update: Solarwinds Support/Engineering Ticket still does not have a fix for this issue. The ticket has been open since July 6th, and they have been evaluating our diagnostics since that week. Support Ticket: 00137887 We're sorry to hear that you're still experiencing issues, even after applying Hotfix 3.…

mharvey wrote: There is, however, no way to have the trap change the node or hardware status. That is no longer the case in SAM 6.2, currently in beta.

This application template has been superseded by AppInsight for Exchange, which is currently available in the SAM 6.1 RC. AppInsight for Exchange is pretty much turn key. No WinRM configuration is necessary. AppInsight for Exchange does all the heavy lifting for you.

I don't believe anyone in the community has yet created an application template to monitor Maximo. I'm also unable to find a trial/evaluation download for this product.

Um, I just broke the page Now I get the follow error.. Any idea how to fix this? Orion Website Error An error has occurred with the Orion website. Additional Information System.Data.SqlClient.SqlException: Incorrect syntax near the keyword 'order'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,…

cfizz34​, can we assume you're seeing these errors in the SQL error log, or are they appearing in AppInsight for SQL? When these errors occur, is AppInsight for SQL collecting data and reporting it accurately, or is polling broken? 

Offhand the only thing I can think of would be to create a dependency between these two interfaces. E.G. Node 1, interface gi1/1 is dependent upon Node 2 gi1/1. This should cause only one interface to go into a 'Down' state. The other would go into an 'unreachable' state. Provided your alerting rules are based on 'Down'…

Are any applications monitored by that polling engine able to poll/collect data or is just this one application not working? Do any newly added assigned applications on that poller work?

SAM does not include NPM's Universal Device Poller, though in many instances you can create SAM SNMP Component Monitors instead.

I would also recommend restarting all Orion services to see if that rectifies the issue. If that doesn't resolve the issue, re-run the Configuration Wizard.

esmsolarwinds​, your explanation may be too much information that I find myself somewhat confused. Are you trying to authenticate users attempting to access the WPM web interface using their LDAP credentials, or are you describing some form of synthetic LDAP authentication monitor?

That should do it. If it does not for any reason you can use psservice.exe as an alert action, but the method you describe above is the recommended and supported way.

The simplest solution would be to require the node to be down for a sustained period of time before being alerted. That time would be greater than is reasonable for a server reboot. A more complex method would be to write a script using the Orion SDK to execute as part of the server shutdown script that unmanages the node…

You would need to stand up a new player and then assign your transactions to that newly deployed player. Once completed, delete the old player.