/
Recurring Journal - Lock request time out period exceeded

Recurring Journal - Lock request time out period exceeded

Description of Issue
  • Unable to Generate Journals from Recurring Journal due to system lock
  • Error inserting gljetrnd - status: -6372 [ISAM -50000]
    Lock request time out period exceeded
    System Log Id: #
  • System Log Message: Insert 860
Context
  • Recurring Journals
  • System Locks
  • Data Integrity
Cause

Recurring Journals are trying to access a resource in Munis that is in use by another process

Additional Information
  • Scope of system lock could be well beyond just Recurring Journals
  • Once resolved ensure all impacted users confirm they are back to normal if not troubleshoot specific issue normally





Related content

View Database Locks
View Database Locks
Read with this
General Ledger Journal Lock
General Ledger Journal Lock
More like this
General Journal Entry Proof error Unknown error during Update -6372 ISAM -50000
General Journal Entry Proof error Unknown error during Update -6372 ISAM -50000
More like this
Release failed error in General Journal Entry
Release failed error in General Journal Entry
More like this
Import Journals - Lock request time out period exceeded
Import Journals - Lock request time out period exceeded
More like this
Munis glcjeent Could not add new DTDF detail record -6372 When Releasing a Journal Entry
Munis glcjeent Could not add new DTDF detail record -6372 When Releasing a Journal Entry
More like this