What is the best method to restart a stopped Windows service?

I've been trying to use the APMServiceControl.exe but no luck!!!!

It does not work with the AM # and the example for COMPONENT TYPE uses a number, but the extract from the component data uses a name.

Is there anything that will restart a Windows Service after it has stopped?

Find more posts tagged with

Accepted answers

lchance

Thank-you Roger! I started out by using Component Name is equal ...

But after all of this, it appears it just needs the full path name to APMSERVICECONTROL in order to work, for whatever reason.

So, here is what works for me!

C:\Program Files\Solarwinds\Orion\APM\APMServiceControl.exe ${ComponentId}

Thanks again!!!

All comments

JasonFerree

It will need a component ID when configuring the trigger action. It should not go by component type or application number.

Here is the page from the admin guide that should help you configure the action.

www.solarwinds.com/.../OrionAPMAGRestartingWindowsServicesWithAlertAction.htm

lchance

Still no luck!

Does this require the parameter, like, -c=START ?

And is this supposed to work, APMServiceControl.exe 2654 (When the AM# is 2654)

If using the canned alert named RESTART A SERVICE, and the AM# is 2654, would I put that number on the Component Type ?

If so, I tried that and it still did not work.

I may need to open a support ticket...

MarieB

Hi Larry--

When you open a support ticket, could you:

--Reference this thread to Support.
--Post back here with a case number.
--Post any solutions you get from Support.

Many thx,

lchance

Hey Marie!

Here's the case Case #242684 - "Can't restart a service" and I've also referenced this thread. THANKS!

RogerWong

Hmmm. So, all that you ought to need to do is enable the Restart a service canned alert. It's not supposed to need any modification to work properly and automatically -- the alert, as configured, does this: "If a component is down, and that component is a Windows service monitor, execute the utility on the command line that will restart the service the component was monitoring"

But... hmmm.

We *might* have a bug. I'm looking at the "Trigger Actions" for that alert, and the command line run is:

C:\Program Files\Solarwinds\Orion\APM\APMServiceControl.exe ${ComponentId}

But, I think it's supposed to be:

C:\Program Files\Solarwinds\Orion\APM\APMServiceControl.exe ${ComponentId} -c=START

I think if you edit the Execute Program alert trigger to that, it will solve this problem for you.

JasonFerree

-c=START is actually the default action if none is specified. It shouldn't have to be added, but won't hurt either.

Probably the first thing we will do is take a look at the log file to see what is going on. We can investigate via the support ticket and report our findings to thwack.

lchance

Roger,

What exactly is Component Type 9? Is this when using SNMP? What if I'm using 'Windows Service Monitor' instead?

And when using this with default Type 9, it appears to restart other services that were stopped (monitored by APM).

I just triggered a test on this and your recommendation worked, but it also caused a second service on a totally different server to restart. I suspect that service is a different component number (AM#) but yet under the same Component Type (9) within the alert.

Would it or should it work if I don't use ${ComponentId} but instead used the real number for my component?

Thanks.