Page History

...

Known issues in version 2.2

Web browser issues

• Anchor
  SQLELEM-9619 SQLELEM-9619

  SQL Inventory Manager displays unexpected error messages if the user manually changes part of the page URL to an invalid address. You can avoid this issue by changing the URL to only known, valid URL addresses.

• Anchor
  SQLELEM-9630 SQLELEM-9630

  Users who have AlwaysOn Availability Group environments may notice errors caused by the unreadable state of the secondary cluster node.

• Anchor
  SQLELEM-9805 SQLELEM-9805

  >>> Failing after upgrade, 9.3 GB of RAM used

• Anchor
  SQLELEM-9628 SQLELEM-9628

  >>> High CPU usage on Inventory Manager Repository database server

• Anchor
  SQLELEM-9629 SQLELEM-9629

  SQL Inventory Manager occasionally discovers instances twice; once as part of the regular discovery process, than discovered again with the instance name as the associated port number.

• Anchor
  SQLELEM-9632 SQLELEM-9632

  SQL Inventory Manager fails to collect transactional activity on some databases.

• Anchor
  SQLELEM-13557 SQLELEM-13557

  SQL Inventory Manager occasionally displays the same application multiple times under different application IDs/names in the Applications list.

• Anchor
  SQLELEM-13550 SQLELEM-13550

  Browser Scan may run even when turned off.

• Anchor
  SQLELEM-9633 SQLELEM-9633

  Users may not add multiple instances when any of the instances contains a special character in the name.

• Anchor
  SQLELEM-9635 SQLELEM-9635

  Upgrading to SQL Inventory Manager 2.0 and later creates an IDERA Dashboard user named serviceuser with the type of Monitoring Group.

• Anchor
  SQLELEM-9649 SQLELEM-9649

  When a user disables monitoring for a database, the associated Health Check Recommendations update correctly, but then do not update correctly when monitoring is re-enabled even if the user attempts to restart the service.

• Anchor
  SQLELEM-13710 SQLELEM-13710

  Reports exported to XML may not include the correct summary count as displayed in the PDF/XLS.

• Anchor
  SQLELEM-13709 SQLELEM-13709

  Reports exported to PDF/XLS/XML do not include the # of Cores, Core Factor, and Possible Core Licenses values.

• Anchor
  SQLELEM-13708 SQLELEM-13708

  The SQL Server Licensing widget displays an unnecessary bracket character in the # of Sockets field.

• Anchor
  SQLELEM-13714 SQLELEM-13714

  Some users may receive an unexpected exception error when clicking Save after making a change in the Manage Health Check.

• Anchor
  SQLELEM-13548 SQLELEM-13548

  >>> If the user changes the display name when upgrading from the SQL Inventory Manager Beta version, two versions of SQL Inventory Manager will exist.

• Anchor
  SQLELEM-13712 SQLELEM-13712

  SQL Inventory Manager incorrectly displays SQL Server 2012 SP3 as SQL Server 2012 SP2 in the Discovered Instances tab.

• Anchor
  SQLELEM-9671, SQLELEM-13680 SQLELEM-9671, SQLELEM-13680

  Instead of displaying only managed instances, SQL Inventory Manager displays all discovered instances in the Managed Instances tab. This tab also may display some instances that are removed from SQL Inventory Manager.

• Anchor
  SQLELEM-13686 SQLELEM-13686

  A Guest user without the proper permissions can view the Instance Summary by manually changing the URL.

• Anchor
  SQLELEM-13561 SQLELEM-13561

  The number of discovered instances does not match in the Dashboard and the Discovered Instances tab.

• Anchor
  SQLELEM-9614 SQLELEM-9614

  SQL Inventory Manager may display the database consistency is not checked for some database although the checks are run. An additional run of the checks does not update this value.

• Anchor
  SQLELEM-13559 SQLELEM-13559

  SQL Inventory Manager may display a foreign key constraint error message when a user attempts to edit or enter a value in some custom inventory fields.

...

• Anchor
  DE45721 DE45721

  In order to set up user account for email alerts, you first must set up and enter individual email addresses in the SQL Inventory Manager Manage Administration page. User accounts added using the Manage Users link in the IDERA Dashboard Administration tab do not have their associated email address appear when viewing the account in the SQL Inventory Manager Manage Users and Subscriptions window.

• Anchor
  DE45725 DE45725

  In order to select the All Instances option for user permissions, you must select the hyperlink for that user account in the Manage Users and Subscriptions window. Select All Instances, and then click Save.

Previous known issues in 1.2

General issues

• SQL Inventory Manager supports authentication between internal services, this feature is disabled by default. To enable it, user needs to change configuration in two places.
• When the SQL Inventory Manager Service or Core Service go down, users on the Administration tab will not be notified of the services status. They may experience error messages when trying to access any options from the Administration view.

Installation and configuration

• When uninstalling SQL Inventory Manager, the user may be prompted to close other IDERA applications such as SQL Safe Management Console for example.

Adding, discovering instances

• The discovery process may take into account host computers without default SQL Server instances.
• Users should take into account that if they choose WMI as a method for scanning, they may have some limitations with the number of SQL Server instances discovered. For more information on how to view and change port ranges, click here.

Monitoring

• The auto refresh option on the Instance and Explorer view may cause the option "Apply filter as it changes" to change its selected setting.
• On the Explorer tab, users may find that after selecting different options on the View Selection lists, the View list does not collapse. To solve this issue, users can manually refresh the page or change tabs and go back to the Explorer view.

Previous known issues in 1.1

General issues

• SQL Inventory Manager may display the message "!!! missing resource key = [com.ider....]" when the Core service goes down and any action is performed on the Instances tab.
• SQL Inventory Manager supports authentication between internal services, this feature is disabled by default. To enable it, user needs to change configuration in two places. Authentication mechanism may or may not work depending upon user's security policy settings.
• SQL Inventory Manager sessions do not expire anymore if users remain on the application. If they leave the application for more than thirty minutes their session will time out and users will need to log in again.

Installation and configuration

• When uninstalling SQL Inventory Manager, the user may be prompted to close other IDERA applications such as SQL Safe Management Console for example.

Adding, discovering instances

• SQL Inventory Manager is currently not validating the information entered for IP addresses and DNS names. Users must be careful with the information they enter since invalid IP addresses or DNS names will cause the discovery to not work properly.
• If SQL Server instances are added using UseOleforWMI:True, IP and mac addresses may not be collected and may be shown as blank.
• When new tags are added in the Add SQL Server Instance wizard, SQL Inventory Manager may not display these newly added tags when accessing the See all tags option.

Monitoring

General

• SQL Inventory Manager may count SQL Server instances as down until it finishes completing their initial data gathering.
• Some WMI properties in Windows XP and Windows 2003 are not available so it is possible that SQL Inventory Manager will not collect the respective information.

Explorer view

• Filters in the Explorer view only display 10 options. The user can click More to access the complete list of options. However, if the user selects options from the extended list, they may not be displayed on the initial view.
• On version 1.0, on the Explorer view, when the user filtered by tags, they could be displayed "by name" or "by count". Currently for Version 1.1 this option is not available.

Health Checks recommendations

• The Refresh option allows to get the latest information from Instances or Health Check Recommendations. When clicking this option, a request for running a background refreshing job is requested and the "Refreshing" status is displayed. This job may take some time so manual refresh is required.
• To receive alert notifications, email addresses need to be provided. The field where these email addresses are specified may not validate the correct email format.

Dashboard

• Data from each instance and health check recommendation in the Dashboard can be refreshed; however, there is no option yet to refresh all instances or recommendations at once.
• The data size of instances that are down may still be taken into account in the data size information of the Dashboard and Instance tab.

Instance details view

• The side bar of the Instance Details view of an instance with "Unknown Error" or "Unresponsive" state may not display the latest information collected

  .

• Information that SQL Inventory Manager was not able to collect such as SQL Server version, Host Server, databases, size, etc., may be displayed with zero value or as blank in the Instance Details view.
• SQL Inventory Manager gathers Driver information taking into account only the server hosting the instance. There is no distinction between drivers that are in a clustered resource group or not. Consequently, it is possible that in a clustered instance, SQL Inventory Manager will display "No drives found" in the Computer Details.

Previous known issues in 1.0

General

• SQL Inventory Manager does not support SQL Server 2000 instances. For more information on the supported SQL server instances, click here.

Installation and configuration

• When uninstalling SQL Inventory Manager, it may be necessary to close other SQL Server applications opened.
• An error message may be displayed when trying to install SQL Inventory Manager on a mirrored SQL Server instance. (Error -2147467259: Failed to create SQL database elem, error detail: unknown error).

Adding, discovering instances

• The Add Instance Wizard does not validate already managed SQL servers until the last step of the wizard when it tries to add it. Additionally in this version, SQL Inventory Manager may let you type any instance name without validation.

Credentials

• Users may get a "credentials failed" message with an incorrect login name on the message. They may also get this message with a blank user name when the windows account does not exist.

Monitoring

General

• SQL Server Instances with a down status may cause a discrepancy in the total instance data size and log size in the Dashboard, Explorer, and Instance view.
• It is possible that recently added instances with N/A and Authentication Failed status display a down status on the right sidebar. This is due to SQL Inventory Manager may not have completed running the initial data gathering; and therefore, it is not known yet the real status of those instances. 
• The user may experience the following message in the Administration tab: "!!! missing resource message key=[com.idera.common.rest.RestException: An exception occurred getting the product configuration.] args=[]",  when IDERA core/Inventory Manager services are down.

Explorer view

• The Explorer view may let users apply filters for instances that are down.
• On the Explorer view when filtering by tags, the total data size may take into account instances more than once for those ones that are linked to different tags.

Health Check Recommendations

...