Versions Compared

Old Version 9

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 10

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Known issues in version 2.2

No longer supports repositories on SQL Server 2005

SQL Inventory Manager 2.2 and later no longer support the use of SQL Server 2005 as a repository. The product does continue to support discovered and managed instances on SQL Server 2005.

Installation and upgrade issues

  • Anchor
    SQLELEM-9805
    SQLELEM-9805
    >>> Failing after upgrade, 9.3 GB of RAM used
  • Anchor
    SQLELEM-96359619
    SQLELEM-96199635
    Upgrading to 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.2.0 and later creates an IDERA Dashboard user named serviceuser with the type of Monitoring Group.
  • Anchor
    SQLELEM-963013548
    SQLELEM-9630
    Users who have AlwaysOn Availability Group environments may notice errors caused by the unreadable state of the secondary cluster node
    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.

IDERA Dashboard issues

  • .
    Anchor
    SQLELEM-980513708
    SQLELEM-9805
    >>> Failing after upgrade, 9.3 GB of RAM used
    13708
    The SQL Server Licensing widget displays an unnecessary bracket character in the # of Sockets field.
  • Anchor
    SQLELEM-962813561
    SQLELEM-9628
    >>> High CPU usage on Inventory Manager Repository database server
    13561
    The number of discovered instances does not match in the Dashboard and the Discovered Instances tab.

Discovery issues

  • 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-963213712
    SQLELEM-963213712
    SQL Inventory Manager fails to collect transactional activity on some databasesincorrectly displays SQL Server 2012 SP3 as SQL Server 2012 SP2 in the Discovered Instances tab.
  • Anchor
    SQLELEM-9671, SQLELEM-1355713680
    SQLELEM-135579671, SQLELEM-13680
    Instead of displaying only managed instances, SQL Inventory Manager occasionally displays the same application multiple times under different application IDs/names in the Applications list. AnchorSQLELEM-13550SQLELEM-13550Browser Scan may run even when turned offdisplays all discovered instances in the Managed Instances tab. This tab also may display some instances that are removed from SQL Inventory Manager.
  • Anchor
    SQLELEM-9633
    SQLELEM-9633
    Users may not add multiple instances when any of the instances contains a special character in the name.

Monitoring issues

  • Anchor
    SQLELEM-96359632
    SQLELEM-9635
    Upgrading to SQL Inventory Manager 2.0 and later creates an IDERA Dashboard user named serviceuser with the type of Monitoring Group
    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-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
    Anchor
    SQLELEM-13710SQLELEM-13710
    Reports exported to XML may not include the correct summary count as displayed in the PDF/XLS. AnchorSQLELEM-13709SQLELEM-13709Reports exported to PDF/XLS/XML do not include the # of Cores, Core Factor, and Possible Core Licenses values. AnchorSQLELEM-13708SQLELEM-13708The SQL Server Licensing widget displays an unnecessary bracket character in the # of Sockets field.
    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
    Anchor
    SQLELEM-13548SQLELEM-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. AnchorSQLELEM-13712SQLELEM-13712SQL Inventory Manager incorrectly displays SQL Server 2012 SP3 as SQL Server 2012 SP2 in the Discovered Instances tab. AnchorSQLELEM-9671, SQLELEM-13680SQLELEM-9671, SQLELEM-13680Instead 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.
    SQLELEM-13686
    SQLELEM-13686
    A Guest user without the proper permissions can view the Instance Summary by manually changing the URL.
  • SQLELEM-13561
    Anchor
    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
    SQLELEM-9630
    SQLELEM-9630
    Users who have AlwaysOn Availability Group environments may notice errors caused by the unreadable state of the secondary cluster node.

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-13550
    SQLELEM-13550
    Browser Scan may run even when turned off.

Performance issues

  • Anchor
    SQLELEM-9628
    SQLELEM-9628
    >>> High CPU usage on Inventory Manager Repository database server.

Reporting issues

  • 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.

 

Previous known issues

Installation and upgrade issues

  • SQL Inventory Manager 2.0 is NOT SUPPORTED on SQL Server 2012 SP2 CU7. Users attempting to connect to instances on this version of SQL Server receive a connection error. IDERA is working on a solution for this issue.

IDERA Dashboard issues

  • Anchor
    DE45646
    DE45646
    In IDERA Dashboard, the Manage Instances view under the Administration view displays both monitored and unmonitored instances instead of only monitored instances.  All users will be able to access the list of instances in the Instance Detail tab under IDERA Dashboard; however, only users with specific Dashboard access will be able to see the instance details.  In SQL Inventory Manager, the Managed tab under the Instances view correctly displays only monitored instances.

Discovery issues

  • Anchor
    DE45688
    DE45688
    Scanning cross-domains using multiple accounts/credentials will not yield any discovered instances even if one of the supplied credentials in the multiple accounts setting is correct for that domain.  At this time, multiple accounts/credentials only work for the same domain. For example, in your environment, SQL Inventory Manager 2.0 is installed on domain A and you request a scan of domain B.  Even when using credentials that are included in the multiple credentials list, SQL Inventory Manager does not return results that include data from any outside domain. As an alternate, you can run the specific domain scan using specific Windows user or SIM service account (under the domain setting).

  • Anchor
    DE45787
    DE45787
    Discovery Status displaying incorrect value for scans other than SQL Server Resolution Services. When you run a scan using method other than SQL Server Resolution Services, it will run and scan and discover instances using the selected method.  However, the discovery status log will have an incorrect log referencing SQL Server Resolution Services.

  • Anchor
    DE45712
    DE45712
    When using the Setup Wizard to manage discovery, the IP Address Ranges and Domain Run Scan Now option is disabled even though an IP address or domain is selected.  The workaround is to uncheck and then recheck those options.

  • Anchor
    DE45719
    DE45719
    In order to connect to a named instance on Amazon RDS, use the following format:
    machinename\instancename,port

Monitoring issues

  • Anchor
    DE45724
    DE45724
    In environments with a large number of monitored instances, the Health Check Recommendations are not immediately updated when you decommission and recommission databases.  There will be a slight delay for the health check recommendations to refresh.

  • Anchor
    DE45713
    DE45713
    When using Internet Explorer, the Comments in the Database Details window are too light to read.

...

IDERA WebsiteProductsPurchaseSupportCommunityAbout UsResources Legal