Symptoms

After the connection between an Agent and its Controller is lost and re-established, the Controller reconnects to the Agent, but the Agent is unable to send data back to the Controller.

More Information

This problem can occur if the network connection is broken or the Controller service or computer is restarted. When this happens, the Controller reconnects to the Agent and shows a successful connection. It is able to send commands (such as job execution commands) to the Agent, which executes the commands. However, the Agent is unable to send status updates back to the Controller, so all instances that have been sent to the Agent show status "Dispatched to Agent."

Workaround

Restarting the adTempus service on the Agent resets the connection and resolves the problem. At this time all queued status updates are sent to the Controller, which will then show the correct status for the instances.

Status

• adTempus 5
  This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.