Summary

This article describes the changes included in the maintenance update for adTempus 3.0 released on November 22, 2009.

Version Information

After you install this update, the About box in the adTempus Console will show a Product Version of 3.0.7. If your Product Version is already 3.0.7 or later, you do not need to install this update.

Installation Notes

This update is a cumulative update, and contains all fixes released in previous maintenance updates. It is not necessary to install previous maintenance updates before installing this update.

This update may install a new version of the adTempus Update Center. If the update is installed from the Update Center, the setup program will prompt you to close the Update Center to continue. This must be done by terminating the Update Center using the Windows Task Manager.

Obtaining the Update

The latest Maintenance Update can be installed through the adTempus Update Center by selecting "Check for Updates" from the Help menu in the adTempus Console or in the adTempus program group in the Windows Start menu. It can also be downloaded here.

Changes in This Update

The following new changes are included in this update. In addition, this update includes all changes from previous updates. See article K00000333 for information on those changes.

General
Recovery from job status data lossCR00000651
Defect

In rare circumstances the database record that stores a job's status information may be lost due to a program problem. In previous releases, once this happened, the job was no longer accessible through the Console. With this update, adTempus will recreate the missing status record, preventing errors in the Console.

Conditions
adTempus now logs status message during condition waitCR00000662
Enhancement

If a job or step is in status "Waiting for Condition" and the job or step has more than one condition, adTempus will periodically log an informational message to the job log indicating which conditions have and have not been satisfied. This information can be used to determine which conditions are preventing a job from running.

If the job or step has only one condition, no message is logged as it is not needed.

After waiting for condition, adTempus may encounter database errors; Console may freezeCR00000637
Defect

If a condition is satisfied after adTempus has been waiting for the condition, either or both of the problems may occur:

  • adTempus may fail to open a database connection, then retry repeatedly to open the connection. As a result, the job does not continue executing until about 20 minutes later.
  • The Console may freeze (stop responding).

This problem occurs primarily if the job is running under a non-Administrator user account. It is caused by adTempus attempting to connect to the database under the wrong security context, resulting in a database logon failure.

The problem was resolved.

Database
Database changes to improve Console performanceCR00000682
Enhancement

New indexes have been added to the adTempus database to speed access to the tables used to store job history. Customers with a large amount of history data should see a slight improvement in Console responsiveness as a result.

Job Execution
When adTempus instance sends a job execution command to remote server, the command may not be executed correctlyCR00000680
Defect

This problem may result in several different incorrect behaviors, including:

  • The job may not be executed, with no warning or error reported.
  • The job may be executed on the wrong Agent.
  • The job may get stuck in the "Waiting for Agent" status on the Master

This problem was corrected.

If a step is disabled, subsequent steps do not runCR00000683
Defect

If a step within a job is disabled, subsequent steps in the job did not get executed, even though they were not disabled.

This problem was corrected.

Pattern matching for file conditions and captures doesn't work if filespec has parenthesesCR00000685
Defect

If a File Capture action or a File Trigger use file specifications that include parentheses, adTempus will fail to match files based on those specifications.

This problem was fixed.

Job Control Action may not successfully start a job located on another serverCR00000688
Defect

If a Job Control Action targets a job on another server, the job may not be started when the action executes. The same problem occurs if a job running on an Agent tries to start another job that is controlled by the same Master.

This problem was fixed.

Notification
Notification messages do not handle .mht attachments properlyCR00000674
Defect

If a notification message includes an attachment with file type .mht, the attachment is not delivered properly.

This problem was resolved.

Scheduling
Chained rule-based scheduling scenarios may not work in some casesCR00000669
Defect

When you create a schedule criterion to select days based on a rule that is relative to another criterion, the schedule may not execute.

This problem was resolved.

"Any Business Day" setting triggers on all daysCR00000678
Defect
If a job is configured to execute on "Any Business Day," it runs on all days, not just business days.Conversely, a job configured to run on "Non Business Days" will never execute.
Security
Creating user may not receive permission to use new Credential ProfileCR00000645
Defect

When a user creates a new Credential Profile for use on a job, adTempus may fail to grant the user permission to use the Credential Profile, resulting in an error when the user tries to use it.

This problem was resolved

Triggers
adTempus fails when including or excluding events for Event Log triggerCR00000636
Defect

This problem was resolved.

For more information see Knowledge Base article K00000335.

File Trigger
File Trigger may not use new values if Job Variable is modifiedCR00000668
Defect

If a File Trigger uses a Job Variable in its file specification and the value for that Variable is set above the job level (i.e., at the Queue, Group, or Server level), the change is not "seen" by the trigger unless the job is modified and saved or the adTempus service is restarted.

This problem was corrected.

User Interface
Console
Holding or Releasing a job through Console context menu does not workCR00000650
Defect

For more information see Knowledge Base article K00000347.

Unhandled exception error if user tries to run a job but has no permission on queueCR00000675
Defect

This problem was resolved.

For more information see Knowledge Base article K00000355.