aLTeReGo ✭✭✭✭✭

This could theoretically work using a PowerShell script monitor using the component message attribute in the Advanced Alert Manager as the value returned by the script which returns the string "Manual" or "Automatic". The Disabled state is obviously not applicable. The statistic returned would then be used to represent the…

When using AppInsight for IIS or AppInsight for Exchange you may see higher than normal memory consumption in the 64bit job engine worker on the agent. This is really no different than what you would see agentlessly for PowerShell processes on the remote host, but on the agent these PowerShell processes all run under the…

The registry key you reference above is not related to the agent. It's native to the Windows operating system and is related to Performance Counters. https://support.microsoft.com/en-us/kb/300956

Absolutely. The following templates are optionally available for monitoring MSSQL servers for anyone who does not wish to use AppInsight for SQL. * SQL Server 2005-2008 Performance (WMI) * SQL Server 2005-2008 Performance (SQL) * SQL Server 2012 Performance (WMI) * SQL Server 2012 Performance (SQL)

Excellent point hilbertd21‌! This is also covered in the following KB article. * SolarWinds Knowledge Base :: AppInsight for SQL: CPU usage at 100%

You could execute an external script as part of an alert action when this component is in a warning or critical state that deletes these files automatically.

Yes. That component is returning the number of "TMP" files in your temporary directory. Unfortunately the template can not be updated because SAM's File Count monitor does not currently support partial name filtering, despite what the component monitor settings may appear to show. This is not so much a bug, as it’s a…

Have you tried configuring your alert in the following manner?

You'll need to upgrade to APM 4.x to leverage grouping and dependencies. The current release is APM 4.2.

Yes. APM 4.2 includes the updated MSSQL application template.

Implicit dependencies are automatically defined by the Orion system. These occur for example when you assign an application to a node. Explicit dependencies are ones that are created manually through dependency management [Settings - Manage Dependencies]

As Petr.Vilem‌ eluded to above, this issue is addressed in SAM 6.2 which is available for download through the customer portal for all SAM customers under active maintenance.

This is a known limitation of the Advanced Alert Manager. These disabled components triggered an alert at the time they were disabled, so their state has not cleared from the Advanced Alert Manager. I recommend temporarily disabling the alert that is showing this disabled component in a failed state, letting the Alert…

This is covered in the Administrators Guide here -> http://www.solarwinds.com/NetPerfMon/SolarWinds/OrionAPMPHComponentTypesLinuxScript.htm You can see this option in the component monitor settings pictured below.

Can you map a drive to the administrative share on this machine from the Orion server? E.G. \\servername\C$ using the credentials you are attempting to use for monitoring? Have you verified that you are using the local administrator credentials for monitoring this host? Is there a firewall or any router access control…

It looks like you're running an earlier version of SAM/APM. The current release version is v5.5. In the version you are running the same functionality exists. It's just called "Browse for Component Monitor".

There is a known issue with SAM 6.6 causing this message to appear improperly when Application Dependency Mapping (ADM) is enabled. To resolve the issue, I suggest disabling ADM. If that's not an acceptable workaround, please contact support. 

Note that this should not be necessary when using a Windows account with Windows Authentication. It is only required when using local SQL accounts with SQL authentication. 

If you've modified the default alerts and need to get them back to their default state, simply delete them and re-run the Configuration Wizard. This will restore any default out-of-the-box alerts to their original state.

mandevil wrote: Does anyone know what features the %_cur% tables support? Was thinking this may be a part of real-time polling in PerfStack, but not sure. Have a situation where a number of tables are growing large that are memory optimized causing less and less memory for normal buffer cache. Especially seeing…

cmblackburn, did your DBA somehow disable the ability to create memory optimized tables on SQL? If so, can you share how this was done so we can better detect this scenario? Currently, we're simply checking the version/edition of SQL and utilizing features available in those versions. If there is a way in which those…

From only the description you've provided so far it sounds as though there is a large number of orphaned jobs. Please follow the steps outlined below. This will clear out any orphaned jobs. * Stop the "SolarWinds Job Engine v2" Windows service * Go to "C:\ProgramData\SolarWinds\Installers" * Run JobEngine.v2.msi and,…

Hardware health monitoring for network devices (not servers) is a function of the recent NPM 10.4.release. I will move this post to the appropriate forum where it will receive better visibility from those most able to assist with this issue.

Honestly with that many nodes I wouldn't consider using VMWare. That's just me. I've run Orion with SL-100 and SL-500 under VMWare and it worked pretty well, but SL-2000 (2000 or more elements) VMWare just didn't perform well. People were always complaining about the performance of the web interface. We now run on…

Custom Properties can be used as view limitations by using the Custom Limitation Builder utility on the Orion server itself.

What version of SAM are you running?

Note that Thin APs are not nodes in Orion. Therefore things like Mute and Unmanage do not apply to them.

I recommend opening a case with support so we can properly track this issue. Please reference this thread when opening your case. We will make every effort to troubleshoot and diagnose the issue, but it is determined to be isolated to a particular server it may require assistance from Microsoft support to resolve.

Based on the following KB articles, it sounds like you might either be running your Orion database on a version of SQL older than 2005, or Named Pipes are not enabled. * SolarWinds Knowledge Base :: Error "Named Pipes Provider, error: 40 - Could not open a connection to SQL Server" occurs * SolarWinds Knowledge Base :: I'm…

Ahh, I forgot to calculate for DST. This is normal behavior for SAM. The server clock can be set to the correct timezone, but all data in the SAM database is stored in UTC.