PDSWSS
asked on
Why suddenly can only one user at a time open our Access 2000 database?
Multiple users have been able to use our MS Access 2000 DB simultaneously for many years.
Recently, only one user can access the DB at a time. For example, when one user has the DB open and a second user clicks on the front end DB it will no longer open.
This DB consists of a front end DB and two backend DBs.
Any suggestions?
Recently, only one user can access the DB at a time. For example, when one user has the DB open and a second user clicks on the front end DB it will no longer open.
This DB consists of a front end DB and two backend DBs.
Any suggestions?
ASKER
By directory you mean the access DBs, correct?
No, not the DB's themselves, but the directory where they reside, yes.
First user to connect will create an .LDB file, which is used to place locks. If that file cannot be created, the DB is opened exclusive.
When the last person is out, the .LDB is deleted unless the DB has been flagged corrupt or they don't have delete priv.
Jim.
First user to connect will create an .LDB file, which is used to place locks. If that file cannot be created, the DB is opened exclusive.
When the last person is out, the .LDB is deleted unless the DB has been flagged corrupt or they don't have delete priv.
Jim.
Sounds like the database is opening in Exclusive Mode... Please check under
Access Options and make sure Shared Mode is selected for all users.
Access Options and make sure Shared Mode is selected for all users.
ASKER
So if the .LDB file is created when the first person opens the DB, the second person should also be able to open the DB if they have the correct permissions in place, correct?
<<So if the .LDB file is created when the first person opens the DB, the second person should also be able to open the DB if they have the correct permissions in place, correct? >>
Yes. The .LDB file is used by JET to place locks. If it's not there, then it can't do that and will open the DB exclusive for the first user that connects.
A good quick check when logged in as one of your users:
1. open explorer and navigate to the directory where the DB is.
2. Right click, select new, then text file.
3. Double click the text file. Add some text, save it, and close.
4. Right click and delete the text file.
If you can do all that, then the problem lies else where.
With all users out, there should be no .LDB file. If you see one, delete it.
The other thing to watch out for is a library or workgroup file with the same name as your DB and it's in the same directory. For example:
myApp.MDW
myApp.MDB
These when opened will result in the same .LDB file name (myApp.LDB) and you'll get all kinds of weird problems as a result.
Beyond that, you want to check and make sure someone hasn't set the exclusive option in Access as tmoore mentioned and also there is no /excl switch on any shortcuts if their used.
Usually if a setup suddenly stops working, then it's security.
If your on a terminal services server, it's also possible to have a corrupt Office install, which would then affect all users. The last thing possible is a corrupt DB.
Usually though, it's the simple stuff.
Jim.
Yes. The .LDB file is used by JET to place locks. If it's not there, then it can't do that and will open the DB exclusive for the first user that connects.
A good quick check when logged in as one of your users:
1. open explorer and navigate to the directory where the DB is.
2. Right click, select new, then text file.
3. Double click the text file. Add some text, save it, and close.
4. Right click and delete the text file.
If you can do all that, then the problem lies else where.
With all users out, there should be no .LDB file. If you see one, delete it.
The other thing to watch out for is a library or workgroup file with the same name as your DB and it's in the same directory. For example:
myApp.MDW
myApp.MDB
These when opened will result in the same .LDB file name (myApp.LDB) and you'll get all kinds of weird problems as a result.
Beyond that, you want to check and make sure someone hasn't set the exclusive option in Access as tmoore mentioned and also there is no /excl switch on any shortcuts if their used.
Usually if a setup suddenly stops working, then it's security.
If your on a terminal services server, it's also possible to have a corrupt Office install, which would then affect all users. The last thing possible is a corrupt DB.
Usually though, it's the simple stuff.
Jim.
ASKER
Thanks for the advice. Will evaluate soon.
ASKER
After testing the Access DB with another user I see I did not explain the problem
as clearly as I could have.
The second person can open the front end when another user is in the DB but can not open any forms when a second person is using the DB. Any ideas?
Sorry for not being clearer when I asked the original questions.
as clearly as I could have.
The second person can open the front end when another user is in the DB but can not open any forms when a second person is using the DB. Any ideas?
Sorry for not being clearer when I asked the original questions.
<<The second person can open the front end when another user is in the DB but can not open any forms when a second person is using the DB. Any ideas?>>
What exactly happens? Error message? Does it hang?
Jim.
What exactly happens? Error message? Does it hang?
Jim.
ASKER
The user mentioned a couple of error messages. One was regarding the network. The other regarding the MS Access Jet engine...
Will need to retest to get the exact error messages. Thanks
Will need to retest to get the exact error messages. Thanks
ASKER
Hangs and then 2 error messages appear on the screen. The user on the other end told me to the best of her memory - the 2 messages included the following text .
"jet engine couldn't find a form" and "disk or network error".
Is this enough text from the error messages to troubleshoot? thanks
"jet engine couldn't find a form" and "disk or network error".
Is this enough text from the error messages to troubleshoot? thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Users were able to
1. open explorer and navigate to the directory where the DB is.
2. Right click, select new, then text file.
3. Double click the text file. Add some text, save it, and close.
4. Right click and delete the text file.
Now one of them is getting a "disk or network error" when trying to open some of the forms.
This is when no one else is using the DB. I have not seen this happen before. Any ideas?
1. open explorer and navigate to the directory where the DB is.
2. Right click, select new, then text file.
3. Double click the text file. Add some text, save it, and close.
4. Right click and delete the text file.
Now one of them is getting a "disk or network error" when trying to open some of the forms.
This is when no one else is using the DB. I have not seen this happen before. Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Still testing - One user getting network errors when another is in the DB.
She can access everything in the DB fine when no one else is using the DB.
Does not sound like corruption. Maybe something specific to her computer.
She can access everything in the DB fine when no one else is using the DB.
Does not sound like corruption. Maybe something specific to her computer.
<<Does not sound like corruption. Maybe something specific to her computer. >>
Does the same thing happen to other users?
Any network hardware been replaced lately (like a hub or router)? Any new additions to the network (new stations, Win 7 is now in the mix, etc).
Odd problem. But if it's been running fine for years, then it's either the DB got corrupt or it's something that affects all users, which would be the network and/or server.
Jim.
Does the same thing happen to other users?
Any network hardware been replaced lately (like a hub or router)? Any new additions to the network (new stations, Win 7 is now in the mix, etc).
Odd problem. But if it's been running fine for years, then it's either the DB got corrupt or it's something that affects all users, which would be the network and/or server.
Jim.
ASKER
Does affect all users.
Since it affects all users most likely a change in the network or server?
Any specific possibilities?
Thanks,
Since it affects all users most likely a change in the network or server?
Any specific possibilities?
Thanks,
It still not clear to me what exactly we are dealing with. Is this a split application with a seperate front end and back end DB? If so, are all users sharing the same front end?
And just to confirm, when one person is in the DB(s), it works fine with no errors?
No matter what, where I would start is re-building the DB(s) involved by:
1. Creating a new DB
2. Importing all objects into it from the old DB.
If you still have the errors, then it is related to the server or network. That can be verified by taking the DB's and placing them locally on a station. It should work fine locally.
You can further extend that test by using this as the new "server" and sharing the DB's from this station. If multiple users can then use the DB, then it's the server. If there are still issues, then it's the network.
As to what netwrok wise, it could be anything; bad cable, router, hub, NIC in a station. You'd need to do some network snooping at that point to figure out what.
Again, I'd focus on the "suddenly"; what's been changed recently? hardware? software? If nothing, then I'd look at Windows updates that have been applied recently.
I'd also take a look at the event logs of both client and server and see if there are any issues.
Jim.
And just to confirm, when one person is in the DB(s), it works fine with no errors?
No matter what, where I would start is re-building the DB(s) involved by:
1. Creating a new DB
2. Importing all objects into it from the old DB.
If you still have the errors, then it is related to the server or network. That can be verified by taking the DB's and placing them locally on a station. It should work fine locally.
You can further extend that test by using this as the new "server" and sharing the DB's from this station. If multiple users can then use the DB, then it's the server. If there are still issues, then it's the network.
As to what netwrok wise, it could be anything; bad cable, router, hub, NIC in a station. You'd need to do some network snooping at that point to figure out what.
Again, I'd focus on the "suddenly"; what's been changed recently? hardware? software? If nothing, then I'd look at Windows updates that have been applied recently.
I'd also take a look at the event logs of both client and server and see if there are any issues.
Jim.
ASKER
After much testing, it appears that one of the DBs was corrupt.
After replacing it with an earlier uncorrupted version from a backup and giving users their own FEs, the problem has appeared to go away.
Thanks for your expert advise. Will assign points now.
After replacing it with an earlier uncorrupted version from a backup and giving users their own FEs, the problem has appeared to go away.
Thanks for your expert advise. Will assign points now.
ASKER
JDettman: Thanks again for staying with this question even though it took a while to solve this issue.
Glad to hear you got it sorted out.
Jim.
Jim.
All users need full read/write/delete privs for the directory.
Jim.