IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known IDERA SQL Compliance Manager issues are described in this section. If you need further assistance with any issue, please contact
| Newtablink |
|---|
| alias | Support |
|---|
| url | https://www.idera.com/support/supportplans |
|---|
|
.
Known issues in version 5.
...
7
General Issues
- 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.
- When users run the SQLcomplianceClusterSetup.exe to upgrade agent service deployment to 5.6.1, the cluster setup installation does not prompt user to agree to upgrade and instead it performs a fresh installation.
- 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.
In order to register the databases on the Secondary nodes, users have to:
- Fail over the Availability Group onto the Secondary node, in order to get access to the list of databases.
- Register the databases on the Secondary node
- Fail over the AG back to the Primary node.
Known issues in version 5.6.1
...
- (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 installation is complete, relaunch the SQL CM desktop console and run the report.
To download the Report Viewer 2010 controls program follow link below:
| Newtab2 |
|---|
| alias | Report Viewer 2010 Controls |
|---|
| url | https://www.microsoft.com/en-us/download/details.aspx?id=6442 |
|---|
|
- In SQL Compliance Manager version 5.6.1 the Row count functionality may show as “Not Applicable”. The issue occurs when you execute 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
Users can increase the time of collection (default is set to 60 seconds) to capture Row count correctly.
- 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.
- 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.
Known issues in version 5.6
General issues
- (Fixed in version 5.6.1) Import Database settings with DML/SELECT filters, flips import settings. When users import database audit settings and apply those settings to multiple databases, the imported settings apply only to some databases. If user imports and applies the audit settings to the same databases again, the configuration settings get flipped, applying the import settings to the databases it did not apply to before while deleting the settings from the ones it previously applied them to.
- (Fixed in version 5.6.1) Invalid stored procedures call to sp_SQLcompliance_AuditXE. A message about an invalid stored procedure appears in the SQL Server Logs; "Could not find stored procedure master.dbo.sp_SQLcompliance_AuditXE". The error message appears because no stored procedure with the name "master.dob.sp_SQLcompliance_AuditXE" exists.
- (Fixed in version 5.7) SQL Compliance Manager Object Activity Report renders all data on a single page. When the Object Activity Report is run, the report displays all the collected data in a single page.
- (Fixed in version 5.6.1) SQL SQL Compliance Manager traces are getting collected on the Passive nodes of an Availability Group. When a primary node becomes a secondary node, the Stored Procedure does not get disabled for the secondary node and the trace files keep gathering. This causes an accumulation of trace files on the secondary node.
...
- (Fixed in version 5.6) Installation or upgrade of SQL Server 2012 native client may cause the system to reboot. When installing or upgrading the version of the native client, once the process is complete, a system reboot occurs without previous warning.
- IDERA Dashboard 3.0.3 and later does not support SQL Server 2005 SP1. Users should not attempt to install SQL Compliance Manager with IDERA Dashboard 3.0.3 and later on a SQL Server 2005 SP1 as that version of SQL Server is not supported by IDERA Dashboard.
General issues
- Case-sensitivity required when specifying the Repository database name. When specifying the location and name of your Repository database, SQL Compliance Manager requires that you use proper capitalization.
- IDERA SQL Compliance Manager does not capture Linked Server Trace Events for SQL Server 2005. Linked server events are not present in the trace files for SQL Server 2005, therefore linked server events are not captured in IDERA SQL Compliance Manager and no alerts will trigger. Microsoft has ended extended support for this version.
- (Fixed in version 5.6) Create/Drop index events recorded as “Alter User Table” event. SQL Compliance Manager records Create/Drop index events as “Alter User Table” events.
- (Fixed in version 5.6) IDERA SQL Compliance Manager is not loading events accessed through a View. SQL Compliance Manager does not display Sensitive Column events when accessed from a view. To access the information using views gather and filter out all SELECT statements. Note that this action will cause extra collection.
...
Known issues in version 5.5
General issues
- ( Fixed in version 5.5.1 ) When users try to upgrade from SQL Compliance Manager 4.5 to 5.5, trace files are not processed. If you currently work with SQL Compliance Manager 4.5, before upgrading stop the Collection Service, Agent Service, and disable auditing to stop trace file processing, then proceed to upgrade to SQL Compliance Manager 5.5, and configure and enable auditing. Upon upgrading to SQL Compliance 5.5, users must upgrade all agents to a 5.x version first. For more information, see Upgrade to this build.
| Anchor |
|---|
| SQLCM-5339/5021/5243/5013/5340/5343 |
|---|
| SQLCM-5339/5021/5243/5013/5340/5343 |
|---|
|
( Fixed in version 5.5.1 ) The SQL Compliance Manager Collection Server is not processing trace files, or processing them slowly, causing backlog files to get accumulated in the Collection Trace Directory in large transactional databases.The workaround for this issue is to increase the tamper detection interval and the Collection interval.
- ( Fixed in version 5.5.1 ) IDERA SQL Compliance Manager installation fails if TLS 1.0 is disabled and if SQL Server 2012 Native Client is not available. IDERA SQL Compliance Manager 5.5 installs SQL Server 2012 native client (version 11.0.2100.60) which does not support TLS 1.2 enabled as per Microsoft.
https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server
Users with SQL Server versions prior to SQL Server 2012 R2 SP3 need to enable TLS 1.0 or update the native client to the supported version (11.4.7001.0) following the link below:
https://www.microsoft.com/en-us/download/details.aspx?id=50402
| Anchor |
|---|
| SQLCM-5218/5222/5328 |
|---|
| SQLCM-5218/5222/5328 |
|---|
|
( Fixed in version 5.5.1 ) SQL Compliance Manager does not process trace files generated by an older Agent after upgrading versions of the Collection Server and the Agent.
...
Known issues in version 5.4.x
General issues
- ( Fixed in version 5.5.1 ) SQL Compliance Manager does not accept user names longer than 20 characters and does not support some special characters for the user password, such as £.
- Removing databases using the Administration pane in the Management Console does not work. You can remove databases using the Explorer Activity panel.
- ( Fixed in version 5.5 ) During an Agent-only installation, if you accept the default destination path for SQL Compliance Manager, and then select a different destination drive and use a sub-folder in the Agent Trace Directory dialog box, the installer does not create the Agent Trace Directory during installation. If this issue occurs, reinstall the Agent specifying a folder instead of a sub-folder as the destination path or use the default path specified in the installer.
...