IDERA strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact Support (www.idera.com/support).
SQL Secure only recognizes the first license key added. If the first license key gets expired the product will ask for a new valid license key, even if the product has another valid license keys registered. You can remove the old license key by deleting it and this way it will recognize the valid license key. You can contact your IDERA Account Team for an updated license.
|Anchor||SQLSECU-2151||SQLSECU-2151The uninstall process may not completely remove the SQL Secure folder in the Program files but user can manually remove it after uninstall process completesThe User Permission Report for specific databases may generate timeout error. Increase the SQL Command Timeout from default to fix the problem.|
The Snapshot Data Collection process for Windows CIS for SQL Server 2016 is showing some incorrect warnings.
|Anchor||SQLSECU-2064||SQLSECU-2064 SQl Secure is not able to add new servers to Server Group Tags.|
|Anchor||SQLSECU-2037||SQLSECU-2037The Show Risk Only option in the Risk Assessment Report does not make any difference in the report list.|
|Anchor||SQLSECU-2244||SQLSECU-2244The Unauthorized Account Check Security Check is not listing the proper permissions for SQL Server 2008 and reports this message "Unauthorized member found: 'public' (VIEW ANY COLUMN ENCRYPTION KEY DEFINITION, VIEW ANY COLUMN MASTER KEY DEFINITION)"|
|Anchor||SQLSECU-2259||SQLSECU-2259SQL Server Installation Directories on system Drive Security check is failing in Azure Virtual Machines.|
|Anchor||SQLSECU-2338||SQLSECU-2338Some older security template requires a user input for the security checks but SQL Secure is allowing user to save these polices without inputting criteria. It can result in a risk finding in the report. When this happens the user can always go back in and edit the policy to update the criteriapolicy is not listing the 3.10 (Ensure Windows local groups are not SQL Logins) and the 3.11 (Ensure the public rolw in the msdb databases is not granted access to SQl Agent proxies) security checks.|
- 20582058Not all SSRS reports are able to export to CSV format. The workaround is to export to Excel and open the report in Excel and re-save as csv format.
Previous known issues
|Anchor||SQLSECU-2053||SQLSECU-2053Database roles and members are not included in the Report Card Details list on registered SQL Server 2000 instancesThe Snapshot Comparison Report is not showing server role changes. |
- 20002000The repository grooming job does not delete snapshots which are in an Error state. Snapshots in an OK or Warning state are appropriately deleted.
|Anchor||SQLSECU-1331||SQLSECU-1331Clicking Technical Support Site on the IDERA SQL Secure Quick Start window redirects to an error page.|
|Anchor||SQLSECU-1329||SQLSECU-1329SMTP email configuration may not work for a secure mail server.|
|Anchor||SQLSECU-2065||SQLSECU-2065The Register SQL Server error message regarding supported versions needs updating to include SQL Server 2016.|
|Anchor||SQLSECU-2058||SQLSECU-2058SSRS reports do not extract to a .csv file.|
|Anchor||SQLSECU-2049||SQLSECU-2049The file type of an exported policy is not selected as .xml by default. In addition, when importing a policy, the file must be manually selected by selecting All Files. |
|Anchor||SQLSECU-2047||SQLSECU-2047IDERA SQL Secure displays an incomplete error message if a specific user/role is given GRANT and/or WITHGRANT permissions by one grantor, and DENY permission by another grantor. The error message does not include identifying detail about the conflicting user or role.|
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal
- The User Permission Report is missing some information when exporting in Excel files.
|Scroll PDF Exporter Ignore|