We are experiencing this exact issue. I’ll be looking more in-depth to see if I can narrow it down. A cursory Google search for: sage “pt.lck” brought me to this forum post and the post you replied to about a month ago. These problems began after the upgrade to 2020 for all15 users here. Sporadic. Sometimes the backups fail as well. The backups are supposed to get everyone out, from my understanding, but it doesn’t seem to work properly. I have gone as far as total (complete) reinstall on the server, and workstations, with no luck. So there’s something else going on. Maybe it’s a simple problem, and I’m overcomplicating it but I am going to start looking into why Sage just disappears. The hint is probably in that.
I have a
PT.LCK that is owned by a different user than the user that created the
SUA00021.LCK file. I checked the user that created the
SUA00021.LCK file to see if Sage was running and it was not “visible” on the desktop. I terminated (
taskkill /f /im peachw.exe) on the workstation. Did not let go of the
SUA00021.LCK so I then had to terminate forcefully Actian (
taskkill /f /im w3dbsmgr.exe) and restart it (
net start psqlwge). Once Actian/Pervasive was restarted, the lock on the
SUA00021.LCK file was let go and as soon as I renamed it, users were able to launch Sage again.
Another Sage 50 user or workstation is accessing this company area or performing a similar company process. Please wait a moment and try again. If you believe you received this message in error, have all users exit Sage 50 and try again.— Sage 50 Accounting