Pau Lo
asked on
could not update; currently locked
We have 2 users of an access 2010 application who get an error ''could not update; currently locked'. I have tracked down the row in the table that these forms are accessing and can see no issues at all, e.g. signs of corruption. Is there anything else that can be done. There are a few forms that show/update date in this particular row, unsure really what may cause this, but as its affecting multiple users each with their own FE the common denominator being that row, what can be done.
If I connect to the backend of the system and try and manually edit a single column in the record it gives the same error.
If I connect to the backend of the system and try and manually edit a single column in the record it gives the same error.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
<<Yes we don't have admin rights over the server,>>
Don't think you'll be able to clear the lock without admin rights. You need access to computer management:
and close the file.
This only works though if the user is a network user (sounds like it is). But if this is a terminal services server, then the access is local. For that, you need to use Process Monitor to find the handle for the file and close it manually.
Jim.
Don't think you'll be able to clear the lock without admin rights. You need access to computer management:
and close the file.
This only works though if the user is a network user (sounds like it is). But if this is a terminal services server, then the access is local. For that, you need to use Process Monitor to find the handle for the file and close it manually.
Jim.
ASKER
I'll speak to the server team then. But your suspicion is the cause of the error is a lock I presume.
With everyone out of the app, the .LDB file should disappear.
If it's still there and you cannot delete it, then a lock is still being held.
Jim.
If it's still there and you cannot delete it, then a lock is still being held.
Jim.
ASKER
Trying to track it down now. It would be a network user. It wont be an RDP session, we do have a citrix access gateway but it logs them onto a citrix server. Nobody bar IT access the file server via RDP.
ASKER
Turned out someone connected to the system via our VPN which crashed and for whatever reason access did not release the lock. Once they re-established a connection again to the file again via VPN it all worked again and the record could be amended.
That will do it. With a JET/ACE backend, all the db processing is carried out on the client side. The server only acts as a file sharing device. So any abnormal disconnect is a problem.
Any remote users you have should be setup with RDP.
Jim.
Any remote users you have should be setup with RDP.
Jim.
ASKER