Inconsistent State, unable to open backend

M

mjdemaris

Working on it...
Local time
Today, 10:45
Joined
Jul 9, 2015
Messages
426
Well, i've done some searching, and tried some suggested fixes, but so far I cannot get into the backend.

Background info:
  • several users called me stating they cannot use the database.
  • each user has a local FE.
  • there is a locked db file (.laccdb) still in the backend folder - (network server)
  • i cannot delete the locked file, i cannot directly open the BE.
  • i cannot run a command line /repair
  • i don't see a "Database To Compact From" dialog box, as suggested by some websites - open Access, click "File" (which is only available if a db is open), click Compact and Repair, use the dialog box to choose file...this does not exist and only works on the currently open file.

So, i am currently waiting for MS to make a backup and recover what it can, but I have been waiting for at least 10 minutes and wondering what else to do.

We use Windows 10, Access 2016.
 
Have you tried making a copy of the BE in a different location? From the description, you are having an issue where one user has the file locked and that is keeping anyone else from accessing it.
 
Well, Mark, I just did that. The MS recovery thing went for 40 minutes and gave up nothing, so i copied the DB.
However, I cannot delete the original files on the network. It looks like I'll have to rename it to get it to work again.
Unfortunately, this means manually deploying each FE again.

Unless you have a better way removing the locked files.

The last error in the copied file is 3343: unrecognized database format, which was thrown when the user clicked a button to close a form (creating a purchase request - which does a few things, so the exact timing and function call is not known...possibly at the form close event)
 
Well, Paul, that sure buffs my confidence in Microsoft.

Seems like a lot of issues have been revolving around that particular build.
 
You and a lot of other people. For my employer I still develop in 2010. I let others live on the bleeding edge. ;)
 
I have users on both, but more on 7. I've got both on different machines, but develop on 7. Lowest common denominator is my thinking.
 
Ok, well, the copied DB says it's in an inconsistent state every time I open it.
Even after I run the compact and repair.

However, the command line seemed to fix that...
 
Have you tried creating a new file and then importing the tables to the new file?
 
OK, copy worked, but didn't resolve all issues. Gina's got the next step in trying to make sure you don't loose everything. Even if your back end does have some corruption, importing to a clean DB can fix a lot of issues.

Have you tried dropping the server and bringing it back up? In many environments this isn't practical due to business concerns. If this is ONE user that has locked up the back end this should reset everything and allow your locked file to be removed. This would also be a good time to double check for any processes that may also be trying to access your back end. Having a backup run on it while doing updates can be messy.
 
Gina: i did try that, initially, as well. Forgot to include in the list above. As long as the BE is in an inconsistent state and "in use", no actions (save copy) can be taken on it, apparently.
 
Have you tried importing from a copy of your BE?
 
I did not try importing from the copy file. However, I did mention (in an edit) that the command line "/repair" worked on the copy file.
After which i was able to rename the BE file, and put it back into production.
Restarting the server is definitely a no go.
Thanks for all your help, oh, and i just checked the old BE and the locked file today, and was able to delete both of them.
 
Also want to include this bit:
I did realize that one of my forms was directly tied to a table, so i created a query for the record source instead. Perhaps this will prevent future problems...
 
Probably not, as the description of your problem is
1) User logs into their computer on your network.
2) User access your BE and puts a lock on it.
3) User decides to go on holiday leaving your back end locked until they either come back OR your server decides "Well, they're not coming back"...

The give away is you not being able to deal with files normally. If the server won't allow you to delete one and tells you it is in use, then the server thinks another user is using it.
 
You must log in or register to reply here.

Similar threads

T
inconsistent state
Replies
2
Views
245
The_Doc_Man
The_Doc_Man
R
Database inconsistent
Replies
9
Views
477
gemma-the-husky
gemma-the-husky
J
Unable to connect to backend tables
Replies
1
Views
367
isladogs
isladogs
A
Solved VBA compact-and-repair of a closed (corrupted) database from a new, blank Access file
2
Replies
24
Views
1,046
isladogs
isladogs
L
Solved Lock file errors on FE. Multiple access tasks in task manager.
Replies
2
Views
337
likecricketilovesit
L

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top Bottom