Page History

IDERA strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact IDERA Product Support (www.idera.com/support).

3.3.2 Known issues

...

4.4 Known issues

• Anchor
  SQLSECU-26632926 SQLSECU-2663

  Exporting reports to PDF may generate blank spaces in the document.  AnchorSQLSECU-2664SQLSECU-2664The export policy process may change the number of security checks enabled for each policy. AnchorSQLSECU-2666SQLSECU-2666Importing policies may display the following error: "This security check requires at least one criterion". AnchorSQLSECU-2676SQLSECU-2676Circular dependency in database user groups causes a "maximum recursion" error message while generating the Database Roles report. AnchorSQLSECU-2679SQLSECU-2679SQL 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.

  2926

  When the server is moved from one policy to another, the Schedule settings are not updated to the new policy schedule. This issue can be solved by manually editing the server or policy schedule AnchorSQLSECU-2688SQLSECU-2688The "SQL Mail Or Database Mail Enabled" security check is validated only against SQL Server 2005 and lower. AnchorSQLSECU-2622SQLSECU-2622 AnchorSQLSECU-2689SQLSECU-2689 AnchorSQLSECU-2678SQLSECU-2678The User Permissions report for specific databases may generate a timeout error. Consider increasing the SQL Command Timeout to prevent the timeout errors.

• Anchor
  SQLSECU-27082935 SQLSECU-27082935

  SQL Secure displays an error message when a 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.

Image Removed

...

3.3.1 Known issues

General

• AnchorSQLSECU-2622SQLSECU-2622The User Permission Report for specific databases may generate timeout error. Increase the SQL Command Timeout from default to fix the problem. AnchorSQLSECU-2544SQLSECU-2544The 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. AnchorSQLSECU-2486SQLSECU-2486The Snapshot Comparison Report is not showing server role changes. AnchorSQLSECU-723SQLSECU-723The User Permission Report is missing some information when exporting in Excel files4.4 is unable to take snapshots from Azure Databases instances.

...