Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / May 2007

Tip: Looking for answers? Try searching our database.

Database gets locked without information in the ldb-file

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Markus Larsson - 30 May 2007 15:58 GMT
Hi!

I’m developing and administrating a big Access system with over 40
concurrent users/Access-sessions and more than 300 tables totaling 10 GB of
data. This system has been in use for over 10 years. We are using Access 2000
on a Windows 2003 Terminal Server, service pack 2. The Access system is split
with Front ends and Back ends and some connection to a MySQL server.

Recently something strange has started to happen. A database gets locked
(like when you open it to make design changes) without a clear reason. The
strange thing is that when this happens nothing is written in the ldb-file,
it’s like the ldb-file is no longer connected to the mdb-file.

If I use Process Explorer to examine the process that is looking the
database I see that the process only has a file handler to the mdb-file and
not the ldb-file. If I remove the handle then the lock is removed and
everything goes back to normal again.

When this happens to a database I can’t:
• Delete the ldb-file.
• Open the mdb-file.
• Use a table in the front end that is in the mdb-file.
In short, all access to the database is denied with the error “The database
is locked by another user.”.

This problem has increased in frequency, today it happened five or six times
with four different databases. I can’t ignored it anymore, if I don’t find a
solution I will have to migrate all tables to MySQL and that is a lot of work
that I don’t have time for.
jahoobob - 30 May 2007 19:07 GMT
My first SWAG would be that some user(s) are opening the db exclusively.
Have new users been added recently?  I would check their FEs to make sure
they are sharing

>Hi!
>
[quoted text clipped - 25 lines]
>solution I will have to migrate all tables to MySQL and that is a lot of work
>that I don’t have time for.
Markus Larsson - 31 May 2007 07:16 GMT
> My first SWAG would be that some user(s) are opening the db exclusively.
> Have new users been added recently?  I would check their FEs to make sure
> they are sharing

No, no new users for a while.
Remember, nothing is written in the ldb-file when this happens. The database
gets locked outside the normal routines, how I don't know.

Markus
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.