Issue
Automation Server stuck in Reboot Cycle
Environment
Automation Server
Cause
This experience is not typical so below is a list of solutions that have worked in the past.
Resolution
ES - AS Communication Issue -
This fix works when the boot cycle only occurs while the ES is online. You can prove this is the case by stopping the Enterprise Server through software administrator, then attempting to log into the AS
- Log into the Enterprise Server
- Click on the Root Server Object in the System Tree Pane
- Click on the Communications tab
- Verify that the listed IP address for the Enterprise Server matches the IP address of the machine
- In the System Tree Pane, expand the Servers folder
- Delete the Affected Automation Server. NOTE: This will break all binds to/from this server.
- Log out of the Enterprise Server and Log into the Automation Server to verify that it is stable.
- Log out of the Automation Server and back into the Enterprise Server
- Re-add the Automation Server to the Enterprise Server