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).
3.3.2 Known issues
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.Exporting reports to PDF may generate blank spaces in the document.
The uninstall export policy process may not completely remove the SQL Secure folder in the Program files but user can manually remove it after uninstall process completes.
|Anchor||SQLSECU-2083||SQLSECU-2083The Snapshot Data Collection process for Windows Server 2016 is showing some incorrect warningschange the number of security checks enabled for each policy.|
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 MachinesImporting policies may display the following error: "This security check requires at least one criterion".|
Some 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 criteria.Circular dependency in database user groups causes a "maximum recursion" error message while generating the Database Roles report.
- 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 instancesSQL Secure counts up decommissioned servers as licensed servers, which may affect auditing of the registered servers if licenses are insufficient. Consider removing the decommissioned servers as a workaround to this issue.|
- The "SQL Mail Or Database Mail Enabled" security check is validated only against SQL Server 2005 and lower.
- 20002000The repository grooming job does not delete snapshots which are in an Error state. Snapshots in an OK or Warning state are appropriately deleted.13311331Clicking Technical Support Site on the IDERA SQL Secure Quick Start window redirects to an error page.13291329SMTP 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. The User Permissions report for specific databases may generate a timeout error. Consider increasing the SQL Command Timeout to prevent the timeout errors.|
- 20472047IDERA SQL Secure displays an incomplete error message if when 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.
|Anchor||SQLSECU-2038||SQLSECU-2038When changes occur between snapshots, IDERA SQL Secure displays the change information only in the Difference column of the Snapshot Comparison window and all other columns are blank.|
|Anchor||SQLSECU-1868||SQLSECU-1868Clicking the Hide and Notify when Complete button while a snapshot is in progress will hide the snapshot progress screen, but no notification is sent when the snapshot does complete.|
|Anchor||SQLSECU-1570||SQLSECU-1570Taking a snapshot of an Azure SQL Database from an on-premises installation of SQL Secure may take an extended length of time. This time is decreased when the snapshot is taken from an Azure VM installation of SQL Secure.|
|Anchor||SQLSECU-2066||SQLSECU-2066In the Snapshot Comparison, the difference is mentioned in reverse order. For example, "Changed from [DescriptionOld] to [DescriptionNew]" is incorrectly displayed as, "Changed from [DescriptionNew] to [DescriptionOld]."|
|Anchor||SQLSECU-1989||SQLSECU-1989If a user deletes a snapshot while it is running, and then tries to take another snapshot soon after, SQL Secure may show an error message. user with Audit Data User permissions launches the console. To fix this error message, consider granting explicit "Select" permissions to the user on the SQLSecure repository database as shown in the image below.|
- When launching the application with the "Run as Administrator" option, the UAC (User Account Control) prompt shows "Unknown" for the Publisher information.
3.3.1 Known issues
- The User Permission Report for specific databases may generate timeout error. Increase the SQL Command Timeout from default to fix the problem.
- The CIS for SQL Server 2016 policy 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.
- The Snapshot Comparison Report is not showing server role changes.
- The User Permission Report is missing some information when exporting in Excel files.
|Scroll PDF Exporter Ignore|
SQL Secure sees who has access to what and how permissions are granted in SQL Server.