Page tree

Known issues in version 2.2

Upgrades

  • Upgrade SQL Enterprise Job Manager from an earlier version, requires version by version upgrade until the latest version.

Known issues in version 2.1

Filters

  • Instance filter is currently not working for tasks when selected in the Schedule tab. 

  • Schedule filter is incorrectly placed under the Status filtering options of the Windows Task Scheduler view. 

Instances Registration

  • Users trying to add instances when two different versions of SQL Enterprise Job Manager are installed on the same IDERA Dashboard could find an error message and not be able to add them. 

  • Instances registered before upgrading SQL Enterprise Job Manager to the latest version are not displayed on the Managed Instances section of the IDERA Dashboard.

Jobs

  • When users edit a multi-instance job to create individual jobs on each instance, the job history of the relevant instances could not display the original multi-instance job properly.

  • Job Details pop-up windows are incorrectly displayed while hovering over different Job Runtime Chart locations.

IDERA Dashboard

  • Removed Instances may still be displayed in the Managed Instances section of the IDERA Dashboard.

  • Removed users may still be displayed in the Managed Users section of the IDERA Dashboard with an unassigned role.

Other Issues

  • Windows Server 2012 is currently not populated as an operating system option to be configured for in the Task Scheduler wizard. 

  • SQL Enterprise Job Manager may prompt an error message when double clicking options through the web console.

  • The collector service of SQL Enterprise Job Manager may stop running under unknown circumstances. Users will need to reboot the respective service. 

  • Users may find an error message while executing the Collection Job on a specific Instance on the Instances tab.

  • SQL Enterprise Job Manager is not displaying the CPU information accurately in the Server Performance Chart.

Known issues in version 2.0

Installation

  • SQL Enterprise Job Manager 2.0 installer does not upgrade from versions 1.0 and 1.1. Users have to uninstall first the 1.x build, then install 2.0. However, during installation users can point the 2.0 installer to previous repository databases so that no data is lost from their 1.x install. 

  • As part of integration with the IDERA Dashboard, a Dashboard user is required to log in the SQL Enterprise Job Manager web application. Users created in 1.x versions are no longer valid. After 2.0 is installed, users will need to be re-created either from the Dashboard Administration tab or the SQL Enterprise Job Manager Administration tab (which syncs the user to the Dashboard.)

  • SQL Enterprise Job Manager may prompt to close other IDERA products such as SQLdm or SQLsafe for its uninstall process.   

Adding/Editing Jobs

  • Users may notice that as soon as they create a new job, the Last Run Outcome for this job is shown as failed in the Jobs tab. Once the collector runs, the status is updated to Unknown or the respective outcome if it ran. 

  • This version provides the most important functionality to create/edit SQL Server jobs. Users should take into account that some options, like job step types (“SQL Server Analysis Services Command” or “SQL Server Integration Services Package” for example) that are handled by SQL Server Management Studio, may not be present in the current version of SQL Enterprise Job Manager.  

  • Users may find that when they switch views after they reschedule jobs in the Schedule tab, the changes in the rescheduled job will not be updated in the calendar until the collector runs or they manually refresh the data.

  • Users will not be able to edit jobs with names that contain characters such as “&” and “+”.  Additionally, users should take into account that jobs with names that include ‘ and “ characters, may not be allowed to edit these jobs or will be prompted with an error message when trying to edit them.   

  • Any selection made to multiple items across SQL Enterprise Job Manager lists (jobs, instances, and alert rules) will be lost when sorting, filtering, refreshing, moving through pages, or performing other actions on the same section. 

  • On the Schedule tab when users double click a time slot to create a new job, SQL Enterprise Job Manager currently does not display the job created in the selected time slot. It takes into account the time slot selected, and according to the time zone difference between instance and calendar, it displays in the calendar the time slot that would correspond to that time in the instance. For example, if the time zone of the computer where SQL Enterprise Job Manager is running is at UTC-6 and the instance where the user chooses to create a job  is at UTC-8 time zone, when the user double clicks the 7:00 pm time slot to create a job, the following outcomes should be expected: 

    • The job will be created at 7:00 pm on the selected instance. 

    • The Schedule tab will take into account the time zone difference between instance and calendar and will display the job 9:00 pm.

Known issues in version 1.0

Installation

  • SQL Enterprise Job Manager may prompt to close other IDERA products such as SQLdm or SQLsafe for its uninstall process.   

General

  • When the server running SQL Enterprise Job Manager is rebooted, users may find that  the SQL Enterprise Job Manager Collection service has not started and an error message will be displayed indicating that the service is not running.

Adding/Editing Jobs

  • This first version provides the most important functionality to create/edit SQL Server jobs. Users should take into account that some options, like job step types (“SQL Server Analysis Services Command” or “SQL Server Integration Services Package” for example) that are handled by SQL Server Management Studio, may not be present in the current version of SQL Enterprise Job Manager.  

  • Users may find that when they switch views after they reschedule jobs in the Schedule tab, the changes in the rescheduled job will not be updated in the calendar until the collector runs or they manually refresh the data.

  • Users will not be able to edit jobs with names that contain characters such as “&” and “+”.  Additionally, users should take into account that jobs with names that include ‘ and “ characters, may not be allowed to edit these jobs or will be prompted with an error message when trying to edit them.   

  • Any selection made to multiple items across SQL Enterprise Job Manager lists (jobs, instances, and alert rules) will be lost when sorting, filtering, refreshing, moving through pages, or performing other actions on the same section. 

  • On the Schedule tab when users double click a time slot to create a new job, SQL Enterprise Job Manager currently does not display the job created in the selected time slot. It takes into account the time slot selected, and according to the time zone difference between instance and calendar, it displays in the calendar the time slot that would correspond to that time in the instance. For example, if the time zone of the computer where SQL Enterprise Job Manager is running is at UTC-6 and the instance where the user chooses to create a job  is at UTC-8 time zone, when the user double clicks the 7:00 pm time slot to create a job, the following outcomes should be expected: 

    • The job will be created at 7:00 pm on the selected instance. 

    • The Schedule tab will take into account the time zone difference between instance and calendar and will display the job 9:00 pm.


IDERA |  Products | Purchase | Support |  Community | Resources |  About Us | Legal