I’m testing repository auditing on a non-persistent test VM running Laserfiche Content Repository Server 12.0.4.433 with Advanced Audit Trail licensed.
I created two test repositories and enabled auditing. After selecting Auditing → Rollover Logs → Action → Perform Rollover, the rollover files appeared, but I couldn’t find the configured active audit log.
For one repository, the active path is:
<RepositoryFolder>\AUDIT\<RepositoryName>.log
That folder currently contains two rollover files:
- <RepositoryName>-20261115-1.log — 1,524 bytes
- <RepositoryName>-20261115-2.log — 2,416 bytes
I created the second file by manually performing another rollover. Its reported date range includes activity after the first rollover, so it looks like later activity was retained somewhere. I haven’t decoded the binary logs to confirm individual events.
Here’s what I’ve checked:
- The active log path and rollover directory point to the expected folder.
- Automatic rollover is set to 50 MB, with no maximum age and compression turned off. Both rollovers were manual.
- ADMIN’s effective audit settings, inherited through group membership, include successful Entry and Session events.
- I created and renamed test documents after rollover.
- I checked the folder using both Explorer and PowerShell with Get-ChildItem -Force.
- I checked again after leaving it idle and after signing out of the repository normally.
- Laserfiche Server is running as LocalSystem, and SYSTEM has Full Control on the audit folder.
- I didn’t find matching audit-related warnings or errors in the Content Repository Admin or Windows Application logs during the period checked.
I also used Process Monitor to capture a test document rename, then another rename followed by signing out of the repository. I checked both lfs.exe and other processes accessing the repository folder, including System.
The trace showed Explorer checking the folder and some search-index activity, but I didn’t see an attempt to create or write the active audit log. There also weren’t any access-denied or sharing-violation results for the audit path.
I saved a filtered PML with 180 events. I haven’t attached it because it contains internal paths and process details.
I haven’t restarted services, changed audit settings, or deleted any audit files during these checks.
Is this expected behavior after a manual rollover? Does Server 12 buffer audit events or temporarily store them somewhere else before creating the active file? What normally triggers that file to appear?
If this isn’t expected, are there any known issues with 12.0.4.433, or other read-only checks I should try before changing anything or restarting the service?