Question

9237: Could not enable audit log

Laserfiche Version 9 Administration

Updated August 4, 2017

asked on January 6, 2014

We have two repositories. Both on the same LF Server and the same SQL Server. When trying to log in we were receiving a 9008 error. I updated the SQL DBMS connection information and we are now receiving the following error message "9237: Could not enable audit log". In the help documentation it doesn't give any details. We do not have Audit Trail, so I'm not sure where to go from here. Any ideas?

2 0

Answer

APPROVED ANSWER SELECTED ANSWER

replied on January 6, 2014 • Show version history

It turns out the SQL server was restarted and caused the connection problem. After restarting the Laserfiche server, the error went away.

13 0

replied on August 4, 2015

I restarted the service and that worked for me as well. Thanks

1 0

replied on November 23, 2015

We are on LF 9.2 and received the same error following a SQL server restart.

There are multiple repositories on the one LF Server, and the error only surfaced on one repository where the audit log file couldn't be reached. We chose to unregister/re-register the problematic repository rather than a restart that might disturb the other repositories. We were forced to set a new path to the Audit, Logs, and Temp folders since the server continued to say that the files were in use. This worked for us and allowed us to log back in.

2 0

replied on August 4, 2017

What steps should I follow?

you can help please

0 0

Replies

replied on January 6, 2014

Laserfiche Server 9.1.0.413. In the Application Log on the LF Server I am seeing the following errors:

Mounting repository 'SD91LFData' failed. Please ensure that the Laserfiche Server has the ability to log in to the database used by the repository and that the repository directory is accessible.

Could not enable audit log. Error: File input/output error.

The auditor encountered an error or corruption in the audit log (Failed to initialize audit log; data may be lost). Error: File input/output error.

The auditor encountered an error or corruption in the audit log (Unable to open audit log). Error: The file exists).

1 0

replied on January 6, 2014

Blake, please have your reseller open a case with Tech Support. If this repository never had auditing on, then the message is probably a red herring and something else is going on when the server tries to mount the repository.

1 0

replied on June 11, 2014

Why would users get a message that LF can't write to the audit log if they do not have audit trail?

1 0

replied on January 6, 2014

Are you running version 9.0.3 or greater? Starting with 9.0.3 if the server is unable to open the audit log it will start a new one instead of throwing an error. There might be more information in the Windows Event Viewer Application log on the server.

0 0

You are not allowed to follow up in this post.

Question

Question

9237: Could not enable audit log

Answer

Replies

Sign in to reply to this post.