Skip navigation
Currently Being Moderated

Lightroom catalog cannot be opened because another application already has it opened

Oct 22, 2008 9:30 AM

 
Replies
  • Currently Being Moderated
    Oct 22, 2008 9:58 AM   in reply to (Harry_R_Matthews)
    Try looking into whatever directory your catalog is in and deleting the ".lock" file with the same name as your catalog.
     
    |
    Mark as:
  • Currently Being Moderated
    Dec 1, 2010 8:21 AM   in reply to (Harry_R_Matthews)

    Thank you, it solved my problem as well!

     

    www.marciocavalcanti.com

    Miami Wedding Photographer

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 23, 2011 12:44 PM   in reply to (Harry_R_Matthews)

    deleted the .lock file...worked for me...

    my computer rebooted and I couldn't open my catalog....I was going crazy...it would open a different catalog fine, but not my large catalog....so I did a search and found this post...thanks so much

     
    |
    Mark as:
  • Currently Being Moderated
    May 17, 2011 6:31 AM   in reply to (Harry_R_Matthews)

    Great! Thank you!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 14, 2011 6:06 PM   in reply to (DW_Harrison)

    Thanks for this solution. Worked great today for me!

     

    Michael

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 9, 2011 9:22 PM   in reply to Michael J. O\'Connell

    Thank you, I had the same problem.

     

    But honestly Adobe… is it too damn complex to search for another lightroom process instead of asking the user to close a non existant process? If you don't find the process you can easily assume something crappy happened and delete the lock file by yourselves and then check the integrity of the database.

     

    I mean… shouldn't be that complex right?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 17, 2011 8:42 AM   in reply to (Harry_R_Matthews)

    I can not tell you how many times LightRoom 3.5 or earlier just freezes under Win 7-64 bit. You can  not CTL+ANT+DEL or anything else but manual shut down. This typically occurs when user enters something before a LightRoom task is completed. It is not acceptable!

     

    When rebooting, anything might have happened but usually nothing. I failed to notice a lost folder of all 2011 photos. This occurred just after my last backup so some delay before even noticing since I was working on older folders. So all are now gone.

     

    The most recent freeze was the typical several minute wait while loading the catalog and reading the camera's card. The inevitable reboot left the catalog locked so it was easy to simply delete the lock file after nearly an hour getting to this suggestion. Maybe we are using oppisite sides of the brain but the delete lock file suggestion would help on the actual error message. The real problem is frequent lock ups! Do you think enough 64 bit users might dump this product with similar lock ups / lost files or folders and long research time to find a solution? Release 4 is not looking likely!LightRoom warning.JPG

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 10:10 AM   in reply to (DW_Harrison)

    Thank you!   Worked like a charm.  I only encountered this error today for the first time after working with LR since release of version 1, and that was due to a sudden power outage.  Glad that finding the solution was this easy!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 9:41 AM   in reply to JohnR84740

    oh no,  i just did as suggested above. Great lightroom opens but all the grading i did on the pictures have gone! I even made a copy of the LRCAT file before deleting the lock file and LR was def closed as i just did a restart.

     

    What happened to all the work i just finished? can i get it back. deadline 29 hours...

    thanks.

     

    info@stushapiro.com

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 2:00 AM   in reply to (Harry_R_Matthews)

    Hiya - just wanted to add my thanks as I was having this same problem and the solution has worked for me as well now.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 30, 2012 12:39 PM   in reply to (Harry_R_Matthews)

    I was just having the same issue, and my problem is now solved!  Thank you so much, @DW_Harrison!!

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (1)