Versions Compared

Key

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

1 UI Warning

Failed to load file permissions for target SQL Server [UI]

Failed to load file permissions for '{0}' audit folder [UI]

Failed to load file permissions for SQL Services on target SQL Server [UI]

Type of exception

SeSecurityPrivilage

Cause

The account under which Sql Secure collector is running does not have enough permissions in Active Directory

Solution

In order to fix this, perform following steps:

1. Go to > Local Security Policy- > Local Policies -> User Rights Assignment on the server you are trying to install on.

2. Assign your logged in account (eg [domain]/[username]) the following rights:

-Back up files and directories

-Debug Programs

-Manage auditing and Security log

-Restore files and directories

-Take ownership of files or other objects

3. Once you have done this, logout then log back in again.

2 UI Warning

Failed to load file permissions for target SQL Server [UI]

Failed to load file permissions for '{0}' audit folder [UI]

Failed to load file permissions for SQL Services on target SQL Server [UI]

Type of exception

UnauthorizedAccessException

Cause

The path parameter specified a directory that is read-only.-or- This operation is not supported on the current platform.-or- The caller does not have the required permission.

 

Example from collector logs:

Failed to get file permissions for \\MACHINE-NAME\C$\Program Files\Microsoft SQL Server\MSSQL13.MSSQL16\MSSQL\Binn\Xtp\gen\include\hkengdef.h: System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

Solution

In order to fix this, we need to go to the sql server installation directory and make sure that the user under which Sql Secure collector is running have enough access permissions on all the folders and files inside installation directory(uncheck "Read Only" checkbox in the properties) and not Read-only access.

Image Added

2 UI Warning

We could not load/read data while processing OS objects. Please check the Activity logs of the server for the possible solutions to avoid this.

Cause

System error encountered when _LookupAccountSid() for given group SID is called.

Solution

the user is not present in that Active Directory or that Account table