Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Problem in Alert action: Execute External Program - .JAR script

Problem in Alert action: Execute External Program - .JAR script

Table of contents
Created by Alexander Aguilar, last modified by MindTouch on Jun 23, 2016

Views: 961 Votes: 0 Revisions: 8


This article addresses the issue where the .jar script does not run from the Orion Alert Action.


NPM 11 and later


Note: SolarWinds does not support troubleshooting of the .jar script functionality in NPM. The following steps describe how to test the functionality to execute a script on Orion without troubleshooting the script.

  1. Create two .cmd scripts. For example:
    • net stop Spooler​
    • net start Spooler
  2. Save the scripts (NStop.cmd and NStart.cmd) to a shared location in the main Orion server.
  3. Create the alert.
  4. On the Trigger Actions tab, click Add Action.
  5. Select to Execute an External Program and click Configure Actions.
  6. Assign a name.
  7. In the Network path to external program field, put \\<servername or IP>\<share name>\NStop.cmd
  8. Add another action.
  9. Select to Execute an External program and click Configure Actions.
  10. Assign a name.
  11. In the network path to external program field, put \\<servername or IP>\<share name>\NStart.cmd
  12. Simulate the action and check if the printer spooler stops and starts when you execute the action. 


Additional Resources:


Last modified