Batches stuck as "in use"

We have run into an issue a few times with both AP and GL batches. The status changes and is stuck on "in use". We check that there are no users in the batch, but the status gets stuck, we can't delete it or post it. The only resolution we are able to do is have our IT department go through the back and into the database and change the status there.

Have others had this problem?

Is there a better/easier way to resolve it?

Any idea of what causes this, so we can avoid it in the future?

Parents
  • How are these batches created? Are they created from the client or imported? If the batches are created from the client, does the user who created them see any errors while they are working within the batch? If they are not, are they ending/killing the task because it appears to be frozen (Gives visual indication of "Not Responding" when clicking on the screen).
  • in reply to LouDavis
    They are created through the client. There is no indication of error or being frozen when they are in the batch. However this morning the batch changed status and was able to be posted. So it might be something internally.
Reply
  • in reply to LouDavis
    They are created through the client. There is no indication of error or being frozen when they are in the batch. However this morning the batch changed status and was able to be posted. So it might be something internally.
Children
  • in reply to DDUSSAULT
    I have found that when the person who created the batch opens it, they can work with it and post it even when it is marked in use. Are you seeing this as well? Also, is it batches created by all users or just certain users having the issue?