Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Restarting Windows Services with an Alert Action

There is predefined alert called "Restart a service" for restarting Windows service with

APMServiceControl.exe

I tried to test it on remote (not Orion running) server but it doesn't work. I mean it did not restart stopped service. Does it work only on Orion server or APM monitor should be different than Windows Service monitor?

My installation is:

SolarWinds Orion Core 2011.1.1, APM 4.0.2 SP4, NPM 10.1.3, NTA 3.7, IVIM 1.1.2

Find more posts tagged with

apm_4.0.2

Accepted answers

martin.susil

Hello,

actually 'Component Name' doesn't have impact on APMServiceControl. But you are correct that 'Net Service Name' (in monitor settings) needs to be 'Service Name' (as displayed in Service properties).

In APM 4.2, this was changed so APMServiceControl also works with service display name - like PsService does.

All comments

Bronx

The following article should answer your questions: (Option 2 in the article may be what you're after).

http://knowledgebase.solarwinds.com/kb/questions/2699/Configuring+a+group+level+alert+to+trigger+the+restart+of+a+service.

:-)

JaroslawLadyga

Unfortunately both solutions do not work.

APMServiceControl works at localhost only. Itdepends on APMServiceControl.exe.config but practically I didn't see option to use dynamic destination server and services.

PsService is better but it works only if I start it up from CommandPrompt window but not from Trigger Action tab at alert definition.

Any more ideas?

aLTeReGo

APMServiceControl should use the same credentials used to monitor the service to restart it so you shouldn't have any issues using it on remote machines with either local or domain credentials. You may need to specify the machine name or domain in the username when assigning credentials to the template for APMServiceControl, but it should work. E.G. "MACHINENAME\username" or "DOMAIN\username".

If you're going to use PsService you'll need to change the user account that the "SolarWinds Alerting Engine" Windows service runs under (right click on "SolarWinds Alerting Engine" -> "Log On" Tab -> "This account" -> enter the username/password of the account that runs PsService command properly -> click "ok" -> Restart the "SolarWinds Alerting Engine") and try again.

JaroslawLadyga

Thanks for advices but still no progress. When tried to run APMservicecontrol.exe from Command Prompt then I got:

...\Program Files\SolarWinds\Orion\APM>apmservicecontrol 6042 -c=START
SolarWinds APM Service Control

Connecting to localhost:17777

...\Program Files\SolarWinds\Orion\APM>

When it runs from alert action then nothing happens.

I set up alert with trigger action type: "Execute an external program" and the program is: ...\Program Files\SolarWinds\Orion\APM\APMServiceControl.exe ${ComponentID} -c=START

Credentials used in APM monitor are efficient on all servers ("DOMAIN\username")

The same final result I get with PsService. It works properly from Command Prompt but do nothing when in alert action. I use batch file to run as external program with2 lines :

@echo off

...\Program Files\SolarWinds\Orion\APM\PsService.exe \\server -u DOMAIN\username -p password START "service name"

I mean the same batch file runs ok while executed from Command Prompt. SolarWinds Alerting Engine uses the same credentials as in the file. I have the same level of access when running batch file from Command Prompt. Maybe it is something related to Win Server 2008? I do not understand that.