Script Probe for Restarting a Server Not Working as Expected
I have written a small batch file to restart our ConnectionServer:
SET EXE="D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\ccm.exe"
%EXE% -disable %NODE%.ConnectionServer -cms %CMS% -username %UID% -password %PWD%
%EXE% -managedforceterminate %NODE%.ConnectonServer -cms %CMS% -username %UID% -password %PWD%
%EXE% -managedstart %NODE%.ConnectionServer -cms %CMS% -username %UID% -password %PWD%
%EXE% -enable %NODE%.ConnectionServer -cms %CMS% -username %UID% -password %PWD%
The batch file works great when I run it from the server.
When I set up the batch file as a Script Probe in the Monitoring section it runs fine if the ConnectionServer is enabled and running. If the ConnectionServer is running but isn't enabled, the probe will restart the ConnectionServer but won't enable it. (It does this if I run the batch file from the server instead of as a probe). When the ConnectionServer is running but not enabled is when I need to the probe to run, kicked off by a Watch.
Does anyone have any ideas on why it would be doing this?
Also, whether the Script Probe restarts the server or not, it shows that it failed in the Probes window. I suspect that this may be because there isn't anything returned from the batch file to indicate success but I can't figure out how to configure that part. Any help with this issue would be appreciated.
This is configured in BI4.1sp5.