Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
2

P: Error while creating Virtual Copies

Community Beginner ,
Jan 24, 2020 Jan 24, 2020

When I try to create a virtual copy in Lightroom ClassicI get the following error:

"An internal error has occurred. ?:0: attempt to index field 'additionalDevelopMetadata' (a nil value)".

The error started after I combined a second catalogue into a main catalogue using the 'Import from another catalogue' function.

The error only happens with the images from the second catalogue that have been imported into the main catalogue. All other images in the main catalogue are fine. I still have the second catalogue and the virtual copy works correctly in that catalogue as well, so the issue appears to be related to the import process. The reason for combining the two catalogues was to reduce the need to swap between the two.

I had already done quite a bit of work on the imported images before I came across the virtual copy error, so I now have a bunch of edited images in my main catalogue that won't allow VCs to be created, and a bunch of un-edited images in the old second catalogue that will allow VCs to be created.

My system details are as follows:

Lightroom Classic version: 9.1 [ 201911291132-64cf80b4 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Home Premium Edition
Version: 10.0.18363
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 1.9 GHz
Built-in memory: 16192.0 MB
Real memory available to Lightroom: 16192.0 MB
Real memory used by Lightroom: 1050.7 MB (6.4%)
Virtual memory used by Lightroom: 1068.6 MB

Similar issues have been reported by other users on the following Adobe Community thread:

https://community.adobe.com/t5/lightroom-classic/error-while-creating-virtual-copies-in-lightroom-cl...

Bug Fixed
TOPICS
Windows
353
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Feb 11, 2020 Feb 11, 2020
Updates to Lightroom Classic, Camera Raw, and the Lightroom Ecosystem were released yesterday and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. You can read more about the updates here.

Thank you for your patience. 
Translate
10 Comments
Adobe Employee ,
Jan 24, 2020 Jan 24, 2020
Hi Chris,

Thanks for reporting this issue and for providing detailed information. I am able to reproduce the issue and will file a bug to investigate it further.

Regards,
Chinoy
Translate
Report
LEGEND ,
Jan 28, 2020 Jan 28, 2020
Translate
Report
Adobe Employee ,
Jan 28, 2020 Jan 28, 2020
Thanks Robert. We will look at that.
Translate
Report
New Here ,
Feb 10, 2020 Feb 10, 2020
I am running into the same problem.  I just installed Lightroom Classic on a new computer and imported the catalog from my old machine.  I don't know if it is relevant, but my old machine was running Windows 7 and had an older version of Classic running on it.
Translate
Report
Adobe Employee ,
Feb 11, 2020 Feb 11, 2020
Updates to Lightroom Classic, Camera Raw, and the Lightroom Ecosystem were released yesterday and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. You can read more about the updates here.

Thank you for your patience. 
Rikk Flohr: Adobe Photography Org
Translate
Report
Community Beginner ,
Feb 11, 2020 Feb 11, 2020
I've just tested this and it seems to work - thank you!
Translate
Report
New Here ,
Feb 11, 2020 Feb 11, 2020
I am not seeing the update.  My system says it has version 9.1 and that it is the most recent. 
Translate
Report
Adobe Employee ,
Feb 11, 2020 Feb 11, 2020
Thanks for the confirmation Chris !
Translate
Report
Community Beginner ,
Feb 12, 2020 Feb 12, 2020
My version is 9.2, build 202001311240-2d026470.
Translate
Report
New Here ,
Feb 12, 2020 Feb 12, 2020
LATEST
It took a while to show up, but I've now been able to upgrade to 9.2 and everything works fine.
Translate
Report