Results 1 to 7 of 7
  1. #1
    New Lounger
    Join Date
    Jan 2003
    Location
    Victoria, Br. Columbia, Canada
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Locked database file (2002)

    I access my company's network through a VPN, and then access my database via a terminal server client. I was working on a form design when the VPN kicked me out, which killed my connection to the terminal server. The .mdb file for the database still thinks I'm there, the .ldb file still exists for it and for the back end where the tables are. Because I had a form open in design mode, it's locked the file so I can't open or delete it. I have backups of everything, so it's not the tragedy it could have been, but I don't want that file to sit there for eternity. Is there any way to nuke it?

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Locked database file (2002)

    Can you delete the .ldb files for the front end and back end yourself? If not, can you ask a network administrator to delete them for you? Usually, the problems you describe are over once the .ldb files have been removed.

  3. #3
    New Lounger
    Join Date
    Jan 2003
    Location
    Victoria, Br. Columbia, Canada
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Locked database file (2002)

    Hi Hans--

    I did try to delete the .ldb files, but it won't let me. It tells me that there is a sharing violation, the source or destination file may be in use.

    I have done it in the past, and it worked fine, but I was never in design mode when the connection died. I don't know if that makes a difference or not.

    Would my network admin be able to delete them even in this instance?

    Thanks

    J

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Locked database file (2002)

    Hi Janny,

    A network administrator should be able to do that.

  5. #5
    2 Star Lounger
    Join Date
    Feb 2003
    Location
    Carrollton, Georgia, USA
    Posts
    123
    Thanks
    3
    Thanked 1 Time in 1 Post

    Re: Locked database file (2002)

    Guys,

    Am I wrong to assume that if the database is open by another user that you can not delete the lbd file? And, if it's open you can modify it either?

    Somewhere, I have seen someone write code to shut the database down remotely. Sorry, I don't have more info.

    KST

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Locked database file (2002)

    You can't delete an ldb file if someone else has the database open, but lock files sometimes get stuck and don't get destroyed even though all users have exited the database. That's what appears to be the problem here. There have been threads on this before, but if no one is in the database, then kicking them out doesn't apply. A reboot usually frees the lock for so it can be deleted, but you can't just reboot a server that way.
    Charlotte

  7. #7
    4 Star Lounger
    Join Date
    Aug 2002
    Location
    Dallas, Texas, USA
    Posts
    594
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Locked database file (2002)

    I have two solutions for you.

    First, and safest, is to just reinitiate your Terminal Server session. It sounds like you lost the connection, but the session is still live. (You have to physically tell TS to stop your session, otherwise it just keeps it running in the background). If you can't log back into it, you network Admin should be able to 'shadow' that session, to close the applicaiton.

    If none of that is possible, have your Network Admin go to the server that has the .mdb on it, and have him/her kill the connections to that file (it does not require a reboot to do this, you can just end sessions or connections).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •