Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Windows
Description
Current Situation
- If you stop the Windows service of a Universal Agent then the service calls the instance script with the stop command.
.\bin\jobscheduler_agent_4445.cmd stop
- This call works properly in a command prompt but not always by the service because the service calls it non-interactively. As a result the Windows service panel might show the Agent status "stopping" and does not allow to restart the Agent.
Desired Behavior
- The Universal Agent should stop always if its Windows service is stopped.
Workaround
- Use the command line interface to stop the Agent
- jobscheduler_agent.cmd stop stops a running Agent
- jobscheduler_agent.cmd kill kills a running Agent