Lightroom CC: Migrations fails at Albums

  • 2
  • Problem
  • Updated 7 months ago
  • In Progress
  • (Edited)
My migration has been a disaster. After cleaning up my hard drive it finally started. At some point it seems that my external drive with my photos (not the catalog) got disconnected. The migration stopped and then after reconnecting it said that the original data source or something like that had changed even I did not do anything. I told it to continue with the original status (not sure about the exact wording anymore) and it said something like importing from manifest. Anyhow after that it kept migrating for quite a while so everything seemed normal.

Than after a few hours it crashed again with this ridiculous error message don't telling me anything. Clicking on support just brought me to a page with possible errors which did not cover my issue.



After clicking ok in the end it just exited and that was it. Somehow it kept syncing images, at least it told me so when clicking on the cloud icon top right.

I went to File > Migrate Catalog again and clicked continue. It started running again this time pretty quickly:
- mark catalog migrated
- adding photos and videos
- adding faces
- adding albums
There at albums at about 81% progress it crashed again with the same message above. I can do this over and over again and always the same result.

When I go into the album section in Lightroom CC it actually has a long list of folders but a) it is quite messy and b) it says 0 photos behind each name. However all albums have a little gray circle with a checkmark in front of them. The albums which I had previously synced with smart collections all have a little blue spinning wheel instead of the checkmark but it shows the correct number of images behind them (not 0)

Also what I noticed, not sure if related to this is about 300 something photos with no meta data and no capture date (which was not the case in Lightroom Classic)

For info I have about 65k images and videos in my catalog, mostly Raw. Currently it says that about 580GB out of 1TB cloud space are used and it says a a little more than 58k photos syncing right now.

Update: Now the photos show up also in the iOS and web app under 'all photos'. So the images seem to sync just the albums are also not syncing
One more thing: If I open the Lightroom app on my iPhone, iPad or Apple TV app (all up to date) or in the web client it only shows the albums I had previously synced via smart collections nothing else from the migrated catalog.

So where does this leave me? Is the migration failed? How can I make it finish? 

Thanks

Btw: I think that 'you can only migrate once' is absolutely ridiculous and a huge joke! There has to be a full reset / start over from scratch option that cleans out everything an lets me start over fresh.
Photo of Hannes Hess

Hannes Hess

  • 25 Posts
  • 3 Reply Likes
  • frustrated

Posted 9 months ago

  • 2
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
We are really sorry about it. Could you please share the logs so that we can see what went wrong?  You can find the folder here ->  /Users/<user>/Pictures/Lightroom Library.lrlibrary/migration/lrcat/<lrcat name> 
Photo of Hannes Hess

Hannes Hess

  • 25 Posts
  • 3 Reply Likes
I have the folder /Users/<user>/Pictures/Lightroom but no folders afterwards like Library.lrlibrary/migration/lrcat/<lrcat name> 
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
Sorry, I wasn't clear. "Lightroom Library.lrlibrary" is a single name. You need to look for the folder/bundle with name "Lightroom Library.lrlibrary" inside Pictures folder.
Photo of Patrick

Patrick

  • 4 Posts
  • 1 Reply Like
I have exactly the same problem. Same useless error message. No indication of the issue. Only some manual attempts at restarting (based on info from user above) suggest that mine also fails during the "albums" process. Also here, it is very unclear to me from the "error dialog", where/how to get support for this problem or how to proceed. It really feels like this "migration process" is designed to convince people to finally really abandon Lightroom, or is that just me? Can someone point me to support or useful info? (Note that it already migrated ~40K photos and it is not even clear whether/how I could restart the process??) Is there some support email where I can get help?
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
Thanks for the logs, Patrick. The issue is because your catalog had albums with names longer than 250 characters, and LrCC doesn't support albums with name that long. These names are of the form `1_2_3_..` and seems to be auto-generated. I am curious how these were created in the first place. 
We are working on handling this error gracefully as well as informing the issue to the user beforehand. 
Photo of Patrick

Patrick

  • 4 Posts
  • 1 Reply Like
Thanks for the explanation. How do I fix this? Can I still change the albums in "Classic", save the library and then have the migration complete? (I suspect this may not work??) Hopefully I don't need to re-try the whole migration? Or, is that even possible or practical?

(By the way - suggestion: when something fails at the very end of a super painful and time consuming migration process, don't put a useless error message that tries to be funny. It is not funny to the (paying!) user (i.e. me) who just spent over a week opening up space, moving files around, getting the libraries in the right place, cleaning up external hard drives, and doing extensive google searching to get to that point. Especially if there are no concrete instructions for how to get actual help, or any hint whatsoever about what may be wrong.)
Photo of Patrick

Patrick

  • 4 Posts
  • 1 Reply Like
Ok - I checked things in the classic program. Those long-named collections were the result of an attempt to import my (apple) iPhoto library, some while ago. I thought this was done using a Lightroom import feature, but don't recall the details. (If so, I may not be the only user with this issue)
Photo of Hannes Hess

Hannes Hess

  • 24 Posts
  • 1 Reply Like
That was exactly the same issue I was having. I also had these 1_2_3 albums. They were created when I migrated from Aperture to Lightroom and I never got rid of these Albums. I now deleted them in LR Classic. However in the mean time I had actually cancelled the migration in hopes it would roll back everything back in the cloud and erase the bits and pieces of the failed migration.
However I still have these half migrated data in the Cloud I cannot get rid of. I guess trying to migrate the library again will only create more of a mess.

What can I do? Asha, can you actually remove the left overs from the failed migration so that I can start over fresh? Or can I do this by myself?

And what about all the photos already uploaded? Do I need to delete them before making another attempt so I don't end up with a bunch of doubles? Or will the migration re-link them to the newly migrated catalog?
(Edited)
Photo of Hannes Hess

Hannes Hess

  • 24 Posts
  • 1 Reply Like
Update: I exported a few images as new catalog in Classic which where already uploaded in the failed migration. Then I migrated that small test catalog which worked without error in CC. However I checked and the images are now double.

So I guess before I attempt another migration approach of my full catalog there is a need to remove everything from the cloud before so I don't end up with all double images.

So how can this be done?

Thanks
Photo of Geoffrey Anderson

Geoffrey Anderson

  • 6 Posts
  • 1 Reply Like
Ah, Apple iPhoto (and Aperture) shenanigans. I have been cleaning up that mess myself (not as terminal as your issue though)
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
It is not advisable to abort the migration if you have already half way and you would like to migrate this catalog again. We will be able to resume the migration properly, in most of the cases, if its being stopped/paused due to some error or other reason. 

Hannes, 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. But please be careful, because any asset you have uploaded via LrCC Desktop or mobile or web client, which has not yet synced down to LrClassic will get deleted.
If you are taking this route, then, 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.

In case you DONT want to delete ALL cloud data and only the ones which was added as part of migration, it will be very difficult to do and it will depend on many other stuff like, whether you had synced assets before, whether you had stacks or face tagging etc.
Photo of Hannes Hess

Hannes Hess

  • 24 Posts
  • 1 Reply Like
Hi Asha,

thanks so much for your help. Finally I am getting somewhere again.
So fortunately I had never synced classic after the failed attempts so my classic library was still 100% intact. The only thing was that I uploaded some pictures from my iPhone after the failed attempt which of course were not in classic (because no sync) and only in the could. I went into CC and saved all these images and videos to my HDD.
After that I took the delete all data option and completely eradicated everything on the cloud. Man that felt good :) Finally a clean slate and now I can start fresh.
I went into Classic, everything still fine in there. I enabled sync no problems. Synced one album into the cloud to see if it worked, took some images from my iPhone directly to the cloud. Waited for the sync, everything works like a charm.
Then I imported the images into Classic which I saved earlier from CC. Now these are also in Classic so all images there safe and sound.

This being said I am finally a happy camper again. 
I will most certainly wait for 1.1 before I try this again. Also I will do some more housekeeping in my Classic library, especially the albums before I try anything again

Any ETA on 1.1 already?

Thanks again for your help!
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
@Hannes, yes, you can wait for the 1.1 release. 
@Patrick, Glad to know that your issue is fixed now. But I would like to know more about the slowness you were talking about. Migration process is slow, or syncing after that is slow, or both?
Photo of Frank Maschmeier

Frank Maschmeier

  • 2 Posts
  • 0 Reply Likes
Hi Asha,

I do have exactly the same issue. Waited for Version 1.1 and then tried to finish migration. But same problem appears.

Therefore I assumed its not fixed in 1.1?

And yes those Albums were created when migrating from iPhoto to Lightroom.
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
Sorry Frank. The fix for this particular issue was not ready by the time we froze 1.1. It will be there in the next release. I had suggested Hannes to wait for the 1.1 release since he had already deleted the iPhoto albums and that wouldn't have interfered anyways. Plus 1.1 has many improvements with respect to, storage management. 

Frank, With respect to your current issue, whats the state of migration right now? Perhaps i can help you with that.
Photo of Frank Maschmeier

Frank Maschmeier

  • 2 Posts
  • 0 Reply Likes
Hi Asha,
thx for offering your help.
That's the state of migration / what I did so far:
a) converting catalogue (57K photos - 300GB) from Lightroom to Lightroom Classic CC
b) moved the catalogue (only catalogue - original photos are stored on Synology NAS) from MacBook SSD to external drive
c) failed to migrate complete catalogue due to extensive space needed on MacBook SSD during migration, therefore:
d) exported year by year from the main catalogue of Lightroom Classic CC into a new Lightroom Classic CC catalogue also stored to the external drive -> 19 catalogues (one per year)
e) migrating the 19 catalogues to Lightroom CC, one after the other
f) 7 catalogues were having the issue "failing at albums", but all photos seem to be migrated
g) for 6 catalogues I confirmed to finish the migration although not complete
h) for 1 last catalogue I kept the migration status open
i) all original files and original catalogues still available

Since the whole process took me around two weeks and I do not desperately need to migrate the album information, my main concerns are:
1) Are all photos migrated? The number of photos shown at "last import" matches with the number of photos in the original catalogue. But not sure if he really uploaded all the original photos and not only smart-previews or such ...
2) What is usually happening after 81% (connecting albums with fotos) during the migration process? / Is there any other important info (meta data or such) which was not migrated due to the early stop of process?

If nothing essential is missing, I would keep it as it is and delete the empty albums/folders. If you recommend restarting the migration process for the affected catalogues, please advice what to do.

Thx, Frank
(Edited)
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
Hi Frank, 

Splitting the original catalog into multiple small ones and then migrating is safe if and only if you have never synced anything from your LrClassic catalog and you never wish to turn on sync in Lr classic. When you export the current catalog into smaller catalogs, the sync information is gone and hence when you migrate the small catalog, LrCC won't be able to match up the synced assets and this will result in duplicate assets( only if you have synced assets from LrClassic before ). After the migration, when you turn on sync in LrClassic, LrClassic will not be able to match up the incoming assets with the ones which it has already, since the catalog doesn't have any information that it has been migrated( because you migrated the smaller ones, but now you are using the original one). This might result in some copies to be created. 

Below is the answer to your specific questions
1 ) Migration always uses originals, not smart previews. Smart previews are generated after importing the original file. Hence if the count is correct, then you should have the original files atleast locally. It is possible that the files have not been uploaded yet. If you have many files, original upload can take time. You can see the status of sync by checking the cloud icon on the right top of the application.
2 ) Assets along with metadata/xmp will get migrated before album migration starts. If your migration fails at the album migration phase, then below are the ones which have got affected/not-migrated.
  1. Albums : Some albums will not be present. Even the ones migrated will be empty.
  2. Root-album assets : the auto-created album which is supposed to contain all the migrated assets for that session
  3. Stacks
  4. If you are using the same original catalog of LrClassic, when you open it next time in LrClassic, it will know that the migration has been started and it was not completed. Hence it might warn you when you try to switch on sync.
Photo of Hannes Hess

Hannes Hess

  • 25 Posts
  • 3 Reply Likes
I just tried to migrate again with LR CC 1.1 and cleansed up library. And again  it crashes with that same ridiculous error message when trying to migrate albums.

I am so unblievably frustrated I am about to throw my laptop out of the window. Argh!

I am really about to go into LR Classic and delete all my collections there, toss it all in the trash and redo all my albums from scratch. But I don't even know if that would help anymore

Please help
(Edited)
Photo of Asha M.J.

Asha M.J., Computer Scientist

  • 54 Posts
  • 7 Reply Likes
Ah... I thought you have deleted the problematic albums already( the ones from iPhoto). Where is it failing at? Could you please send me the logs to my mail id?
Photo of Hannes Hess

Hannes Hess

  • 25 Posts
  • 3 Reply Likes
I wiped the cloud again completely. I guess Aperture and iPhoto must have produced some more crap in collections. Actually I noticed that there was a collection and a sub collection inside that and they had the same name. Maybe such kind of thing messes it up to. Also I noticed that the Aperture import created a bunch of collections sets but put the actual photos all in collections called Project Photos (which I have 100's of).

I don't know and don't care anymore. I will completely redo my collections from scratch now in LR Classic and then try another go. If that fails again then bye bye Cloud.