adTempus logs an Alert and reports a message in the Application log in the Windows Event Viewer indicating that a database error has occurred:
Additionally, you may find that the Agent is not reflecting configuration updates made on the Master, and may not execute jobs sent by Slave or Load Balance queues.
This problem occurs if all of the following are true:
When the Agent receives the new Job Group from the Master, it treats the group as a different object than the existing group with the same name. This is because adTempus identifies objects using an internal unique identifier, not the name. Even though the groups have the same name, they have different identifiers, and therefore are treated as different objects.
The Agent therefore tries to save the Job Group as a new object, and this results in a database error because of a constraint that prevents two groups from having the same name.
To determine the name of the group that is causing the problem, review the "adtempus.service.log" diagnostic log file (see article K00000417 for information on how to locate this file). In the log file you will find the error message shown above, preceded by information similar to the following:
The line shown in bold above (beginning with "Parameter: @p8") gives the name of the Job Group causing the problem: in this case, "TEST".
On either the Master or the Agent, edit the Job Group with this name and change the name to something unique. Once the group has been successfully replicated from the Master to the Agent, you can move jobs from the group on the Agent into the group sent from the Master, if desired.
Arcana Development is currently investigating this issue.