Page tree

Versions Compared

Key

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

...

  • Anchor
    SQLCM-6273
    SQLCM-6273
    The installation wizard of the Agent service fails when running the audited SQL Server under the Local System account. In order to grant all required permissions successfully, run the SQLcompliance-x64.exe  installer to perform a manual agent-only installation.
  • Anchor
    SQLCM-6230
    SQLCM-6230
    (Fixed in version 5.8.1)  When performing a migration of the Collection Server, while installing the new Collection Server components, the installer raises an error message that prompts for the removal of the newly restored SQLcompliance and SQLcomplianceProcessing databases. The installer locates these databases which have been restored for the purpose of the migration, on the server instance which has been designated as the new repository database server during the installation process. Do not proceed with the removal of these databases, instead contact
    Newtablink
    aliasSupport
    urlhttps://www.idera.com/support/supportplans
     for further assistance with installation or look up the KB Article #00012649 for further instructions, in the Solutions section for the SQL Compliance Manager product in the 
    Newtablink
    aliasIDERA Customer Portal
    urlhttps://idera.secure.force.com/
    . AnchorSQLCM-6247/6223SQLCM-6247/6223(Fixed in version 5.8.1) When running the console reports and/or the newly SSRS deployed reports, the execution fails with the following syntax error: "Query execution failed for dataset 'ReportOutput'. (rsErrorExecutingCommand) Incorrect syntax near')'.

Known issues in version 5.7.1

...

General Issues

  • Anchor
    SQLCM-6247/6223
    SQLCM-6247/6223
    (Fixed in version 5.8.1) When running the console reports and/or the newly SSRS deployed reports, the execution fails with the following syntax error: "Query execution failed for dataset 'ReportOutput'. (rsErrorExecutingCommand) Incorrect syntax near')'.
  • Anchor
    SQLCM-5989
    SQLCM-5989
    (Fixed in version 5.7.1)  When users add a GMSA account as part of a group, SQL CM does not recognize it as a Trusted User. As a workaround, users need to specify the account and the group when configuring Trusted Users and update the audit settings each time a new GMSA account is added to the group.
  • Anchor
    SQLCM-6058
    SQLCM-6058
    (Fixed in version 5.7.1)  When users run the SQLcomplianceClusterSetup.exe to upgrade agent service deployment to 5.6.1, the cluster setup installation does not prompt users to agree to upgrade and instead it performs a fresh installation.
  • Anchor
    SQLCM-6128
    SQLCM-6128
    (Fixed in version 5.7.1)  When registering databases to the Primary node of an audited Availability Group, SQL Compliance Manager is not able to establish a connection with the AG databases on the Secondary nodes. Therefore, these databases do not get automatically register on the Secondary nodes.

...

  • Anchor
    SQLCM-6057
    SQLCM-6057
    (Fixed in version 5.7)  The Daily Audit Activity Statistics Report displays an error message in the SQL CM desktop console when the ReportViewer.DataVisualization component is missing. To run the report correctly, close the SQL CM desktop console and install the Report Viewer 2010 program. Once the installation is complete, relaunch the SQL CM desktop console and run the report.

To download the Report Viewer 2010 controls program follow the link below:

Newtab2
aliasReport Viewer 2010 Controls
urlhttps://www.microsoft.com/en-us/download/details.aspx?id=6442

  • Anchor
    SQLCM-6055
    SQLCM-6055
    In SQL Compliance Manager version 5.6.1 the Row count functionality may show as “Not Applicable”. The issue occurs when you execute a large query and during execution the start and the end of the SQL Statement get captured in different trace files.  Since both events are located in different trace files, SQL CM is not able to map these events and therefore displays that Row count is “Not Applicable”. Users can increase the time of collection (default is set to 60 seconds) to capture Row count correctly.
  • Anchor
    SQLCM-6012
    SQLCM-6012
    SQL Compliance Manager is currently allowing users to select the Upgrade Agent option, even if the Agent is already in latest version. Upon selection, SQL CM prompts you to upgrade the agent using the full setup program.
  • Anchor
    SQLCM-6027
    SQLCM-6027
    (Fixed in version 5.7.1)  When you configure Sensitive Column auditing without first selecting the DML or SELECT option on the Audited Activities tab, then the SQLcompliance Agent has problems creating the sp_SQLcompliance_Audit stored procedure, and auditing stops working.

...