This could be the result of any of the following:
- LepideAuditor Suite Service is not running
- The selected user does not have the sufficient rights to run the service or to add the domain, or its rights have been removed
- Auditing is not enabled at the domain
- The login credentials of the selected user (for running the service or for adding the domain) are incorrect
- The selected user does not have the sufficient rights to create the database in SQL Server.
- The selected user or account, for running the service, does not have a SQL login with “sysadmin” role.
- “Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings” is enabled.
Check whether LepideAuditor Suite Service is running or not. Select any of the following users to run the service.
- A local system administrator
- A member of Domain Admins Group
- Manage Service Account object
Verify the login credentials of the user with which you are running the service. The password should be blank in the case of a Managed Service Account object. LepideAuditor Suite Service should always be running.
A SQL login for the user or account selected to run the service should exist with “sysadmin” role.
The selected user to add the domain should be a member of the following groups:
- Domain Admins
- Group Policy Creator Owners
- Enterprise Admins
- Schema Admins
Please verify the login credentials of the user that you are using to add the domain.
Auditing should be enabled at the domain. While adding the domain, you should enable the auditing at the domain using the wizard. If the auditing cannot be enabled automatically, then you have to enable it manually. Please refer to the guide to enable auditing manually to know the steps in detail.
The provided user for creating or accessing the database for auditing logs should be assigned the “sysadmin” role in the SQL Server.
If you are using "Windows Authentication", then a login with Windows Authentication and “sysadmin" role, for the user with which you are currently logged in at the system, should exist in SQL Server.
Perform the following steps to disable a Group Policy.
- Access “Group Policy Management Console.”
- Edit Default Domain Controllers policy. It opens “Group Policy Management Editor” console.
- Go to "Computer Configuration" → "Policies" → "Windows Settings" → "Security Settings" → "Local Policies" → "Security Options."
- Double click "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" to access its properties.
- Please make sure this policy is set to "Not Defined", i.e. "Define this policy setting" should remain unchecked always. Uncheck "Define this policy setting", if it is checked.