Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > ipMonitor > Troubleshoot the External Process Action

Troubleshoot the External Process Action

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 27 Votes: 0 Revisions: 7

This Alert can sometimes return errors which are misleading. The most common one is ???Access rights are insufficient???. This article will explain how to troubleshoot issues with the External Process Alert, but first let's describe the fields:

[Executable Name]: This is the name of the executable you wish to run. If you want to run a visual basic script, you will need to first start cscript.exe from here.
[Directory]: This is the location where the executable is located. This path must be local to the ipMonitor host.
[Startup Directory]: This is the directory where you wish to run the executable from.
[Credential for Action]: This is the Credential which points to the Windows Account you wish to use in order to trigger this executable.
[Failure Command Line]: This field is used to supply the executable with specific parameters to use in the event of a detected failure.
[Recovery Command Line]: This field is used to supply the executable with specific parameters to use in the event of a detected recovery.

In order to test these values within a CMD prompt, you first want to make sure to run it as the same account ipMonitor is using. Here???s how:

1. On the ipMonitor system, open a CMD prompt.
2. Type the following command and press Enter:

Runas /user:[Credential for Action] cmd.exe

3. Enter the password when prompted.

This will run a CMD window which is running under the same Windows account used by the Credential assigned to the Monitor.

4. Within the new CMD window, change to the path specified within [Startup Directory]

5. From here, run the following commands:

-To test the failure parameters:

[Directory][Executable Name] [Failure Command Line]

Example: c:\windows\system32\cscript.exe restart_IIS_pool.vbs websrv1

-To test the recovery parameters:

[Directory][Executable Name] [Failure Command Line]

Example: c:\windows\system32\cscript.exe recover_ticket.vbs

If these commands fail, ipMonitor will also fail. The error returned by the command should indicate where the issue truly lies.
 

Last modified
19:37, 22 Jun 2016

Tags

Classifications

Public