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 > 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