Skip to main content
Participant
July 31, 2020
Question

Unable to update folder location

  • July 31, 2020
  • 4 replies
  • 683 views

Hi there,

I'm having an issue with Lightroom Classic CC - 7.3. I have some pictures that I sorted and moved into a new folder. Normally this is no problem and I would just click "Update folder location" and find the new folder. But now everytime I try to update the location, I'm running into an error that that says:

 

"An internal error has occured: Database "K:Pictures\Lightroom\Backups\LightroomCatalog.lrcat\Lightroom Catalog-4.lrcat": UNIQUE constraint failed: AgLibraryFolder.id_local  Statement: INSERT INTO AgLibraryFolder ( id_local, id_global, pathfrom Root,)"

 

Anyone know what's causing this issue?

 

 

This topic has been closed for replies.

4 replies

GoldingD
Legend
July 31, 2020

Are you opening an existing worrking catalog, or are you opening a backup of a catalog?

 

I assume the missing folder you are pointing to is not that backup.

Where are the missing photos? What hard drive, what folder?

 

JohanElzenga
Community Expert
Community Expert
July 31, 2020

This could be a sign of the 'capitalisation problem'. Can you post a screenshot of your folder panel? By the way, I notice from the path that you are running Lightroom with a catalog located in the Backup folder. That won't cause this issue, but I wonder if that's because you had earlier problems.

-- Johan W. Elzenga
Rob_Cullen
Community Expert
Community Expert
July 31, 2020

I have seen a similar error in the past, but no answer-  sorry!

I note your words- "....some pictures....".  So if you moved only "some" photos from one folder to another with the OS file browser, then LrC will still recognize the original folder in the same place, so 'updating' a folder location will not work. I suspect you may only be able to re-link individual photos one-by-one.

 

 

Regards. My System: Windows-11, Lightroom-Classic 15.3, Photoshop 27.5, ACR 18.3, Lightroom 9.3, Lr-iOS 10.4.0, Bridge 16.0.3 .
99jon
Legend
July 31, 2020

Are you not using the latest v 9.3?