Pages: [1]   Go Down

Author Topic: Can't Open Catalog, but Backup Works  (Read 1956 times)

HSakols

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1239
    • Hugh Sakols Photography
Can't Open Catalog, but Backup Works
« on: January 17, 2016, 09:36:19 pm »

Hi When I try to open my Adobe Lightroom 6 catalog I now get the following message.  The Lightroom catalog cannot be used because the parent folder “/Volumes/Newer HD/Main Image Catalog” does not allow files to be created within it.  Luckily, I can access the backup catalog.   Is it possible to repair my primary catalog?

Logged

fdisilvestro

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1854
    • Frank Disilvestro
Re: Can't Open Catalog, but Backup Works
« Reply #1 on: January 18, 2016, 02:17:46 am »

Hi,

The message you are receiving does not mean that there is an issue with the catalog. It looks like LR is lacking permission to write in the folder.
When LR opens, it creates two additional files <catalog>.lrcat.lock and <catalog>.lrcat-journal even if you don't perform any edit.

Try moving or copying your catalog to a different location, maybe to the folder where you have the backup (since you know it works there)

bns

  • Full Member
  • ***
  • Offline Offline
  • Posts: 181
    • Boudewijn Swanenburg Photography
Re: Can't Open Catalog, but Backup Works
« Reply #2 on: January 18, 2016, 03:15:46 am »

If the files lrcat.lock and or lrcat-journal are still present, simply delete them. When LR terminates properly these file are deleted. If they are still present, LR will not start.

cheers,
Boudewijn Swanenburg

HSakols

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1239
    • Hugh Sakols Photography
Re: Can't Open Catalog, but Backup Works
« Reply #3 on: January 18, 2016, 11:38:17 am »

Quote
Try moving or copying your catalog to a different location

Thank you.  That did the job. 
Logged

howardm

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1984
Re: Can't Open Catalog, but Backup Works
« Reply #4 on: January 18, 2016, 12:08:15 pm »

You should really look into how/why the permissions on 'Newer HD' got borked to read-only (instead of read-write)
Pages: [1]   Go Up