aLTeReGo ✭✭✭✭✭

It looks as though the alert was not imported correctly during upgrade. Below is how that alert should be configured.

Have you tried using the Component Monitor Wizard and creating your own application template? My understanding is that iPlanet exposes some information via JMX, but without access to the application it's hard to know for sure.

Not to worry. We have several script gurus who lurk the Thwack forums solely looking to help people such as yourself with their custom scripts. I recommend heading over the the to post what you have, along with a description of what you're looking to accomplish. It's pretty likely someone will be both able and willing to…

We have worked jointly with Microsoft and a few customers who experienced this issue and in each case a repair of the MSSQL server resolved the issue.

XenServer support would be a feature of Virtualization Manager​, which is a separate Orion module from Server & Application Monitor​.

The escalation actions order is correct. At this point I think we've gone as far as we can in a public forum. I would recommend opening a case with support so we can troubleshoot this issue further.

I believe I answered this question in the following thread that you created. Way of configuration on SAM

You may be hitting the command line character limit limit of the operating system. I suggest copying the script to the host and calling the script from SAM's Linux/Unix script monitor to see if that works better. The below example shows this basic principle using SAM's Windows Script Monitor to execute a perl script on the…

Alternatively you can use WMI to gather this information using the same Component Monitor Wizard.

I'm not sure what exactly you are referring to. Perhaps you have created or downloaded some Universal Device Pollers from Thwack for monitoring Dell server hardware health. I would contend that if you own SAM then you have no need for these Universal Device Pollers, since server hardware health functionality is included…

Adding additional indexes to the database are not officially supported. In fact these indexes can and do on occasion cause upgrade issues, or problems when re-running the configuration wizard. I recommend that you keep careful notes on what indexes are added so they can be easily removed should you encounter similar…

SAM's VMware Performance Counter Monitor is not currently compatible with ESX v6.0 and later. This is a bug we are tracking internally under SAM-2464. It is expected to be fixed in the SAM 6.2.3 release, which should be available before month end.

Bursty disk I/O is nothing to concern yourself about but tell me what kind of drives are your DB on? SCSI, SATA, SAS? Is this is RAID? If so what's the RAID level 0,1,5? (common RAID levels) Is there any visual indication of heavy disk I/O? In other words is your hard drive light lit constantly? Windows feels like it's…

The 'Execution Mode' setting determines whether WinRM is used or if the PowerShell script should simply execute on the local machine. If the node is managed agentlessly (WMI/SNMP/etc.) then WinRM is likely needed, though it really depends on how the script was written and what the script performs. E.G. You could in some…

The Node Details, and related Summary Views are best for aggregating information specific to the node across multiple products using things like the Multiple Object Chart, etc. Summary views are best for aggregating information across multiple nodes, but can also be used for specific nodes/applications/etc using the Custom…

That is correct. Only templates have a description field. Once they're assigned to a node this field is no longer viewable or editable since it was designed to describe the application template as a whole and include pre-requisite information etc. Component monitors are where troubleshooting information should be added,…

At this point I'm at a complete loss to explain why the process monitor is showing only 4GB of memory consumed when all other data is to the contrary. The exception being the Task Manager in your screenshot above, but that is because you are showing "Memory (private working set) and not "Working set (memory)". At this…

Great! Thanks for sharing. I'm sure this will help others who may encounter similar issues in the future.

Below is an example of how to select that component as part of the alert definition Here is also an example of how to add the statistic (days remaining until the certificate expires) as a macro to your alert message

Silly question I know, but does the event log monitor change status when this event ID is seen in the Event Log? I'm trying to determine if this is a monitoring issue or an alerting issue. Both the out-of-the-box alert "Alert me when a component goes down" and "Alert me when an application goes down" should trigger when…

If the node is appearing in Orion then it sounds like the Agent was installed and registered with the AMS. Is that node listed under 'Manage Agents'? 

redlotus‌, please open a case with support for this issue and post your case number here in this thread. I will ensure your case is routed to the appropriate engineer who is working directly with Microsoft to find resolution for this issue.

jkuvlesk​ is heading up our KB migration effort. She should be able to answer that question.

Re-running the configuration wizard is really the best and only recommended way.

If the node is managed via WMI you'll need to update the node credentials under [Settings - Manage Windows Credentials]. If the node is managed via SNMP or ICMP you'll need to update the credentials you selected in the Component Monitor Wizard under [Settings - SAM Settings - Credentials Library]

For workstations or other devices that can be down for prolonged periods of time I would recommend using the Agent for monitoring. This is especially true in DHCP environments where the monitored end device IP address is prone to changes.

What message? Do you mean "HResult: The specified object is not found on the system"?

To be honest I've been more looking for an answer for what went wrong with the patch so it could be corrected in future builds, and not necessarily trying to work around the problem. Such as reinstalling Orion, or renaming all my maps. Do these solutions sound hoke to anyone else, or is it just me? I'm sure they work, but…

I edited the resource and tried selecting the map again, with the same result. In fact, none of my maps work. All my maps are listed but It doesn't matter what map I select, none of them work. I've opened my maps in map maker and they open up just fine. Any other suggestions?

KB is now located here > https://support.solarwinds.com/SuccessCenter/s/article/Create-a-Group-of-Nodes-alert-using-a-Custom-property-to-Identify-Group-name-and-Group-Member-Name-With-Variables