Skip to main content
Participant
October 23, 2017
Answered

Migration fails with non-informative error message

  • October 23, 2017
  • 3 replies
  • 1872 views

I am trying to migrate my catalog from Lightroom Classic CC to the new Lightroom CC and getting a non-helpful error message directly after checking file paths.

SIMILAR REPORTS (but still not the same)

- Migration failed with uninformative error

- Migration error

MY ENVIRONMENT

- MacBookPro11,3 with MacOS 10.13 with a SSD formatted with encrypted APFS

- Lightroom Classic CC 7.0 [ 1140024 ]

- Lightroom CC 1.0 [ 20170919-1412-ccb76bd ] (Sep 19 2017)

- "Classic"-Catalog at default place /Users/<user>/Pictures/Lightroom/Lightroom Catalog.lrcat

- about 30.000 image files (mostly NEF raws and JPEGs) of total size 500 GB

- Image files stored on connected samba share smb://<servername>._smb._tcp.local/<share name>/<folder name> (running on a Synology NAS with latest firmware).

- CC originals folder location changed to an external spinning disk hard drive (size: 1 TB). Connected via USB. Formatted as MacOS Extended (Journaled, Encrypted).

- free space of main harddrive close to 150 GB

PREPARATIONS

- strictly followed  https://helpx.adobe.com/lightroom-cc/using/migrate-to-lightroom-cc.html

- double checked if samba share and USB disk are connected and accessible/writable

STEPS

1.) start Lightroom CC via Terminal using option "-tracebacks"

2.) start migrating catalog via UI of Lightroom CC. (File -> Import -> Migrate LR catalog)

3.) migration wizard starts up and checks all file paths. At least the maximum count of my images is reached before the message appears.

OBSERVED BEHAVIOR

- Error message: "Migration was not successful. No one is more unhappy about this than us. Except you probably. Please contact our support team."

- For Terminal output see end of this post

- Migration is terminated

EXPECTED BEHAVIOR

- Successful migration 😉 or at least some useful information that could help me (or support) to resolve the issue.

- Some log file that could provide more information. Where could I look on what actually went wrong?

TERMINAL OUTPUT

2017-10-23 21:30:08.912 Adobe Lightroom CC[1676:304008] Enabling noisy tracebacks.

objc[1678]: Class MacExePath is implemented in both /Library/Application Support/Adobe/OOBE/PDApp/P7/adobe_licutil.app/Contents/MacOS/adobe_licutil (0x1f6454) and /Applications/Utilities/Adobe Application Manager/P7/axlibv7.dylib (0x4c1d1ac). One of the two will be used. Which one is undefined.

2017-10-23 21:30:09.333 Adobe Lightroom CC[1676:304008] *** WARNING: Textured window <AgFullScreenableWindow: 0x7f7fc271bd70> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.

2017-10-23 21:30:11.948 Adobe Lightroom CC[1676:304008] Failed to restore first responder (message was _finishedLoadingNibDependencies) NOT KEY

2017-10-23 21:30:25.407 Adobe Lightroom CC[1676:304008]

maybeAssignLayoutAttributeL had an unhandled key: place

2017-10-23 21:38:20.939 Adobe Lightroom CC Helper[1679:313266] WFModels ERROR Observable model "WFCatUserModel.makeUserModel/catalog/checkNeededMainDriveSpace" posting transient error {

}, "bad argument #2 ((*temporary)) to ? (string expected, got boolean)", nil

2017-10-23 21:38:20.944 Adobe Lightroom CC[1676:313272] WFModels ERROR Observable model "checkNeededMainDriveSpace" posting transient error {

}, "bad argument #2 ((*temporary)) to ? (string expected, got boolean)", nil

2017-10-23 21:38:20.944 Adobe Lightroom CC[1676:304008]

?:0: attempt to index a nil value

    0: upvalue  ?                              - 749838990:1956+1

    1:          [unnamed]                      - 1096034565:20+3

    2: global   pcall                          - C

    3: method   next                           - 835593318:52+7

    4: method   onNext                         - 1132845634:30+6

    5:          [unnamed]                      - 2135929331:61+8

    6: global   pcall                          - C

    7:          [unnamed]                      - 2135929331:185+20

    8: global   pcall                          - C

    9:          [unnamed]                      - 1802721243:96+14

   10:          [unnamed]                      - tail

   11: global   pcall                          - C

   12: method   invoke                         - 363310666:47+4

   13:          [unnamed]                      - 1220733886:30+14

   14: global   pcall                          - C

   15:          [unnamed]                      - 1220733886:46+24

   16:          [unnamed]                      - tail

   17: method   ensureActive                   - 2135929331:221+23

   18: method   onNext                         - 1333402193:369+38

   19:          [unnamed]                      - 749838990:1848+11

   20:          [unnamed]                      - tail

   21:          [unnamed]                      - 1724616215:399+16

   22:          [unnamed]                      - C

---------------------------------

This topic has been closed for replies.
Correct answer Apfelkraut_org

As workaround I was able to successfully migrate my catalog by placing the image files, the original lightroom classic catalog, and the originals folder of Lightroom CC on the same external USB drive. For details see the Migration fails with non-informative error message | Photoshop Family Customer Community

3 replies

Participating Frequently
January 21, 2019

Hi - I had a similar issue, and none of the suggested fixes/workarounds I could find on the web, nor with Adobe  tech support could resolve my instance of this issue.

What eventually worked for me, and which hopefully will help others who have a similar problem is this:  in Lightroom classic, simply export your entire catalog to a new catalog, and migrate that new catalog to Lightroom CC.  This effectively rebuilds your catalogue from scratch, maintaining all your metadata etc but fixing whatever minor corruption that was causing the migration to hang.  Secondary tip is to export your lightroom classic catalogue into several sub-catalogues and importing those.  This helps disk space issues with very large catalogues.

marcelloa88472007
Participant
January 4, 2021

Good day, I had the same issue in migrating the existing Lightroom Classic library to the [new] Lightroom (cloud based).

My library was pretty large and at the end of every export attemp I got an error.

 

What wrorked for me was to export my whole library by year (2010, 2011, 2012...), in order to have much smaller libraries.

I will now migrate each library into Lightroom (cloud based).

 

In the majority of the cases I think that errors occur when the software has to handle large libraries.

Apfelkraut_orgAuthorCorrect answer
Participant
November 3, 2017

As workaround I was able to successfully migrate my catalog by placing the image files, the original lightroom classic catalog, and the originals folder of Lightroom CC on the same external USB drive. For details see the Migration fails with non-informative error message | Photoshop Family Customer Community

Sahil.Chawla
Adobe Employee
Adobe Employee
October 24, 2017

Hi Apfelkraut,

I see you have also posted this issue here and it is being looked at by our engineering person Migration fails with non-informative error message | Photoshop Family Customer Community

please reply to that person so that we can get this issue resolved for you.

Regards,

Sahil

Participant
October 24, 2017

Hi Sahil,

thanks for your reply. I did so just now but meanwhile also found an alternative approach that worked for me.

May I still ask what should be posted here and what at the Photoshop Family Customer Community? What is the difference at all?

Best regards,

Apfelkraut