...
| Warning |
|---|
The SQL Compliance Manager 5.0 installation kit default extraction path is the same as previous versions and may cause issues if the previous files still reside at that location. Before launching the SQL Compliance Manager 5.0 upgrade, either select a different installation location or delete the files from the following location: c:\Program Files\Idera\SQLcompliance x64 Installation Kit or c:\Program Files (x86)\Idera\SQLcompliance x86 Installation Kit
|
SQL Compliance Manager 5.
...
3 remote Agent cannot be upgraded using the Management Console or Web Console
An issue in SQL Compliance Manager 5.3 prevents users from upgrading a remote Agent using the SQL Compliance Manager Management Console or the Web Console. For more information about upgrading to this release, see Upgrade from SQL Compliance Manager 4.5 to version 5.3.
SQL Compliance Manager 5.0 and later do not support Microsoft Windows Server 2000 or the .NET 2.0 framework
Beginning with version 5.0, SQL Compliance Manager 5.0 does not support Windows Server 2000 or the .NET 2.0 framework. While SQL Compliance Manager 4.5 and prior versions continue to operate with Windows Server 2000, SQL Compliance Manager 5.0 and later require the .NET 4.0 Full framework to take advantage of the additional features. For additional information about supported versions, see the SQL Compliance Manager Software requirements.
...
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.
Known issues in version 5.3
Installation and upgrade issues
- If you change the Display Name of IDERA SQL Compliance Manager during an upgrade, the installer perceives that you want an ADDITIONAL installation of SQL Compliance Manager rather than an upgrade of the previous version. This action results in TWO SQL CM TABS and does not upgrade the product in your environment. To upgrade SQL Compliance Manager, type the name displayed on the Web Console tab for your current installation.
- IDERA SQL Compliance Manager 5
...
- .3 does not support SQLcomplianceAgent silent installation.
- The Collection Trace directory is not created when choosing a non-default path during installation. Use the default installation path to avoid this issue.
IDERA Dashboard issues
- Users who upgrade from a previous version of IDERA SQL Compliance Manager that supports the IDERA Dashboard may notice two issues with the widgets on the Dashboard Overview. First, duplicate SQLCM Environment Alerts widgets appear. Second, the Audited Instances widget may not display any data.
Enterprise Activity Report Card issues
- The Overall Activity view of the Enterprise Activity Report Card included on the Home view of the Web Console and in the Windows Console displays all events processed by the system rather than only those generated as event alerts, failed logins, privileged user activity, DDL activity, and security alerts.
Instance issues
- If you use the IDERA SQL Compliance Manager Web Console to edit existing Threshold Notifications , you may notice that the current settings are not properly displayed. They are correctly saved in the database and are simply not properly displayed in the Web Console.
- Users cannot register a new instance using the IDERA SQL Compliance Manager Web Console. This feature does work properly in the IDERA SQL Compliance Manager Windows Console.
| Anchor |
|---|
| SQLCM-3798, SQLCM-3332 |
|---|
| SQLCM-3798, SQLCM-3332 |
|---|
|
After you use the IDERA SQL Compliance Manager Windows Console to delete a SQL Server instance that includes Archived events:- an error occurs when you attempt to view your registered instances in the Web Console.
- an "Agent heartbeat was not received" event occurs on every heartbeat check.
Auditing issues
- While the IDERA SQL Compliance Manager Web Console Audit Event Filters view displays Enable or Disable in the Status column, the exported file displays only a 1 in that same column and for both statuses.
| Anchor |
|---|
| SQLCM-3640, SQLCM-3639 |
|---|
| SQLCM-3640, SQLCM-3639 |
|---|
|
After registering an AlwaysOn Availability Group server for auditing using the Listener method, IDERA Compliance Manager:- allows auditing of all databases for the Primary node, including those that are not part of the AG. Note that if the primary node changes, the non-AG databases will not be available.
- (Cluster Agent configured on nodes) returns an error after running the update query with one column of a table selected for Before and After auditing OR when you select Audit Selected Columns with all columns selected instead of checking Audit All Columns. While the data is updated in the table, no Before and After data is collected.
- If you select Custom for the Audit Collection Level and attempt to add privileged users when adding a new database for auditing, an error occurs when you click Add. To avoid this issue, add the new database without selecting any privileged users, and then go back and edit the properties for the audited database and add a privileged user.
- When adding or removing a database role for a user on SQL Server 2008 R2, the audited event does not capture the SQL statement.
- If you have two tables in the same database that have the same name but different schemas, auditing fails on those two tables.
- When Capture Transaction Status for DML Activity is enabled for auditing on the database, capturing SQL Statements will have variables instead of values.
- Some SQL Server startup/stop events may cause the integrity check to fail.
- Case-sensitive collation may prevent some trusted and privileged users from being captured.
Alerting issues
- If you use the IDERA SQL Compliance Manager Windows Console to edit an existing Alert Rule , you may notice that the current settings are not properly displayed. They are correctly saved in the database and are simply not displayed in the Windows Console. This feature does work properly in the IDERA SQL Compliance Manager Web Console.
- If you use the IDERA SQL Compliance Manager Web Console to create an Alert Rule including Sensitive Column Accessed or Column Value Changed , you may notice that the alerts are not generated when these events occur. This feature does work properly in the IDERA SQL Compliance Manager Windows Console.
- If you use the IDERA SQL Compliance Manager Web Console to create an Event or Status Alert Rule , you may notice that the alerts are generated when these events occur, but no corresponding email notifications are sent. This feature does work properly in the IDERA SQL Compliance Manager Windows Console.
Previous known issues
Users experience some AlwaysOn Availability Group issues when the listener uses any port other than the default
...
Case-sensitive SQL Server instances do not trigger a Column Value Changed alert when a column that is set up for Before-After Data auditing is changed.
Previous known issues
Net Time value not updated in recurring schedules
...
SQL Compliance Manager now includes alert messages for all alerts. If you have not defined an alert message and an alert is generated , the alert message will display raw variable information without any corresponding values. Configuring your alert messages and defining the variables to include will allow you to customize what you see in alert messages.
Adding BLOB data type to table definition prevents updates
When you change the definition of a table you are auditing to include BLOB data types, the Before-After data trigger prevents UPDATE, DELETE, and INSERT operations from modifying the table, such as through stored procedures or third-party applications. This issue is most likely to occur when you are auditing all columns in the target table.
...