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).
...
4.4
...
Known issues
Exporting reports to PDF may generate blank spaces within the document.Anchor SQLSECU-26632926 SQLSECU-2663 Anchor SQLSECU-2664 SQLSECU-2664 The export policy process may change the number of security checks enabled for each policy.Anchor SQLSECU-2666 SQLSECU-2666 Importing policies may display the following error: "This security check requires at least one criterion".Anchor SQLSECU-2708 SQLSECU-2708 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.Anchor SQLSECU-2707 SQLSECU-2707 Anchor SQLSECU-2661 SQLSECU-2661 When launching the application with the "Run as Administrator" option, the UAC (User Account Control) prompt shows "Unknown" for the Publisher information.Anchor SQLSECU-2772 SQLSECU-2772 Renaming the sa login in a SQL Server instance generates a false warning risk level in the 'sa account is not disabled' check.
3.4 Known issues
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 schedule2926 Anchor SQLSECU-2663 SQLSECU-2663 Exporting reports to PDF may generate blank spaces within the document.Anchor SQLSECU-2664 SQLSECU-2664 The export policy process may change the number of security checks enabled for each policy.Anchor SQLSECU-2666 SQLSECU-2666 Importing policies may display the following error: "This security check requires at least one criterion".Anchor SQLSECU-2676 SQLSECU-2676 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.Anchor SQLSECU-27082935 SQLSECU-27082935 Anchor SQLSECU-2707 SQLSECU-2707 Anchor SQLSECU-2661 SQLSECU-2661 When launching the application with the "Run as Administrator" option, the UAC (User Account Control) prompt shows "Unknown" for the Publisher information.Anchor SQLSECU-2735 SQLSECU-2735 A 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 check4.4 is unable to take snapshots from Azure Databases instances.
...