aLTeReGo ✭✭✭✭✭

What version of Exchange are you monitoring and how many MAPI User Experience Monitors do you have configured in SAM? If there are more than one, are any of them working?

This issue is addressed in SAM 6.2 which is available for download through the customer portal for all SAM customers under active maintenance.

I have conferred with support that this should work without issue. What you are seeing is mostly commonly caused by one of two reasons. a) Domain name may have been improperly typed. You can verify proper domain name in ControlPanel -> System and Security -> System (Unlikely, but still the most often cause) b) Inproperly…

If all the information you need is available via SNMP, that would be the prefered method. Otherwise you would need to utilize the template referenced above and modify it to suite the server being monitored by specifying the specific volumes you'd like monitored. 

I recommend opening a case with support so we can look through your log files to determine the cause of the issue.

Agreed. This is just a standard NET-SNMP MIB walk here. No vendor specific OIDs appear anywhere in the MIB walk. Configuration of SNMP on this device appears relatively straightforward, so it seems unlikely to be a configuration issue. Can you verify you're using SNMP v2 and not v3 just to eliminate view limitations as the…

Then the only likely remaining permission is the SAM Admin role pictured below under "Server & Application Monitor Settings" editable under each users account settings.

I changed the Process to svchost since I'm not running "harmony_server" on my Orion server. The script however appears to work without issue running SAM 6.2.3.

What type of device is this occurring on?

'Unreachable' is a substitute status only for 'down'. If the parent is 'Down' but the children are still up and polling correctly, their true/real status will be reflected.

fcpsolaradmin Can you please open a case with support? This issue is being tracked internally under FB408488 and the parent for the case bravo opened. Please reference this number and this thread when opening your case to ensure it's routed appropriately. 

ikomrad​, the 'test' button simply validates the credentials provided. It cannot verify the permissions without actually trying to deploy the agent itself. If you're having intermittent success deploying the agent I wonder if you might be deploying the agent over a WAN connection that may be timing out. The 'push' process…

The VolumeType sting in the field is indeed inconsistent. I'm not familiar enough to know where the discrepancy is coming from but NetworkDisk is the same as FixedDisk. There's no difference. This same defect can also be found for Fixed Disks as well. I've logged this as a bug internally under FB401365. In the meantime you…

Can you provide a link to the specific template you're trying to download from the Thwack Content Sharing Zone?

That is very likely the case. I would recommend opening a case with support. There are likely other side effects of this you may not yet have noticed, such as "Poll Now" or "Test" buttons not working as expected for nodes managed by this polling engine.

Alerts don't need to be setup for each application you create or assign to a node. It's all dependent on how the alert is written. For instance if you use the out of the box alerts "Alert me when an application goes down" or "Alert me when an application goes into warning or critical state" these apply to any and all…

Are you using AppInsight for SQL? SAM supports the use of Named Pipes and your connection string should not differ for TCP/IP vs Named Pipes. This is handled by the operating system and the SQL driver.

Bitness only relates to the cmdlets being called within the script. When the script is run outside of SAM what is the format of the output? Can you post a screenshot?

, I will leave you with the following sneak peak to taunt give you a better idea of what this looks like in SAM 6.0.

The Count Statistic as Difference option for the SNMP Component monitor is currently being tracked as a feature request internally under FB104440.

Based on the screenshot provided it appears you're attempting to use the MSSQL driver to connect to your MySQL database. You need to specify the correct MySQL driver to connect to a MySQL database. In the case of the driver you have installed I believe the following ODBC connection string is what's needed. Also, if you…

jamesun, could you please open a case with support for this issue so we can track and follow-up appropriately? We would like to verify if the issue you are encountering is the same as the one we hope to include in RC3, or if this is a new as-yet-unknown issue.

John Spanitz, you should have received an email from me Monday 2/17 at 1:10PM entitled "SolarWinds Server & Application Monitor 6.1 RC2" with links to download RC2. If you did not, please reply to the original email you received requesting links to download SAM 6.1 RC2.

Can you specify which version of Exchange you're attempting to monitor, as well as what version of Windows Exchange is running on? Lastly, please gather the “RunWinRMConfigurator.log” file located under “C:\ProgramData\Solarwinds\Logs\APM\” on the Exchange server itself, and email that to me by replying to the RC invite…

Can I assume you created your own custom application template named "POA MySQL Server"? Is the alert showing up as triggered in the "Active Alerts" resource, or listed in the Triggered Alerts section of the Advanced Alert Manager? I'm trying to determine if this an issue with the alert condition not triggering or a problem…

I took the liberty of posting this as a file in the Content Exchange to make it easier for others to download from Thwack and import into Orion. It can be found here > Response Time vs Packet Loss Last 30 Days

It's very possible to assign the same application template to the same node configured to use different settings. This is the recommended method for monitoring database servers with multiple instances/DPN/etc.

Negative. This means that the escalation process will continue unabated UNLESS the alert is acknowledged. This is a great way to break the normal automated escalation process from occurring if needed.

This should only effect your primary Orion server. No changes to the Additional Pollers should be necessary.

Is the error you're receiving persistent for these nodes or does this only occur occasionally?