If you work in the system with multiple users or tend to open several screens at a time you may run into a loop of error messages as you try to add, change, or edit something in a journal. Read on to find out what the messages mean and how to get them to go away so you can continue working (and prevent them from occurring in the future).
Do the following loop of error messages look familiar to you?
If so, then what’s important is identifying which type of error (out of the two possibilities) you are receiving. To troubleshoot the cause of the error, you should click "OK" on image 1, which then brings you to image 2. From here press the highlighted arrow that is shown on image 2, which will take you to one of the following two screens that provides the reason for your session being locked.
Option 1: Record already locked by this session
When it reads “Record already locked by this session,” it tells us that you (the user) are trying to edit the same transaction twice. You essentially have locked yourself out. When you are attempting to edit a transaction that is already open, the system doesn’t know where to look.
To get yourself unlocked, you must log out completely by using the start menu at the bottom left hand corner. This is the only way to log off of the server completely (see our previous blog post “How to Properly Log Off the PROCAS Server, and the Benefits of Doing it Properly”). Hitting either of the “X’s” at the top of the screen will not work, as it just disconnects you for the time being. Once you get logged back in, the transaction you were editing may or may not have saved your changes. We have found in most cases that the journal is left how it was, and it may be sitting out of balance.
Option 2: Record already locked by user
If it reads “File is locked” then this tells us that a different user has the same transaction open. Line two of the message on image 4 will let you know which user is attempting to edit the same entry.
In this case, logging out wont fix the issue. To get unlocked you will need to have the user listed on the screen close down the window you are trying to access. So in this instance, I would ask “smartin,” the user listed on image 4, to close the window that is locking me up, as we both shouldn’t be editing the same entry at the same time. Once they have finished what they are doing and have closed their window, you shouldn’t have a problem accessing the journal.