You are viewing limited content. For full access, please sign in.

Question

Question

Audit trail problem resulting in 9237 error for end users

asked on August 11, 2015

We keep getting a "could not enable audit log" error. Does anyone else have any experience with this or know how to fix it?

0 0

Answer

APPROVED ANSWER
replied on August 11, 2015

What's the exact version of the Laserfiche Server being used?

Make sure that the Laserfiche Server service account has read/write permissions to the Audit Log path (path listed in the registry for the AuditLog dword under HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\Engine\8.0\Repositories\[Repository_Name]).

If the path is valid and the Laserfiche Server service account has the necessary rights, then navigate to the path and backup the [Repository_Name].log file. Then delete that file from the AUDIT folder. Restart the Laserfiche Server service and see if it starts up properly and if users can log into the repository.

0 0
replied on April 18, 2017

I know this is an old post, but I encountered this issue today and your suggestion fixed my problem. Thanks.

0 0
replied on August 4, 2017 Show version history

 

Sorry, I'm not an expert, as I check those permissions Can you be more explicit please

This error shows

Código de error: 9237
Mensaje del error: No se pudo habilitar el registro de auditoría. [9237]

------------ Detalles técnicos: ------------

LFSO:
    Pila de llamadas: (Exception)
        ProcessResponseHeaders
        InternalDoLogin
        LFSession::Login
        CLFConnection::Create
    Detalles adicionales:
        HRESULT: 0xc0042415 (ProcessResponseHeaders, LFSession.cpp:4892)
         (LFSO/10.1.0.209)
LF.exe (10.1.1.254):
    Pila de llamadas: (Exception)
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginDialog::LoginToServer
    Pila de llamadas: (Current)
        CLoginDialog::LoginToServer
        CLoginDialog::LoginToServer
    Detalles adicionales:
        Exception: 0x80042415 [9237] (No se pudo habilitar el registro de auditoría.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:796)
    Call History:
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)

 

En visor de eventos de windows

 

Se ha encontrado un error al ejecutar instrucción de base de datos en auditoría.  Mensaje: [Microsoft][SQL Server Native Client 10.0][SQL Server]El nombre de objeto 'auditlogs' no es válido.; Instrucción SQL: 'select log_state from auditlogs where log_uuid = :uuid<char[36]>'; Variable SQL: ''; Estado SQL: 42S02.

0 0
replied on August 4, 2017

Hi Alfonso,

The issue you're running into is a bit different. From the support case that was opened for your issue, it was seen that the repository database had been manually modified and the auditlogs table had been dropped from the database. Please note that manual database modification is not supported.

Moving forward, please restore a backup of the repository database prior to the dropping of the auditlogs table.

Regards

1 0
replied on August 7, 2017

Hi Alexander.
good day.

We do not have a database backup
Can you help me with the query to generate that table?
Please

0 0
replied on August 7, 2017

They query to create the auditlogs table and associated indexes was provided through the support case.

1 0
replied on August 7, 2017

Many thanks for the support Alex

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.