Hi David,
I believe the issue you are experiencing is due to FusionReactor
running “sc” with insufficient privileges on the remote machine.
There are many different domain controller configurations and group
policy options that can effect the successful completion of the “sc”
command. Whilst I find it intriguing that you can run the command
manually from your monitoring box against the \\web1a machine, without
entering into a consulting engagement and spending time thoroughly
investigating I would recommend the work-around laid out below.
There is a FREE tool from Microsoft called PsService (
http://technet.microsoft.com/en-us/sysinternals/bb897542.aspx ). The
tool allows you specify the credentials to use for the remote service
restart, thus ensuring appropriate privileges are available to perform
the restart.
We are able to offer an installation, configuration and testing
service for this tool for which a 4-hour support block would cover.
I hope this information helps resolve your problem.
Additionally, may I point you at our CF consultancy services pages of
our site (
http://www.fusion-reactor.com/services/cfservices.cfm ). Our
experts can help you resolve the root cause of your issue and prevent
the need for the service restart in the first instance. This obviously
leads to a more stable and better performing platform.
Best regards,
David Stockton
Intergral (UK) Ltd - The makers of FusionReactor