Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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: 980 Votes: 0 Revisions: 8

Overview

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

Environment

NPM 11 and later

Steps

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

Tags

Classifications

Public