Can I see who locked the batch and admin release the lock ?

More than once in recent history I have a user reporting they cannot post a batch because it is locked by "another user"

Error

Description: Batch ##### is currently locked by another user. You will not be able to set it's status to Ready to Post until everyone has left it.

Source: 12:42:04 - A/P Payment Batch List

I know nothing about Sage administration and I haven't found anything suggesting there is something I can do about this beyond a comment eluding to it 

You can't in version 2012, you need 2014 or higher.

https://www.tek-tips.com/viewthread.cfm?qid=1759142

So I can confirm that the user in question, who blames themselves for the lock, logged off the application already. Which makes me think its someone else that has the batch opened somewhere. I looked for open transactions on the DB but that netted nothing. The only thing I can think to do is force all users out of the program which feels extreme. How to I figure out who has a lock on a particular batch.  

Version: 2018 (300 Premium) (Build 40) (Product Update 4)

Parents Reply Children
  • 0 in reply to Jay Converse Acumen

    So that will show me the users that have A/P Payment Batch List screen open? Not necessarily who what the specific batch open. However this will narrow down the list of suspects. Will see about logging those specific users off or asking them if they have that batch open. 

  • 0 in reply to Jay Converse Acumen

    This means the only way to unlock a batch is too log users off the system? We tried to get all users out of that screen but the error still persists. Now we are going to try to  kick all users out of the system. 

  • 0 in reply to Matt Cameron

    If you get stuck and want to find out if there are still users actually accessing AP screens, RDP into the App/File server -> goto Share and Storage Managements -> Shares -> select your Sage share and select Open Files.  This will show all the paths users are accessing including any users who have application files open in A/P.  If you have third-party add-on's such as Orchid DML, also check those users have exited the Orchid app from the Task Tray.  Finally if you have web users you can stop the App Pool for Sage 300 related websites.  Good Luck...Cheers Tim