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.4 Known issues
The User Permission Report for specific databases may generate timeout error. Increase the SQL Command Timeout from default to fix the problemExporting reports to PDF may generate blank spaces within the document.
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 checksexport policy process may change the number of security checks enabled for each policy.
- Importing policies may display the following error: "This security check requires at least one criterion".
- Circular dependency in database user groups causes a "maximum recursion" error message while generating the Database Roles report.
- 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.
The Snapshot Comparison Report is not showing server role changesWhen launching the application with the "Run as Administrator" option, the UAC (User Account Control) prompt shows "Unknown" for the Publisher information.
The User Permission Report is missing some information when exporting in Excel filesA user without login is identified as an orphan user. As a workaround, when these users are discovered and manually validated as such, they should be added into the exclusion filter of the Orphaned Users security check.
|Scroll PDF Exporter Ignore|