Can't find what you're looking for? Access our previous PDF-based library.
5 min read
Published Jul 21, 2026Issue Summary
Lepide Auditor stops inserting audit data into the database across multiple file servers. Logs accumulate in the agent queue and are not processed.
This issue occurs in environments using Microsoft SQL Express as the database service. SQL Express has a hard 10GB per database size limit. When any individual Lepide database reaches this limit, data insertion halts immediately for that database — and if action is not taken promptly, logs continue to accumulate, further straining the server.
Observations
Data insertion failure notification appears in Lepide for one or more file servers
File server reports show no new data in reports — audit logs stop updating
Multiple file servers affected simultaneously if databases on each are near or at the size limit
Server CPU and RAM usage increases as unprocessed logs accumulate in the agent queue
Issue recurs periodically as new databases fill up over time
Root Cause
The issue is caused by two compounding factors occurring together:
Factor 1 - SQL Express 10GB Database Size Limit
Microsoft SQL Express enforces a strict 10GB maximum size per database. When a Lepide audit database reaches this limit:
All new data insertion to that database stops immediately
Lepide generates a data insertion failure notification
Audit logs from file server agents are no longer written to the database and begin queuing
SQL Express does not warn proactively as the database approaches 10GB. The insertion simply stops when the limit is hit. If the notification is missed or ignored, logs continue to accumulate silently.
Factor 2 - Insufficient Server Resources
When logs accumulate in the agent queue due to the database limit being hit, the server must hold those unprocessed logs in temporary storage. If the server has insufficient RAM (e.g., 16GB) or limited free disk space on the database drive (e.g., only 15GB free), this log accumulation causes:
High RAM usage as the backlog builds up
Disk space on the C drive filling up with temporary log files (if Lepide is installed on the C drive)
Degraded overall server performance affecting the Lepide console responsiveness and other services
How to Troubleshoot
Step 1 – Check for Data Insertion Failure Notifications
In the Lepide console, check for any data insertion failure notifications or error alerts. These will identify which file server(s) and which database(s) are affected.
Step 2 – Check Database Size in SQL Server Management Studio
Open SQL Server Management Studio (SSMS) on the Lepide server. Connect to the SQL Express instance and check the size of each Lepide database:
Right-click on the affected database > Properties > General
Check the Size field — if it is at or above 10GB, the limit has been reached
Step 3 – Check Server Resource Usage
Open Task Manager on the Lepide server and check:
• Disk space on C drive and database drive — check available free space in File Explorer
Immediate Resolution — Create a New Database
The fastest way to restore data insertion is to create a new database in Lepide and point the affected file server to it. This immediately bypasses the full database and resumes log processing.
The steps to do this are as follows:
Open the Lepide console and navigate to the affected file server configuration.
Create a new database — name it clearly with the year or a sequence number (e.g., LepideFileServer_2026_DB2) so it is easy to identify later.
Save the configuration. Data insertion will resume immediately.
Verify data is flowing by checking the file server report. New logs should appear within a few minutes.
Data insertion resumes immediately after creating a new database. All previously accumulated logs in the agent queue will begin processing automatically.
If there is a large backlog of accumulated logs, expect increased CPU and RAM usage for 1-2 days while the backlog is processed. This is normal and will stabilize once the queue is cleared.
Historical data from the old (full) database is not lost. It can be accessed via the Explore Backup option in the Lepide console — select the old database to browse historical audit records.
Long-Term Recommendations
Recommendation 1 — Monitor Database Size Regularly
Check Lepide database sizes in SSMS at least once every 1–2 weeks, especially in environments with multiple file servers and high log volumes. Do not wait for a failure notification - proactively create a new database before the 10GB limit is reached.
Recommendation 2 — Increase Server RAM
For environments with multiple file servers generating high log volumes, a minimum of 32GB RAM is recommended. Low RAM (16GB) significantly increases the risk of performance degradation when log backlogs accumulate due to database limit events.
Recommendation 3 — Increase C Drive Free Space
Ensure at least 100GB of free space is maintained on the C drive at all times (if Lepide is installed on the C drive). Temporary log files accumulate quickly during a database limit event, and a nearly-full C drive will make the situation significantly worse.
Prevention Checklist
Check all Lepide database sizes in SSMS every 1–2 weeks
Set a reminder to create a new database when any database reaches 8GB (before hitting the 10GB limit)
When you receive a data insertion failure notification - act immediately and create a new database. Do not wait.
Maintain at least 32GB RAM on the Lepide server in multi-file-server environments
Keep at least 100GB free on the C drive and Database drive at all times
Keep Lepide updated to the latest version
Plan for a SQL Express to licensed SQL Server upgrade for long-term stability
Status
Resolved - Creating a new database immediately restored data insertion. Accumulated log backlog began processing automatically.