When a job or step has more than one Condition, and the job or step is not executed because a condition is not met, adTempus now writes a message to the job log indicating which conditions were met and which were not.

In some cases, the adTempus service may fail to start during computer boot-up, reporting that the database is not available. If you subsequently start the service manually, it starts without any problems.

This problem occurred because adTempus tried to connect to the database before the database server had completed initialization. It has been fixed so that adTempus will wait for the database server to finish initializing.

When a job or step has more than one Condition, and the job or step is not executed because a condition is not met, adTempus now writes a message to the job log indicating which conditions were met and which were not.

adTempus performs a daily backup when adTempus is using the SQL Server Express database. However, if the adTempus database name has a hyphen in it (which occurs if the name of the computer on which adTempus is running has a hyphen), the backup was not performed. This problem was corrected.

In some cases, the adTempus service may fail to start during computer boot-up, reporting that the database is not available. If you subsequently start the service manually, it starts without any problems.

This problem occurred because adTempus tried to connect to the database before the database server had completed initialization. It has been fixed so that adTempus will wait for the database server to finish initializing.

Previously, adTempus created a daily backup for the adTempus database only when adTempus was using the MSDE or SQL Server Express database. In some cases adTempus failed to recognize that a SQL Server Express database was in use and backups were not performed.

adTempus will now create a daily backup when adTempus uses a local SQL Server instance, regardless of which database edition is being used (MSDE, SQL Server Express, or a full standalone instance).

adTempus does not perform backups for remote database servers.

The adTempus data export and import tools now provide visible progress indicators during export and import operations. Previously there was no indicator other than a wait cursor (hourglass), which made it difficult to determine whether the operation was proceeding.

In the Export tool, the option to export data to another adTempus server was always disabled. The window has been fixed so that the option is available.

When you attempt to edit an imported job from the "Import Results" page of the Import Wizard, the Queue selector of the job window may be empty (no Queues listed). As a result, the job cannot be saved because no Queue is selected. This issue has been fixed.

When adTempus runs an "external" script (a script not stored in adTempus), in some cases scripts aborted with a timeout message even if you have specified that the script should not have a timeout. This issue was corrected.

For more information see Knowledge Base article K00000319.

In rare cases, an internal resource deadlock caused adTempus to stop executing jobs and responding to the adTempus Console. This problem was resolved.

For more information see Knowledge Base article K00000320.

In some situations the adTempus service failed (crashed) while communicating with the adTempus Console. The exact  conditions that lead to the failure are not known. This issue has been resolved.

In some cases the adTempus service failed (crashed) while calculating the execution schedule for a job. The problem generally occurred when a job was modified, or in some cases when the system clock on the computer was changed.

This issue has been corrected.

When you use date criteria in the Job History and Message Log queries in the adTempus Console, adTempus performs the query using the wrong time zone. This may cause the queries to miss some records that should be included, or include some records that should be excluded.

This issue has been corrected.