✕
×

Auditing Database Cannot Be Accessed in AD State Reports

SM
By Sarah Marshall time 1 min read time Published Jul 13, 2026

Table of Contents

  1. 1.Issue
  2. 2.Cause
  3. 3.Resolution
  4. 4.Outcome

Issue

  • Users encounter an error stating that the auditing database cannot be accessed while generating AD State Reports in Lepide Data Security Platform.

Cause

This issue typically occurs due to:

  • Missing or incorrectly configured Primary Database

  • Insufficient SQL permissions for the database

  • AD scan not completing successfully due to database access issues

Resolution

Follow the steps below to resolve the issue:

Step 1: Verify Primary Database Configuration

  • Open Lepide Data Security Platform.

  • Navigate to:
    Settings → Current Permission Scan Settings

  • Ensure that a Primary Database is properly configured.

Step 2: Re-run AD Scan

  • After confirming the primary database, initiate a fresh AD scan.

  • Check if the scan completes successfully.

Step 3: Troubleshoot Scan Issues

If the scan is:

  • Stuck at “In Progress”, or

  • Failing to complete

Then verify the database roles in SQL Server.

Step 4: Check SQL Database Roles

For the primary database (for example LepideCPA DB_march2026):

  • If the database does NOT exist in SQL Server:

    • Assign the DB Creator role to the Lepide service account.

  • If the database EXISTS in SQL Server:

    • Assign the DB Owner (db_owner) role to the Lepide service account.

Outcome

Once the appropriate permissions are assigned:

  • The AD scan completes successfully

  • AD State Reports start generating without errors