Page 1 of 2 12 LastLast
Results 1 to 15 of 20
  1. #1
    Join Date
    Sep 2008
    Posts
    7

    Unanswered: Ldb file cannot be deleted..

    Hi All,

    I have several databases partioned in front end and back. Recently, the ldb file cannot be deleted because it is saying that the file is in use.

    I have tried many things but nothing seems to solve this issue. The users have full access on the folder where the databases are. The users say that when a failover (i dont know what this means) is done, then the locks disappear.

    I looked for MsAccess.exe on the server, but found none. I even looked for users who have open the shared file (using Windows MMC), unfortunately, the file does not seem opened there as well.

    Using the LDBView, i found that the file is open on a particular server and the databases are in suspect state. Do this mean that the database is corrupted?? I tried a Compact and Repair but again this fails due saying that the file is already open.

    I recently installed SP3 for MsOffice. This also hasnt resolve this issue.

    If anyone has a solution can you please post.

    Thanks for your replies.

    Amit

  2. #2
    Join Date
    Apr 2005
    Location
    Zagreb - Croatia
    Posts
    372
    Ask your system engineer, he can delete LDB file.

  3. #3
    Join Date
    Sep 2008
    Posts
    7
    He tried he gets a message saying that the file is currently in use. Even the users have logged out of the application. But it seems that only the failover is successful in removing the lock.

    Is there any alternative where this file cannot be deleted. Please advise

  4. #4
    Join Date
    Apr 2005
    Location
    Zagreb - Croatia
    Posts
    372
    Sometimes I have the same problem and my system engineer delete LDB file without any problem.

  5. #5
    Join Date
    Sep 2008
    Posts
    7
    Hello,

    How does he delete the file. I mean, does he make use of any software or just right click on the ldb file and delete?

    Thanks for your replies.

    Amit

  6. #6
    Join Date
    Apr 2005
    Location
    Zagreb - Croatia
    Posts
    372
    I don't know that, I'm programer only.

  7. #7
    Join Date
    Apr 2005
    Location
    Zagreb - Croatia
    Posts
    372
    My system engineer said, he did it via Nowell software.
    we have got a Nowell network.

  8. #8
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    if the LDB fiel is reaminaing open when you are certain no one is using the db then you have a potential problem

    it could be caused by network problems
    it could be casue by an an Access instance that has crashed but not cleared the LDB
    it could be casued by a ghost process (where the Access instance has crashed by reamined active in memory).

    there is a mechanism of viewing who is connected to a LDB file.. forge the details it was in the Getz Access Developer Handbook, and Im sure its on t'web somewhere.
    it can identify which machine which user is still registerd as using the ldb.

    ..of course your users could be lying (as if!)
    ..of course it could actaully be you rmachine that is creating the error messages

    you should be able to delete the LDB file by a simple OS command.. find where the file is and delete it... look for a fiel of the same name but with a diferrent extension (usually its in the same directory as the MDB/MDE). But Id want to make sure its not being used before culling it.
    I'd rather be riding on the Tiger 800 or the Norton

  9. #9
    Join Date
    Feb 2004
    Location
    Chicago, IL
    Posts
    1,312
    My suggestion would be to have anyone that has used the database to shutdown their systems. I have had that problem several times and shutting down each system that may have opened the database usually works. I don't know why it works, but when in doubt shut it down.

  10. #10
    Join Date
    Oct 2004
    Location
    Melbourne, Australia
    Posts
    201
    DCKunkle's remarks are on the ball, I think. The point to remember is that there is a lot of caching going on in the most unlikely places (even the links between backend and front-end databases). You must be sure that there is no action going on ANYWHERE !

  11. #11
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    If you use this script: http://www.dbforums.com/showpost.php...6&postcount=19, you'll never have the problem ever again with locked *.ldb files. With the current setup sounding like it does, you most likely will experience this problem time after time.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  12. #12
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Sounds like the all-too-common problem of Access not quite closing.

    Check the task manager for a service called MSACCESS.EXE and close it when found. I have never run into a situation where the LDB couldn't be deleted that wasn't caused by this... it always turns out to be a machine that is hanging on to the database.

    And yes, restarting the entire network would also "fix" it. Finding it in Task Manager will at least point you to the computer that is holding onto the database though.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  13. #13
    Join Date
    Sep 2008
    Posts
    7
    Hi All,

    Thanks for your replies.

    There is no MSAccess.exe running in the task bar. The LDBView says that the database is in suspect state. Moreover making 50 users restarting their PC's is not acceptable by a management view.

    Note that the Citrix server (server1) from where the database is accessed is rebooted everyday and the database itself resides on another server (server2) which is not restarted.

    This application exists for about 10 yrs, and it is only recently that this issues have cropped up.

    Any help of getting this lock of out the way will help me a lot.

    Thanks for posting.
    Amit

  14. #14
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    Its not unknown for Access (or other applications) to run in background, or remain as processes and not appear in the task bar, but DO appear in the TASK MANAGER.

    what I suspect may have happened is that Access has crashed, for what ever reason, and not fully shutdown, leaving an orphaned process on a computer which doesn't appear on the task bar, but still has a cliam on the MDB/LDB.

    If the app has run succesfully for the period of time you indictate then I'd want to investigate what has changed recently in the system.

    rebooting the server which has the db on, or moving that db to a server that is periodically rebooted may be a smart move.. that will sever any ghost processes links to the db.
    I'd rather be riding on the Tiger 800 or the Norton

  15. #15
    Join Date
    Sep 2008
    Posts
    7
    Is there any software or application where i can see the ghost processes running and kill them. If not, is there any command (i tried del /f from command prompt but it didnt work)

    According to the engineers, there is nothing installed before this error have started.

    Cheers
    Amit

Posting Permissions

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