User Stuck in MS Access DB on a Network Drive 1

[lmcpug]

Does anyone know of a way to "kick" a user from a DB that resides on a network drive? Besides involving Network Service? It would appear a power surge caused the "hang" and now we cannot modify or design the DB or enter exclusive mode. ALSO... Compact and repair will also not function.

Any help would be appreictaed.

Thanks in advance!

LMC pug

 

[dhookom]

Did you attempt to delete the LDB file?

Duane
Hook'D on Access
MS Access MVP

 

[lmcpug]

We did try this and this is the error msg we get:
cannot delete "database main cannot find a specified path make sure you specifiy the correct path"

Also posted more info as below:

ACCESS 2007 database lock out
All users can log into the main page; but when any of the 3 admins try to go exclusive, they cannot, as the database has been placed in a state by user 'UserID' on machine 'PCId' and this user has a file locked that prevents it from being opened in exclusive.
This is a multiple user DB.

We have tried everything from searching the whole database to see what file is locked, nothing! We had the IT's take the "UserID" off the server completely and then re instate; file still locked.
We have done numerous hard reboots, nothing.

Aside from pulling our hair out; we are truly hoping someone out there has had this similar problem and can advise a repair.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

any help would be greatly appeciated
regards,
lmcpug

 

[lmcpug]

Okay, after much trial and error
the conclusion is that the "UserID" who has locked the system, is stuck in the LDB files?!?!? It is the only conclusion that makes any sense as the system will not allow us to remove these files.
We have also deliberately tried to corrupt the system and fix this way but to no avail.

Any help at all would be so much appreciated right about now

We are literally pulling our hair out at this moment as the Access is literally our Roledex to all of our Ontario contacts and info. We are literally lost without it right at the moment.

lmcpug

 

[kermit01de]

I am not sure about why windows gives you the error message you described --> cannot delete "database main cannot find a specified path make sure you specifiy the correct path"

If you try to delete a file in windows, usually you should get "access denied" or anything like that, but I never saw a "database main" message from windows.

Did you try to copy the accdb and rename it --- compact/repair --- take a frontend, correct the links to the "new" backend ...



Kind regards
Mirko
--------------------------------------
>>>>>> ... I am sure, some supportissues are a matter of PEBKAC ... <<<<<

 

[-cush-]

I am sure you have tried this, but make sure machine 'PCId' is off.

 

[lmcpug]

Hi Everyone,

good news! We were able to get the IT dept to go on the server and ditch the file.

We attempted everything under the sun and all of your advise was duely noted and tried as well. But to no avail.

Apparently, should this come up with anyone else the only way, if you are on a server you cannot access due to security, and your LDB gets stuck, only the IT's can do the work necessary.

Myself and my partner in crime, would like to thank everyone for their input! It was very much appreciated.

Have a great weekend!
lmcpug

 

[dhookom]

So the IT dept just deleted the ldb file?

Duane
Hook'D on Access
MS Access MVP

 

[lmcpug]

Hi dhookom,

Yes, that is what I am being told.
They went in searched out the LDB file and removed it.

We have been working on the database tonite and have had no problems!

Thanks again and hope that this helps out with anyone else who
has the same problem occurring!

Have a great weekend!
lmcpug

 

[lameid]

To me, it sounds like a user session did not terminate it's file lock due to a power failure on the client.

Either your IT group did something to kill the file lock or the lock expired on the server. The quick and dirty way to kill such locks is to boot the machine the file is on.... Not necessarily a viable approach for a Server. I am sure with research you could find the right way to kill the locks but you would need administrative rights on the server.... It never came up for me to need to do so I have never researched it.

 

[jsteph]

lmcpug,

In the future:

(Server 2000/2003)
Go to the server Admin Tools-->Computer Management-->Shared Folders-->Open Files

Kill the file there.

(Server 2008)
ServerManager-->File Services-->Share and Store Management...
On the right look for "Manage Open Files"

Kill it there.

--Jim

 

[lameid]

Thanks jsteph for rounding that out nicely.