Article ID: K00000333
Last Updated: January 28, 2009
Summary
This article describes the changes included in the maintenance update for adTempus 3.0 released on January 28, 2009.
Version Information
After you install this update, the About box in the adTempus Console will show a Product Version of 3.0.6. If your Product Version is already 3.0.6 or later, you do not need to install this update.
Important Changes
This update corrects a significant issue with the adTempus client security framework (see article K00000334). As a result, after this update some non-Admin users may not be able to perform actions that they were previously able to perform, due to security misconfiguration. Please review article K00000334 regarding these potential issues.
Due to the nature of the changes made in this update, you must update both the adTempus Client (Console) and Server (adTempus service) if non-Admin users use the adTempus Console. Once this update is applied to an adTempus server, that server will no longer accept connections from non-Admin users who are using an older version of the client software.
If all of your adTempus users are members of the Administrators group on the adTempus server, it is not necessary that their clients be updated at the same time, but it is still recommended.
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 K00000326 for information on those changes.
| Database |
| | Some database operations fail for non-English installations of SQL Server | CR00000635
Defect | When adTempus is used with a SQL Server instance that uses a language other than English, some adTempus database queries and updates may fail due to a problem with the formatting of date values that adTempus sends to the database. As a result of this, the following problems may occur:
- The Message Log Query and Execution History Query may fail to return records, or may produce an error message when run.
- adTempus may fail to purge old job history data from the database.
This problem has been resolved. |
|
| Distributed Scheduling |
| | Agents may hang while waiting for a response from the Master | CR00000630
Defect | |
In some cases adTempus Agents may "hang" for anywhere from a few seconds to many minutes while waiting for the Master to respond to a communication message. During such a hang, the Agent stops executing jobs.
This problem was resolved. |
|
| Import/Export |
| | Job export does not include passwords or history | CR00000625
Defect | |
Due to a problem introduced in version 3.0.5, adTempus ignores the options in the Export dialog box that allow you to include passwords when exporting credentials and to export the job history. Checking these boxes did not cause these items to be included in the export. This issue was resolved. |
|
| Job Execution |
| | Job Control Action to restart job doesn't work unless force new instance option is specified | CR00000615
Defect | If you use a Job Control Action to restart the current job, and the job is configured to not allow multiple instances, the job will not be restarted unless you have checked the "Force a new instance of the job if necessary" option in the response.
adTempus has been changed so that the job will be restarted even if this option is not checked. |
| adTempus stops functioning because it cannot create more worker threads | CR00000620
Defect | |
Due to a problem, adTempus in some cases fails to destroy worker threads when they have finished working. It is possible for this to lead to an exhaustion of system resources that prevents adTempus from creating additional worker threads, leaving it unable to execute jobs and perform other tasks. Typically this situation will only arise if the adTempus service has executed many thousands of job instances since it was last restarted, or if it is rejecting a large number of invalid connection attempts from remote clients or other servers.
This issue was resolved. |
|
| Security |
| | adTempus Console fails to enforce security for non-Admin users | CR00000626
Defect | |
This problem was resolved. For more information see Knowledge Base article K00000334. |
|
| User Interface |
| | Console | | | Job diagram tool fails with license error | CR00000627
Defect | |
Due to a software build issue, the Console displayed an error message when a user attempted to diagram a job, indicating that the diagramming component was unlicensed. This problem was resolved. |
| Cannot edit schedule trigger if computer's timezone information is unreadable | CR00000629
Defect | |
In certain circumstances adTempus is unable to read the computer's timezone list. This results in an error when you try to create or edit a schedule trigger: "InvalidArgument=Value of '0' is not valid for 'index'".
This problem was resolved. |
| Search and replace fails if it encounters a network resource that has credentials | CR00000631
Defect | If you use the Search and Replace tool in the adTempus Console, the tool will fail if any of the jobs being searched use network resources for which explicit credentials have been specified.
This update fixes this problem, and extends the Search and Replace tool so that it searches the paths of network resources. |
| Job Editor | | | Cannot change condition not satisfied action for job step | CR00000616
Defect | | If you change the "If conditions(s) are not satisfied" rule for a step, the change is not saved when you click OK to close the window. This problem was fixed. |
| Cannot create or modify WMI trigger because of credential error | CR00000618
Defect | |
When you try to create or modify a WMI Trigger, adTempus gives an error message indicating that you must enter credentials for the trigger, even though the window does not provide a place to enter credentials.
This problem was resolved so that this error does not occur. |
|
|
|
