Question .accde locked back end & unrecognized database format

[Deamo]

I setup a backend-frontend on a network drive, which was working fine for a short time, then ended up with a couple errors and an inaccessible database.

On two difference occasions, two different users accessed their own copies of the accde front end, which has locked the backend for every other user including myself.

When I had them exit the front end and try to re-open it, they would be met with the Unrecognized Database Format error.
The lock file that was created for the backend when they opened their frontend, would remain even after closing the file - this part of the issue?

All other users would still be receiving the File is Already In Use error even at this point, irrespective of trying to open their frontend, or the backend.

Deleting the lock file (.laccdb), results in every user receiving the Unrecognized Database Format error.

By moving the backend to a different location, and opening it, access claims the database is in an incosistent state and manages to recover all the data without error

The user's involved all have write access to the network drive, and i've setup the fodler as a trusted location in access

When this occurred the first time, I deleted the split database and re-split it from the original.

Any help with sorting this would be much appreciated


Also posted on the dbforums site, but can't add the link

 

[Galaxiom]

Possibly a network dropout or congestion problem during writing to the backend.

How busy is your network.? Also check the routers and cabling.

 

[Deamo]

It's at work, so reasonably busy, during testing i had it stored on the same server, but a different folder and it worked flawlessly while 5 of us were working in it at once.

I'm starting to think there might be some permissions issue, as i have full access to the folder in which it was stored during testing, however the folder in which it must be stored for general use i only have read-only access to (for files that i haven't created).

Though i'm at a loss as to how that would have any effect, expecially given that i wasn't in the database when either of the 'file in use' errors were appearing

 

[Galaxiom]

Permissions issues for the Backend should throw errors. You seem to have corruption happening.

Could anyone have opened the backend directly while other were writing via the Front End? Could two users have had the backend directly opened together.

 

[Deamo]

Yeah, it was entirely possible the first time

The 2nd, not so much. I watched as he opened his front end from his desktop. He just left it open at that point, which seems to be confirmed in the lock file, as his PC was the last two listed

hmm, maybe it's a case of importing the tables, etc one by one into a new database?

 

[Deamo]

Interestingly, this morning there's no lock file and both the back end and front end are accessible without error

So the lock file i looked at yesterday was showing 5 active connections from 4 users
Would access not closing properly cause that?

 

[Galaxiom]

Yes Access crashing will leave a lock file behind.

It is a pain when the lock on the backend can't be deleted. Shutting down the computer should release it but that wastes time. The open share does eventually time out allowing the lock file to be deleted.

To avoid the wait go to the server. Administration Tools > Shared Folders > Session and close the offending session.

 

[Deamo]

Thanks for the help Galaxiom.

Appears that it was a combination of an Access session not closing properly (not necessarily crashing), folder permissions and someone possibly accessing the back end.

The permissions should be getting updated shortly.
Users may end up with having to stay with the current spreadsheet if we continue to have issue with access sessions not closing