Can't find what you're looking for? Access our previous PDF-based library.
3 min read
Published Aug 07, 2026Issue Summary
After migrating Lepide Auditor to a new server or upgrading to 26.1, the web console loads and is accessible but fails to generate any reports. All reports return the following error - “Audit database cannot be accessed….” despite audit data being present and the Main Console working correctly.
This issue is specific to post-migration or upgrade scenarios where the new server has not had the required Microsoft ODBC driver installed. The main console and core auditing are not affected — only the web console report generation fails.
Observations
The Web Console opens and login works correctly
All report sections return error - “Audit database cannot be accessed….”
The Main Console is working fine — reports generate correctly from there
The Issue started immediately after migrating Lepide to a new server or upgrading to 26.1.
Re-entering the credentials or restarting the web console service does not resolve the issue
Root Cause
The Lepide web console uses Microsoft OBDC driver 17 to generate the reports.
IMPORTANT-
To confirm if this issue is due to the Microsoft OBDC driver:
Open the php_errors file located on the Path: Lepide Data Security Platform\LDSP Web Console\logs
Check for the error of the Microsoft OBDC driver as shown in the screenshot below.
Resolution — Install the Microsoft ODBC Driver on the New Server
Step 1 – Download the Microsoft ODBC Driver
Download the Microsoft ODBC Driver from the official Microsoft website. If the Lepide server does not have internet access, download it from a machine that does and transfer the file to the server.
Official download: Download Microsoft ODBC Driver 17 for SQL Server (x64)
Step 2 – Install the Microsoft ODBC Driver on the Lepide Server
Run the installer on the Lepide server and complete the installation with default settings.
Step 3 – Restart the Lepide Server
After the ODBC driver is installed, restart the Lepide Server.
Step 4 – Verify Web Console Report Generation
After restart wait for approx. 2-3 hours as it sometimes takes time to connect in backend.
Next, generate a report to confirm it is now working:
Log in to the web console
Navigate to any report section (e.g., AD Changes, File Server, CPA Permission Scan)
Click Generate Report
Confirm data is returned correctly
Status
✅ Resolved — Installing the Microsoft ODBC driver fully restored the report generation in the Web Console.