Page History
IDERA strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact
Newtablink | ||||
---|---|---|---|---|
|
In this section you can find information on:
- Issues known in this version.
- Issues known in recent releases.
- Issues known in releases previous to SQL Diagnostic Manager 10.0
...
Anchor | ||||
---|---|---|---|---|
|
Licensing
When entering a license key, the SQL Diagnostic Manager License Key Wizard may throw an exception while referencing a Windows registry path. To avoid this error, launch the SQLDM Desktop Client using the 'Run as Administrator' option.
Disk Size
SQL Diagnostic Manager will not be able to determine the available Disk Size of Mount Points for any SQL Server version older than SQL Server 2008 R2.
Drive metrics
SQL Diagnostic Manager drive metrics cannot detect the disk drives using OLE Automation, it is only possible when using WMI.
Anchor | ||||
---|---|---|---|---|
|
...
Known Issues in version 11.0
Reports
The 'Days since last backup metric' is based on the last time any kind of backup (Full, differential, or transaction log) was made on the database.
...
The load time is longer for Azure screens because some features have been upgraded, such as:
- The The 'Batch Collection' metric that has been replaced with individual collections makes the load time longer.
- The 'Initial Collections'in which the load time can be longer.
...
The Blocked Process Threshold is automatically updated when the activity monitor trace/extended event session starts, even if it already has the correct value.
By changing the Blocked Process Threshold, SQL Server reports that a configuration setting has changed. The "correct" value is set in the SQLDM instance properties under the Activity Monitor tab.
...
The Session tab may not be visible if the database is unloaded and SQL Diagnostic Manager and System sessions are filtered.
...
Known issues in version 10.6
...
Info |
---|
All the fixes included in 10.4.2 and 10.4.3 have not been integrated in SQL Diagnostic Manager 10.5. These Fix Versions are included in the upcoming version SQL Diagnostic Manager 10.5.1. |
...
The license library has changed. If you encounter problems with your current license, contact Licensing.
Installation and upgrade
Upgrading SQL Diagnostic Manager
...
The friendly name assigned to an instance through PowerShell is not being automatically refreshed and is not being displayed in the Desktop Console UI. Right-click All Servers in the tree pane and select Refresh to to manually refresh the instances information and visualize the assigned friendly name.
...
Anchor | ||||
---|---|---|---|---|
|
SQL Diagnostic Manager version 10.0 is designed to integrate with License Manager 2.0, allowing for a self-service licensing model. However, an issue in the Generate License Keys link of the License Keys window fails to direct to License Manager. For additional information on this feature and a workaround, see see Generate a new license key.
IDERA Dashboard and web console console
Anchor | ||||
---|---|---|---|---|
|
Some SQL Diagnostic Manager users may find that it takes approximately a minute for any of their monitored instances to display in views of the SQL Diagnostic Manager web console where a list of instances is available.
...
Expand | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
Known issues in version 9.1 General
Anchor |
|
Anchor | ||||
---|---|---|---|---|
|
SQL SQL Diagnostic Manager is designed to allow users access to the SQL SQL Diagnostic Manager Console from the Thumbnail, Heatmap, and Alerts Detail views. In SQL Diagnostic Manager 9.1 clicking the ‘launch SQLdm’ icon takes users to the corresponding instance dashboard screen but occasionally fails to clearly mark the specific instance it refers to in the Servers tree
Alerting
AnchorDE43024 DE43024
SQL Diagnostic Manager fails to display one alert response when multiple metric thresholds are breached
DE43024 | |
DE43024 |
SQL Diagnostic Manager version 8.5 and later is designed to trigger an alert response only after multiple metric thresholds are breached when the “Where all metrics are in specified list” condition is selected. However, an issue in the “Send a Network Management (SNMP) Trap Message”, “Send an email to recipient”, and “Run the following SQL Script” actions of the Alert Response Window cause these actions to execute several times, resulting in multiple alerts.
AnchorDE43027 DE43027
The action “Run the following program” fails to execute when configuring automated responses to alerts
DE43027 | |
DE43027 |
Users with SQL Diagnostic Manager version 8.0 and later may find that when creating an alert response with the associated action “Run the following program” in the Alert Response window, the specified program does not run once the condition is met.
AnchorDE43056 DE43056
SQL Diagnostic Manager returns PoweredOff alerts for the VM Power State metric when servers are not turned off
DE43056 | |
DE43056 |
Some SQL SQL Diagnostic Manager users may view PoweredOff alerts when reviewing the generated “VM Power State” alerts for their servers linked to vCenter or Hyper-V host servers. These alerts display even though the servers are not turned off.
AnchorDE42976 DE42976
The actions “Write an event to the Windows event log” and “Send an email to recipient” in the Alert Response Window fail to deliver multiple alert statuses
DE42976 | |
DE42976 |
Users with SQL Diagnostic Manager version 8.5 and later may find that when creating an alert response with multiple metrics as a condition and associated actions “Write an event to the Windows event log” and/or “Send an email to recipient” in the Alert Response window, the feature fails to deliver complete alert information and displays only one alert status when condition is met.
VM Configuration
AnchorDE43066 DE43066
SQL Diagnostic Manager fails to update fields in the VM Configuration window after the virtualization host server is edited
DE43066 | |
DE43066 |
Users with SQL Diagnostic Manager version 8.5 and later may find that fields such as the Virtual Machine name, Type, and Computer Name in the VM Configuration window are not updated correctly after the virtualization host server is changed.
Known issues in version 9.0
General
SQL Diagnostic Manager fails to update fields in the VM Configuration window after the virtualization host server is edited
Users with SQL Diagnostic Manager version 8.5 and later may find that fields such as the Virtual Machine name, Type, and Computer Name in the VM Configuration window are not updated correctly after the virtualization host server is changed.
Web Application Service
The IDERA Dashboard's Web Application Service fails to restart after reboot
Users with SQL Diagnostic Manager version 9.0 may find that the IDERA Dashboard's Web Application Service does not automatically restart after a machine reboot.
Alerting
SQL Diagnostic Manager fails to display one alert response when multiple metric thresholds are breached
SQL Diagnostic Manager version 8.5 and later is designed to trigger an alert response only after multiple metric thresholds are breached when the “Where all metrics are in specified list” condition is selected. However, an issue in the “Send a Network Management (SNMP) Trap Message”, “Send an email to recipient”, and “Run the following SQL Script” actions of the Alert Response Window cause these actions to execute several times, resulting in multiple alerts.
The action “Run the following program” fails to execute when configuring automated responses to alerts
Users with SQL Diagnostic Manager version 8.0 and later may find that when creating an alert response with the associated action “Run the following program” in the Alert Response window, the specified program does not run once the condition is met.
SQL Diagnostic Manager returns PoweredOff alerts for the VM Power State metric when servers are not turned off
Some SQL SQL Diagnostic Manager users may view PoweredOff alerts when reviewing the generated “VM Power State” alerts for their servers linked to vCenter or Hyper-V host servers. These alerts display even though the servers are not turned off.
The actions “Write an event to the Windows event log” and “Send an email to recipient” in the Alert Response Window fail to deliver multiple alert statuses
Users with SQL Diagnostic Manager version 8.5 and later may find that when creating an alert response with multiple metrics as a condition and associated actions “Write an event to the Windows event log” and/or “Send an email to recipient” in the Alert Response window, the feature fails to deliver complete alert information and displays only one alert status when condition is met.
Expand | ||
---|---|---|
| ||
Known issues in version 8.6AlertingSQL Diagnostic Manager fails to update statistics for some monitored SQL servers and triggers a persistent alert ‘Unable To Monitor’ for the sameUsers with SQL Diagnostic Manager version 8.0.1 and later may find that some servers are not returning any statistics due to an issue in the Activity Monitor settings that causes the entire refresh of servers to fail. SQL Diagnostic Manager fails to display one alert response when multiple metric thresholds are breachedSQL Diagnostic Manager version 8.5 and later is designed to trigger an alert response only after multiple metric thresholds are breached when the “Where all metrics are in specified list” condition is selected. However, an issue in the “Send a Network Management (SNMP) Trap Message”, “Send an email to recipient”, and “Run the following SQL Script” actions of the Alert Response Window cause these actions to execute several times, resulting in multiple alerts. The action “Run the following program” fails to execute when configuring automated responses to alertsUsers with SQL Diagnostic Manager version 8.0 and later may find that when creating an alert response with the associated action “Run the following program” in the Alert Response window, the specified program does not run once the condition is met. The actions “Write an event to the Windows event log” and “Send an email to recipient” in the Alert Response Window fail to deliver multiple alert statusesUsers with SQL Diagnostic Manager version 8.5 and later may find that when creating an alert response with multiple metrics as a condition and associated actions “Write an event to the Windows event log” and/or “Send an email to recipient” in the Alert Response window, the feature fails to deliver complete alert information and displays only one alert status when condition is met. SQL Diagnostic Manager returns PoweredOff alerts for the VM Power State metric when servers are not turned offSome SQL SQL Diagnostic Manager users may view PoweredOff alerts when reviewing the generated “VM Power State” alerts for their servers linked to vCenter or Hyper-V host servers. These alerts display even though the servers are not turned off. SQL Diagnostic Manager fails to stop alert generation after the Availability Group Preferred Replica alert is un-checkedUsers with SQL Diagnostic Manager version 8.6 that have the Availability Group Preferred Replica alert configured may find that when un-checking the alert in the Alert Configuration window to stop raising the alert, SQL SQL Diagnostic Manager continues to generate the alert which also displays in the Alerts View. Un-checking the configured database in the Configuration tab of the Alert Configuration window solves this issue. GeneralSQL Diagnostic Manager fails to update fields in the VM Configuration window after the virtualization host server is editedUsers with SQL Diagnostic Manager version 8.5 and later may find that fields such as the Virtual Machine name, Type, and Computer Name in the VM Configuration window are not updated correctly after the virtualization host server is changed. Known issues in version 8.5GeneralThe Query Monitor trace in SQL Diagnostic Manager does not return queries in progressUsers with SQL Diagnostic Manager version 8.0 and later may find that when using the Query Monitor functionality, the queries returned and displayed do not include queries in progress. SQL Diagnostic Manager fails to update fields in the VM Configuration VM Configuration window after the virtualization host server is editedUsers with SQL Diagnostic Manager version 8.5 may find that fields such as the Virtual Machine name, Type, and Computer Name in the VM Configuration window are not updated correctly after the virtualization host server is changed. AlertingSQL Diagnostic Manager returns Blocking Session Wait Time alerts with session 0 and missing information when blocking-process node is emptySome users may experience Blocking Session Wait Time alerts with missing information and session 0 when the blocking-process node is empty in SQL Server. In SQL SQL Diagnostic Manager 8.01 and later versions, this issue may occur only if the trace that is collecting blocking data doesn’t return a SPID for a blocking process. SQL Diagnostic Manager fails to display one alert response when multiple metric thresholds are breached.SQL Diagnostic Manager version 8.5 and later is designed to trigger an alert response only after multiple metric thresholds are breached when the “Where all metrics are in specified list” condition is selected. However, an issue in the “Send a Network Management (SNMP) Trap Message”, “Send an email to recipient”, and “Run the following SQL Script” actions of the Alert Response Window cause these actions to execute several times, resulting in multiple alerts. The action “Run the following program” fails to execute when configuring automated responses to alerts.Users with SQL Diagnostic Manager version 8.0 and later may find that when creating an alert response with the associated action “Run the following program” in the Alert Response window, the specified program does not run once the condition is met. The actions “Write an event to the Windows event log” and “Send an email to recipient” in the Alert Response Window fail to deliver multiple alert statuses.Users with SQL Diagnostic Manager version 8.5 and later may find that when creating an alert response with multiple metrics as a condition and associated actions “Write an event to the Windows event log” and/or “Send an email to recipient” in the Alert Response window, the feature fails to deliver complete alert information and displays only one alert status when condition is met. SQL Diagnostic Manager returns PoweredOff alerts for the VM Power State metric when servers are not turned off.Some SQL SQL Diagnostic Manager users may view PoweredOff alerts when reviewing the generated “VM Power State” alerts for their servers linked to vCenter or Hyper-V host servers. These alerts display even though the servers are not turned off. Known issues in version 8.0Installation and configuration issuesThe SQLdm Setup Wizard is interrupted after selecting the SQL server instance on which you want to install the SQL Diagnostic Manager RepositorySome users may experience an interruption due to memory corruption in their SQL SQL Diagnostic Manager installation after selecting the SQL Server instance on which they want to install their SQL SQL Diagnostic Manager Repository. Note that the SQL SQL Diagnostic Manager installer does not complete on machines where memory corruption prevents connections to SQL Server. Furthermore, in these types of environments other applications such as SQL Server Management Studio also do not function. Negative values received from vCenter as a warning message do not impact VM data collectionSome users may receive negative values from vCenter as a warning message. The message is logged as in the SQL SQL Diagnostic Manager Services. Note that this does not have any impact in terms of VM data collection and users are able to view VM and VM Host data. Console crashes when upgrading to SQL SQL Diagnostic Manager 8.0 while logged in the IDERA Newsfeed accountUsers who remain logged in the IDERA Newsfeed account and upgrade to SQL SQL Diagnostic Manager 8.0 may experience console crashes. Note that an upgrade from SQL SQL Diagnostic Manager 8.0 to 8.0.1 will solve this issue. |
Expand | ||
---|---|---|
| ||
Known issues in version 7.5GeneralSQL SQL Diagnostic Manager 7.5 no longer supports Microsoft Windows 2000 or the .Net 2.0 frameworkSQL SQL Diagnostic Manager 7.5 does not support Windows 2000 or the .Net 2.0 framework. While SQL SQL Diagnostic Manager 7.2 and prior versions continue to operate with Windows 2000, SQL SQL Diagnostic Manager 7.5 and later require the .Net 4.0 Full framework to take advantage of the additional features. Server OverviewTimeline refresh causes a memory leakSQL SQL Diagnostic Manager experiences a memory leak when you are viewing the Timeline and click Refresh. To free the memory, you must restart the SQL SQL Diagnostic Manager Management Console. QueriesQueries view filter may not properly filter in some situationsIn environments with large databases, the Queries view filter may not properly filter if you attempt to change filter properties during a refresh. ResourcesFile Activity displays an unhelpful error message when WMI credentials are invalidSQL SQL Diagnostic Manager displays the error message, "An error occurred while refreshing the active view," when you attempt with access the Resources > File Activity view if your WMI credentials are invalid. If this message appears, verify your WMI access credentials and try again. Installation and configuration considerationsSQL SQL Diagnostic Manager Repository computer must run Microsoft SQL Server 2005 or laterSQL SQL Diagnostic Manager 7.0 and later require Microsoft SQL Server 2005 or later running on the computer that hosts the SQL SQL Diagnostic Manager Repository database for all installations. SQL SQL Diagnostic Manager Console only users cannot upgrade to the full version without uninstalling SQL SQL Diagnostic ManagerUsers who have an installation of SQL SQL Diagnostic Manager Console only on a computer can use the upgrade to update their current version of the desktop client console, but cannot use the upgrade program to install the full version of SQL Diagnostic Manager. Registering a SQL Server instance that uses an Alias Name requires an alias on the host computerWhen registering a SQL Server instance using the alias name, an alias must first be created on the computer that hosts the SQLdm Management and Collection Services. If the instance uses Named Pipes, Named Pipes must be enabled in the SQL Server network configuration of the aliased SQL Server instance. Management Service does not start when the account permissions are incorrectIf the account you specified for the SQL SQL Diagnostic Manager services does not have System Administrator privileges on the SQL Server instance hosting the Repository database, the setup program cannot start the SQLdm Management Service. This issue only occurs during installation. Some users may receive an error message when opening the SQL SQL Diagnostic Manager stating that there is no valid license availableTo resolve this issue, use the Management Service Configuration wizard to specify credentials for a Windows account or SQL Server login that has System Administrator privileges on the SQL Server instance hosting the Repository database. You can start the Management Service Configuration wizard from the Programs menu. SQL SQL Diagnostic Manager Reporting does not support Microsoft Reporting Services 2000SQL SQL Diagnostic Manager only supports Microsoft Reporting Services 2005 and later. SQL SQL Diagnostic Manager requires Predictive Analytics for baseline-related resultsSQL SQL Diagnostic Manager 7.5 requires the Predictive Analytics Service in order to display baseline-related results. During installations and upgrades, SQL SQL Diagnostic Manager installs the Predictive Analytic service with the other included services. If Predictive Analytics is not detected or is disabled, SQL SQL Diagnostic Manager cannot generate baseline data for the requested report. The following reports require the Predictive Analysis Service to include baseline-related results: Phase out SQL SQL Diagnostic Manager mobile managerIDERA is announcing end of life for SQL mobile manager (SQLmm). On October 1, 2012, all support for SQLmm will stop and the SQLmm trial site will be decommissioned. Also, any remaining installations of SQLmm 3.6 or earlier that use the IDERA redirectors will no longer work. To continue using a Web-based monitoring solution that is accessible from your smart phones or tablet devices, upgrade to SQL SQL Diagnostic Manager 7.0 or later, and deploy SQLdm Mobile. IDERA discontinued distribution of SQL mobile manager in October 2011. SQLdm Mobile does not support Microsoft IIS ExpressSQLdm Mobile requires the standard version of the Microsoft IIS Web Server, version 7.0 or later. For more information, see the SQLdm Mobile requirements. SQLdm Mobile & Newsfeed installation cannot be changed or repaired using Add/Remove ProgramsTo successfully change or repair your SQLdm Mobile & Newsfeed installation, uninstall the application and components, and then run the setup program to reinstall your deployment. SQLdm may not properly link to vCenter from some monitored virtual SQL Server instancesThe SQLdm VM Configuration window displays a list of your monitored virtual SQL Server instances, but the link between an instance and the associated vCenter may not work properly. To access this window, click Tools > VM Configuration. VM Host Server Change alert not always triggered when a VM moves from one host server to anotherEven if the circumstances warrant SQL SQL Diagnostic Manager to trigger the VM Host Server Change alert, users who have virtual machines running on an ESX host managed by vCenter 5.0 or later may not receive the alert when they move a VM from one host to another. Negative values received from vCenter as a warning message do not impact VM data collectionSome users may receive negative values from vCenter as a warning message. The message is logged as in the SQL SQL Diagnostic Manager Services. Note that this does not have any impact in terms of VM data collection and users are able to view VM and VM Host data. Query Monitor disregards filter for SQL Server 2000 usersSome SQL Server 2000 users may notice that SQLdm Query Monitor includes SQL Diagnostic Manager queries in the results even if the Exclude SQL Diagnostic Manager queries check box is checked in the Advanced Query Monitor Configuration window. SQLdm Mobile Server Dashboard charts display “Data not available” errorThis error indicates that SQLdm Mobile was not able to collect all the performance metrics tracked by these charts. This issue is more likely to occur with the I/O and Per Read/Write charts on the Disk dashboard. To correct this issue, use the Microsoft IIS Manager console to restart the SQLdm Mobile Web site (virtual directory). Start and Stop service actions not supported for virtual SQL Server instancesThe Start and Stop service actions are not supported for virtual SQL Server instances (instances located on a Windows cluster node). To start or stop a service on a virtual SQL Server 2008 instance, use the Microsoft Failover Cluster Management tool. For SQL Server 2005 or earlier, use the Microsoft Cluster Administrator tool to manage services. Gaps between the real-time view and back-filled historical data can be seen on the CPU viewThis occurs only when the CPU view is accessed via the Server tree. To view the information, without any gaps, access the CPU view via the ribbon. Free disk space reported as zero on databases with special charactersFor servers and path names that include special characters such as % or #, SQL SQL Diagnostic Manager may incorrectly report the remaining disk space as zero. |
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Anchor |
|
...