Job Scheduling and System Automation
adTempus 5 Known Issues
This page is for adTempus 5 only. For adTempus 4, see adTempus 4 known issues.
Open Issues
The following Knowledge Base articles describe known issues in the current release of the software. See the Release Notes for information on recently-fixed problems.
| Issue | Status |
|---|---|
| K00000645: Cannot create a Remote Agent without specifying the "Optional Name" | Hotfix Available |
| K00000644: Setup fails to recognize valid license | Open |
| K00000643: PowerShell scripts unable to load some modules | Hotfix Available |
Available Fixes
The following issues have been resolved in a hotfix update but have not yet been included in a general release. If you are affected by one of these problems, see the hotfix page to obtain the hotfix.
Version 5.1.1.10
Email trigger does not set EmailProcessing.MessageLocation variable when message body is not present
When an email trigger is configured to save the body and attachment separately and the message does not contain an HTML or plain-text body part, adTempus properly saves the attachments but fails to set the EmailProcessing.MessageLocation Job Variable with the location of the saved attachments.
Version 5.1.1.5
Cannot create a Remote Agent without specifying the "Optional Name"
For more information see article K00000645.
Version 5.1.0.300
Database upgrade from 4.x may fail when removing non-existent constraints
When upgrading to adTempus 5 from adTempus 4, the database upgrade script may fail when trying to drop a database constraint that is not present in the database. This can happen if the adTempus database has previously been through upgrades from version 3, or if the constraints have been removed for some reason. The database upgrade scripts were modified to ignore missing constraints.
Setup does not recognize agent-only license when upgrading
When upgrading an agent-only instance of adTempus, setup does not recognize the agent-only license that is present on the computer and reports that no license was found. This problem was corrected so the license is detected.
Version 5.1.0.297
Custom ("Other") connection type does not work correctly for Database Operation Task
If the connection type for a Database Operation Task is set to "Other" (using a custom OLEDB connection string), the connection test fails with error ADT005320E: Unrecognized database type "unspecified", and the task will fail if the job is executed.
Version 5.1.0.296
Hidden job variables can be revealed in Job Detail Log and diagnostic logs
When hidden Job Variables are used as part of the command line for a Program Execution Task, the variable values are logged to the Job Detail Log and in adTempus server diagnostic logs. The software was changed to conceal the values in these places.
Version 5.1.0.291
Some modules not found when running PowerShell script after update to 5.1
PowerShell scripts may fail because some external modules cannot be loaded.
For more information see article K00000643.
