Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Troubleshoot the External Process Monitor

Troubleshoot the External Process Monitor

Table of contents
No headers

This Monitor 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 Monitor, 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.
-[Command Line Parameters]: These are the parameters to be passed to the executable. If you want to run a vbscript, you will put the script file name and parameters to be passed to it.
-[Startup Directory]: This is the directory where you wish to run the executable from.
-[Credential for Monitoring]: This is the Credential which points to the Windows Account you wish to use in order to trigger this executable.

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 Monitoring] cmd.exe

3. Enter the password when prompted.

This will run a CMD window which will run 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 command:

[Directory][Executable Name] [Command Line Parameters]

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

If this command fails, so will ipMonitor. The error returned by the command should indicate where the issue truly lies.

A few additional things to verify:

  • Ensure that the Windows Account assigned to the ipMonitorSrv service is allowed to impersonate the Windows Account assigned to the Credential being used by the Monitor. The LocalSystem account normally has everything needed to accomplish this. Naturally, if the ipMonitorSrv service is running as a domain admin account, the Monitor should not be given a Credential.
  • Ensure that the Credential being used only has the following Usage Restrictions selected:
    • May be used with Windows Impersonation for use with RPC
    • May be used with Windows Impersonation to start an external process


IMPORTANT: If calling anything from c:\windows\system32\ directory on a Windows 64-bit OS, make sure the files also exist in c:\windows\sysWOW64\ as all calls to c:\windows\system32\ by 32-bit applications such as ipMonitor are redirected to c:\windows\sysWOW64\.

Last modified