Journal Error - Locked Database

Support
1

We received this error today:

Failed to write journal events into the embedded journal database. Journal events will be accumulated in memory until the embedded journal database is available again. ‘database is locked database is locked’.

Should we be concerned or is there a quick remedy?

Thanks.

Casey

1 Like
2

Seems to have resolved itself.

1 Like
3

Let us know if the error message appears again.

4

Hi.
Have you opened journal database file in any external application?
Could this be the cause of the error?

5

All,

This happened again this morning.

From my knowledge, we have not opened the journal database file.

6

I have noticed this happening as well.

7

@Tanner.Hart and @Shaheed_Fazal, are you using an Internal or external journal? In the latter case, which database you are using?

8

The error can appear when some application is locking or interfering with the journal database file: C:\ProgramData\EasyMorph Server\journal.db. Possible causes and solutions:

  • Locked by antivirus software -> Add the folder/file to the list of exclusions of the antivirus software
  • The file is synchronized by a backup/sync software -> don't use real-time synchronization
  • The file is located on a shared drive -> don't use a shared drive for Server system files and folders

Usually, the error resolves itself. As soon as the journal database file is unlocked, the Server writes accumulated in memory events in the journal, so nothing is lost unless the Server was reloaded before the journal was unlocked.