Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.1 Known issues

  • 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-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

  • 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.
  • 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-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 check.

...