Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Failure to restart a service via ipMonitor

Failure to restart a service via ipMonitor

Table of contents
No headers

The first thing to do is open the Service Restart Action via “Configuration -> Alert List” and click the “Force Test” button above it. If this fails, the following steps are recommended:

1. On the ipMonitor system, open a cmd prompt.

2. Type the following command:

runas /user:[domain\user] cmd.exe

***where "[domain\user]" represents the account used by the Credential assigned to the Restart Service action.

3. Enter the password when prompted.

4. Within the new CMD window, enter the following command:

sc \\[remotesys] stop [servicename]

***Where [remotesys] is the system hosting the service you wish to restart.
***Where [servicename] is the service you are attempting to control via ipMonitor.

Did the service on the remote system stop?

Last modified

Tags

Classifications

Public