Skip to main content
Inspiring
October 23, 2017

Lightroom CC: Migration fails with non-informative error message

  • October 23, 2017
  • 31 replies
  • 457 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/CONVERSATIONS (but still not the same)
https://feedback.photoshop.com/photoshop_family/topics/migration-fails-with-unhelpful-error
https://feedback.photoshop.com/photoshop_family/topics/lightroom-cc-catalog-migration-error-unknown

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//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://._smb._tcp.local// (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 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.

31 replies

Inspiring
August 31, 2019
Hello,

I'm also having this issue since long, I tried everything even uninstall lightroom an still happening.

Is so frustrating paying every month for a product that doesn't work and also as I can see in the threats no one from adobe cares to give some explanation or hot-fix to install or something to help.

Inspiring
November 17, 2018
I'm having similar issues, where I cannot migrate from LR Classic to LRCC. Both products are fully updated. Can someone from Engineering please get in touch with me?

==


********** ERROR CODE AND COUNT ***********
PROCESSING_ERROR : 1


********** SOURCE FILE PROCESSING DETAILS ***********
storeProviderID : EA3569AC-688B-4140-93FE-424DCB3A8C39
Source DBVersion  : 0700003
Number of absolute folder paths : 2
Number of relative paths : 476
Number of Valid folders : 76
Number of invalid folders : 0
Size of Valid Assets : 108510748344
Number of assets : 15476
Number of assets owned by sources. : 15476
Number of missing assets due to missing files : 0
Number of missing assets due to missing folders : 0
Number of missing assets  : 0
Number of virtual copies : 6
Number of skipped virtual copies : 0


***************************
( ErrorCode: PROCESSING_ERROR )
***************************
PROCESSING_ERRORError occurred during [ 
Asset_stage_verification_pass : bad argument #1 to 'stringByAppendingPathComponent' (string expected, got table)  ].  Error Info : ^2


Inspiring
October 27, 2018
I see this thread is fairly old but I'm still having a similar issue. CC will not import my Lightroom catalogue. I've put all the details of my issue here in this thread but was asked to comment here. https://forums.adobe.com/message/10610287#10610287

Rick Spaulding -
Legend
February 13, 2018
Hi folks! 

It is my pleasure to announce that we have released a new version of Lightroom CC tonight. We believe the new version has fixed this issue. Update your application to the new Lightroom CC 1.2 and give it a try.


Enjoy!

Victoria Bampton LR Queen
Community Expert
Community Expert
January 5, 2018
Victoria - The Lightroom Queen
Participating Frequently
January 3, 2018
Hi Michael, 

Thanks for the logs. The issue you are facing is actually https://console.getsatisfaction.com/photoshop_family/conversations/migrations-fails-at-albums. This will be fixed in next release.
If you want to delete ALL the data in cloud, you will be able to do it by using the `Delete All Data` options in LrClassic->Preferences->Lightroom CC. 

Before migrating, you will need to clean up the albums with names _1_2... which are more than 250 chars.

After deleting all cloud data, before launching Lightroom CC after the operation, you can delete your `Lightroom Library.lrlibrary`. Note that any pending import will be deleted. I hope you dont have any. After that you should be able to migrate the catalog, assuming you have enough cloud/local storage and all album names are under 250 chars.
Participating Frequently
January 2, 2018
I will. 
Inspiring
December 31, 2017
I'm getting this error also. I've done all the work-arounds mentioned above, and I am using version 1.1, where this was supposedly fixed. Can someone contact me privately to get this fixed?
Participating Frequently
December 14, 2017
This issue( migration error due to failure in fetching drive details ) has been fixed in the 1.1 release. Thanks everyone for helping us resolve this.
Participating Frequently
November 29, 2017
ok. So we see there are issues with the file. Could you please close LrCC, delete the MRU, relaunch LrCC, wait 10 mins, then start migration? 
Let me know how it goes.