Idera strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact Support.
In this section you can find information on:
- Issues known in this version.
- Issues known in recent releases.
- Issues known in releases previous to SQLdm 7.5.
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 SQLdm 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.
Previous known issues
Known issues in version 8.6
Alerting
SQL diagnostic manager fails to update statistics for some monitored SQL servers and triggers a persistent alert ‘Unable To Monitor’ for the same
Users 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 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 SQLdm 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-checked
Users 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, SQLdm 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.
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.
Known issues in version 8.5
General
The Query Monitor trace in SQL diagnostic manager does not return queries in progress
Users 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 window after the virtualization host server is edited
Users 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.
Alerting
SQLdm returns Blocking Session Wait Time alerts with session 0 and missing information when blocking-process node is empty
Some 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 SQLdm 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 SQLdm 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.0
Installation and configuration issues
The SQLdm Setup Wizard is interrupted after selecting the SQL server instance on which you want to install the SQLdm Repository
Some users may experience an interruption due to memory corruption in their SQLdm installation after selecting the SQL Server instance on which they want to install their SQLdm Repository. Note that the SQLdm 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 collection
Some users may receive negative values from vCenter as a warning message. The message is logged as in the SQLdm 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 SQLdm 8.0 while logged in the Idera Newsfeed account
Users who remain logged in the Idera Newsfeed account and upgrade to SQLdm 8.0 may experience console crashes. Note that an upgrade from SQLdm 8.0 to 8.0.1 will solve this issue.
Known issues in version 7.5
General
SQLdm 7.5 no longer supports Microsoft Windows 2000 or the .Net 2.0 framework
SQLdm 7.5 does not support Windows 2000 or the .Net 2.0 framework. While SQLdm 7.2 and prior versions continue to operate with Windows 2000, SQLdm 7.5 and later require the .Net 4.0 Full framework to take advantage of the additional features. For additional information about supported versions, see SQLdm requirements.
Server Overview
Timeline refresh causes a memory leak
SQLdm experiences a memory leak when you are viewing the Timeline and click Refresh. To free the memory, you must restart the SQLdm Management Console.
Queries
Queries view filter may not properly filter in some situations
In environments with large databases, the Queries view filter may not properly filter if you attempt to change filter properties during a refresh.
Resources
File Activity displays an unhelpful error message when WMI credentials are invalid
SQLdm 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 considerations
SQLdm Repository computer must run Microsoft SQL Server 2005 or later
SQLdm 7.0 and later require Microsoft SQL Server 2005 or later running on the computer that hosts the SQLdm Repository database for all installations.
SQLdm Console only users cannot upgrade to the full version without uninstalling SQLdm
Users who have an installation of SQLdm 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 SQLdm.
Registering a SQL Server instance that uses an Alias Name requires an alias on the host computer
When 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 incorrect
If the account you specified for the SQLdm 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 SQLdm stating that there is no valid license available
To 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.
SQLdm Reporting does not support Microsoft Reporting Services 2000
SQLdm only supports Microsoft Reporting Services 2005 and later.
SQLdm requires Predictive Analytics for baseline-related results
SQLdm 7.5 requires the Predictive Analytics Service in order to display baseline-related results. During installations and upgrades, SQLdm installs the Predictive Analytic service with the other included services. If Predictive Analytics is not detected or is disabled, SQLdm cannot generate baseline data for the requested report. The following reports require the Predictive Analysis Service to include baseline-related results:
Phase out SQLdm mobile manager
Idera 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 SQLdm 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 Express
SQLdm 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 Programs
To 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 instances
The 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 another
Even if the circumstances warrant SQLdm 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 collection
Some users may receive negative values from vCenter as a warning message. The message is logged as in the SQLdm 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 users
Some 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 checkbox is checked in the Advanced Query Monitor Configuration window.
SQLdm Mobile Server Dashboard charts display “Data not available” error
This 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 instances
The 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 view
This 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 characters
For servers and path names that include special characters such as % or #, SQLdm may incorrectly report the remaining disk space as zero.
Known issues in versions previous to 7.5
General
SQLdm displays a refresh error when a user attempts to view data for an instance to which he does not have admin rights
SQLdm displays a refresh error message when a user tries to view data for a monitored SQL Server instance to which the user does not have administrative rights. The message states that, "An error occurred while refreshing the active view."
SQLdm displays an error when a user attempts to configure disk collection for an instance to which he does not have admin rights
SQLdm displays an error message on the Server Properties Disk Drives window if a user's collection service credentials do not have administrative access to the monitored SQL Server instance, and the user attempts to view the list of attached disk drives on that instance. Note that WMI credentials are not used to retrieve disk drive information on this page.
Drives may not appear in the Resources Disk view when you switch to direct WMI collection
Users who select to collect OS metrics using direct WMI collection may notice mounted drives appearing in some areas of SQLdm but not on the Resources Disk view. To refresh this list, you must restart the SQLdm Management Console.
Dashboard
Custom Counters dashboard panel does not return to default after deleting all counters
The Custom Counters dashboard panel includes a drop-down list to allow you to select from the available counters. If you delete all counters, the panel does not return to the default title and continues to display one of the counter names.
Resources
Disk Filter Columns does not work on a blank chart
The Filter Columns selection does not work in the Resources > Disk view if you receive a blank chart due to your WMI credentials being invalid.
Alerts
OS Disk Time (Percent) and OS Disk Time Per Disk (Percent) alerts may not trigger for some users
Users with Windows Server 2008 SP1 and SQL Server 2000 SP4, and who select direct WMI collection for their OS metrics may experience an issue preventing OS Disk Time (Percent) and OS Disk Time Per Disk (Percent) alerts from triggering. If this issue occurs, switch to using OLE automation.
Virtualization-related alerts occasionally raise more than once
In some circumstances, SQLdm may repeatedly raise virtualization-related alerts when there is no change in the status.
Custom Counters
SQLdm does not automatically add unassociated custom counters to an alert template created from an instance
If you use alert templates and create a custom counter, SQLdm automatically adds the new counter to your existing alert templates. However, if you create a custom counter not associated with an instance, and then create an alert template based on the alert configuration of one of your monitored instances, SQLdm does not add the new counter to your alert template nor can you manually add the counter.
To avoid this issue, add the missing custom counter to any SQL Server instance, create an alert template from that instance, and then clear any undesired custom counters from that instance.
SQLdm Mobile
SQLdm Mobile My Servers view filter does not work
The filter on this view will consistently display the message, “You have no favored or followed servers or the servers list has not been cached yet,” regardless of the filter option you choose. This issue occurs even when you are following servers or have marked servers as favorites.