LR026 - Fixing Sync Problems caused by switching the Sync CatalogFixing Sync Problems caused by switching the Sync CatalogWritten Fall 2024 This is part 3 of a 3 part series concerning the sync process between Lightroom Classic (LrC), and Lightroom (Lr or Lr/Cloud) and is current as of Lr/Classic 14.0.1 and Lr/Cloud (desktop) 8.0. Part 1 LR/Classic and LR/cloud Sync behavior discusses how various operations and commands done in Lr/Cloud and Lr/Classic affect synced images. Part 2 Changing Which LrC Catalog Syncs with Lr/Cloud concerns the reconciliation process between Lr/Cloud and LrC when the synced catalog is changed and many of the problems that come from that process. Part 3 (this part) discusses options for fixing Lightroom Sync problems caused by changing the sync catalog. This includes the dreaded “images don’t sync and can’t be made to sync” problem plus many others. Two types of sync problemsThere are two major categories of sync problems. The first is when images are “stuck” in the sync process. In this case the sync status shows an unchanging “xx images syncing”
And the sync activity log (Preferences -> Lightroom Sync) shows a list of items waiting to sync.
The other category of sync problems is different. I don’t have a good name for this category so let’s just call it “Structural” sync problems. In these the sync status shows “synced” with a green checkmark, there are no images in the Sync Activity list
But, when you sync or un-sync some images the sync process seems to function as it should but it doesn’t. Many images (especially newly imported ones) may sync fine while other images have problems. Here are some of the most common symptoms for this category of sync problems
Before you start troubleshooting sync problemsNo matter how careful you are, unexpected things can happen. Even if you are working with Adobe Tech Support, they too make errors. Therefore it is a good idea to take out some insurance before you start troubleshooting ‘just in case”. Backup your catalogBackup your catalog. I suggest copying ALL the files/folders relevant to your catalog to another folder not just the “.lrcat”, and “.lrcat-data” files you get in the backups produced by LrC itself. Create a Sync LogMany times, Adobe requests a Log to help them debug sync problems. These logs are not really meant to be viewed by customers but sometimes they do make interesting reading – especially if you are a techie.
It may take several minutes to generate the report. Take a look at it if you wish by clicking the “Show in Finder/Explorer” button in the dialog box you’ll get when it is done generating (unzip foe report and open the HTML file). But otherwise you can just ignore it for now. Clear or change the default sync folderThis is the folder, specified in “Preferences -> Lightroom Sync”, where the sync process places images which originated in one of the Lr/Cloud apps.
If you are still using the default shipped with LrC, that folder is “Mobile Downloads.lrdata” (not shown in the preferences dialog) and is in the same folder as the catalog but it is not a regular folder with images (on Mac’s it is a package). Rather it is a special format and only really usable by LrC. In this case using preferences you can designate or create a real folder and choose to copy the images from the default folder as part of the process.
Once it’s a real folder, if it has any images in it, either copy them to other folders or use ‘Preferences -> Lightroom sync” to designate a different and empty folder. We do this in case in our troubleshooting Lightroom decides to download a large number of images form the cloud it will be convenient to have them all in one place and not intermingled with previously downloaded images. This does happen. Clear “From Lightroom” Collection setWhen Albums are in Lr/Cloud but are not linked to corresponding Collections in LrC, the sync process creates new synced collection in a collection set called “From Lightroom” (and will create it if it’s not already there). If you already have collections in “From Lightroom” it is a good idea to move those collections to some other collection set.
We do this so that if the troubleshooting decides that the Albums in Lr/Cloud are no linked to their mate in LrC, and as such syncs them all down to LrC as new collections you’ll have them all in one place and not intermingled with previous ones. This does happen. Save your LR/Cloud OriginalsThis is in case the images in the cloud get wiped out as some cloud originals may not have synced to LrC. Images that originated in LrC are still in your catalog, which you just backed up, and those physical image files should also still be in your disk file system as well so we don’t need to worry about those. Here’s how to do this using the Lr/Desktop app.
Save your recently edited LR/Cloud ImagesThis is only useful if you do edits in the Lr/Cloud apps. Again depending on when your sync problems started, most edits have already synced to LrC. However edits done after your problem started may not have synced down to LrC. Those are the ones we’re after. If you’ve made edits in Lr/Cloud that did not synced down to LrC and you’d like to keep them you will need to export them. This can be tricky but you probably know the date where your sync issues started so the ones you want are those edited on or after that date. I don’t know of a way to isolate this to only images that were edited in Lr/Cloud after some date so you’ll wind up with images edited in both Lr/Cloud and LrC after that date.
Troubleshooting ‘stuck’ imagesMost common Lightroom syncing problems are ‘stuck’ images and can be resolved by following “normal” troubleshooting processes and this is not really the purpose of this article but I do suggest following the “before you start” tips near the top of this article before you start. A good description of those normal troubleshooting steps can be found in How to troubleshoot Sync issues with Classic 13.3 and later from “The Lightroom Queen”. In most cases this will get you back to normal. But before you start any corrective procedures, even ones you try on your own, make sure you have a current backup of your catalog as sometimes a fix turns out to make things worse. Before you contact to AdobeOne of the steps at the bottom of the normal troubleshooting is to contact Adobe Tech Support (which you may consider as an optional step). Adobe doesn’t know your catalog or how you are using it and in their eagerness to fix your problem may do something that messes you up or even causes additional syncing problems. So, it’s a good idea to take another catalog BU before you make that call. If the normal troubleshooting has failed to solve your problem, or you have one of these symptoms try these “Advanced” troubleshooting ideas which comprise the rest of this article. Smart Previews invade Catalog Mismatched images Orphan images Un-Syncable images One major cause of these ‘structural’ sync problems (as I call them) which are not resolved by the normal troubleshooting is changing which catalog is syncing with the cloud. Most of these cases stem from changing which catalog syncs with the cloud. If you’re curious of how you might of gotten into your predicament, see Changing Which LrC Catalog Syncs with Lr/Cloud. LOW VOLUME RESOLUTIONSThe solutions described in this section tend to work best when you have a manageable number of images exhibiting the problem. In cases where the number of images with the problem is too large to deal with using these techniques, sometimes an export/import will work. See HIGH VOLUME RESOLTUIONS below. Smart Previews Invade the CatalogThis is most often caused by restoring a backup catalog from awhile ago and making it the sync catalog and is also be caused by switching to an un-related catalog and making it the sync catalog. Smart Previews will invade the catalog when Lr/Cloud contains images originally synced up from an LrC catalog but a newly synced catalog does not contain those images or Lightroom does not perceive that the newly synced catalog contains those images. In these cases the SP’s in Lr/Cloud are synced down to LrC and placed the DSP (“downloaded-smart-previews”) subfolder under the transfer folder (the one designated in preferences to get Lr/Cloud downloads). No Disk file is created for these but the DSP folder is created. BTW, the reason we emptied or re-pointed the default Lightroom sync folder to an empty folder was to prevent these newly downloaded SP’s from being intermingled with ones perhaps already there.
In many cases the SP’s that synced down from Lr/Cloud are duplicates of full size original images already in your catalog in other folders. But in other cases they will be the only version of the image in the catalog. SOLUTION If the SP is the only copy in the catalog, but you still have a full size original on disk someplace
If the SP is a duplicate of an original image still in your catalog and you don’t have too many of them you can do something different. These steps pretty much retain everything except the LrC edit history.
If you are happy just keeping the original still in the catalog you can. But there is a problem as the one synced to Lr/Cloud is the SP in the DSP folder, not the original. As long as the SP remains in Lr/Cloud you may not be able to sync your original. To keep the original (with its edit history and other metadata), but losing any edits done in Lr/Cloud which had not synced to LrC, do this.
Empty CellsEmpty cells are empty grey cells in the gird/filmstrip. Even in normal operations this can occur when images are “missing” and there is no preview in the catalog. But changing the sync catalog can also create missing images in the catalog and sometimes SP’s downloaded from Lr/Cloud need a nudge to show up in the grid and filmstrip. SOLUTION If the empty cell is an SP, take it to the develop module which usually will cause it to appear in the grid and film strip. Empty cells can also be fixed by using your OS to put a copy of the physical file into the folder where LrC thinks it should be or by using the “find missing” tools in LrC.
In many cases ‘Empty Cells” also have no matching image in Lr/Cloud so see the next section if that is also the case. Different edits in LrC and Lr/CloudThis symptom is where the same image is different in Lr/Cloud compared to Lr/Classic. In most cases you will not be able to reconcile those differences through the normal sync process. What makes this problem maddening is that doing further edits using some edit controls will sync fine, but using other edit controls will not sync. In particular, the edit controls that resulted in the differences are not syncable but other controls are. This can occur when you restore from an older catalog where edits had been done on synced images after a BU you reverted to was created and the last such edit was done in LrC. If the last edit was done in Lr/Cloud this problem does not happen. Spooky, huh? NOTE: This result occurred in 3 test runs in November but in December (using the same versions of LrC and Lr) these images all retained their most recent edits in two successive tests as they should. I am leaving this in this article as you may experience this behavior. As I can no longer reproduce this situation I cannot provide a canned solution for how to handle cases where the last edit was done in LrC. SOLUTION I’m sure there are solutions but as I can’t reproduce the problem, I can’t test different solutions so I don’t feel it is proper to include guesses here. If anyone reading this has this problem let me know. However, you can try the Export/Import solution below whish should work but you’ll lose edits not present in the LrC catalog. Orphan Images - No Matching image in Lr/CloudHere you have images in LrC which are marked as being synced, and are in the “All Synced Photographs” special collection but there is no matching image in Lr/Cloud. As it turns out, these images are also un-syncable so see the ”Un-Syncable Images” section below as well.
Un-Syncable ImageThere are two flavors of this problem. In the first, when you edit the supposedly ‘synced’ image, the sync status shows that it is syncing but when it’s done nothing shows up in Lr/Cloud. So it can’t be made to sync. If you then un-sync it (remove from the “All Synced Photographs” special collection) and then add it back to a synced collection it becomes flavor 2 A flavor 2 un-syncable ‘synced’ image is one where if you edit the image in LrC, the sync status shows that it is syncing to the cloud but as soon as it is finished, it becomes un-synced, is removed from all synced collections, and is removed from the “All Synced Photographs” special collection. Again remaining un-syncable. For either flavor, see Export/Import Solution below EXPORT/IMPORT SOLOUTIONThis method can be used but you may lose some edits but it will usually make the image syncable again. If you have the original image still on disk “save metadata to disk”, remove the image from LrC and Lr/Cloud, re-import it to LrC again and re-add it to its synced collections. If you also want to save its participation in collections (other than Publish Service Collections) and retain its edit history you can Export as Catalog (without negative files), remove from LrC and Lr/Cloud, then import from that exported catalog. HIGH VOLUME SOLUTIONSIf there are too many images to deal with using the low volume solutions, take a look at these high volume solution. These are more aggressive and affect the entire set of images but may do the trick. CLEAR ENTIRE CLOUD SOLUTIONThis approach involves clearing everything out of the Adobe Cloud and re-syncing it all from LrC. But, there this is not a perfect solution as there are some negative aspects like losing edit history of edits done in Lr/Cloud (the edits can be kept but not the history)
CLEAR CLOUD & SYNC WITH CATALOG COPY SOLUTIONThis approach involves clearing everything out of the Adobe Cloud, exporting your catalog as a new catalog, and syncing the exported catalog. But, there are some negative aspects to this like losing edit history of edits done in Lr/Cloud (the edits can be kept but not the history), also issues with images in Publish Services, and shared/make public web pages. These steps are basically the same as the previous solution except we first make a new catalog using the ‘Export as Catalog” function and then use that catalog for the step listed above.
GO NUCLEAR AND SWITCH TO NEW ADOBE ACCOUNTThis approach is the last resort if all else fails and you have no more hair to tear out of your head. It involves creating a new Adobe account, and re-syncing a copy of your catalog to the new accounts cloud. But like the others, this is not a perfect solution as there are some negative aspects like losing edit history of edits done in Lr/Cloud.
Hope that helps but if you can’t get it figured out, see my Lightroom help web page for one-on-one private help over zoom.
PLEASE, PLEASE, PLEASE leave comments. This series of articles related to syncing took me over 5 months to perfom the testing and writing the results and it was very complicated and I'm giving it to you for fee. You are not seeing any ads on my website. You did not have to provide a credit card or create yet another account to read this. But, I would truly like to know your reaction. Was it useful? Was it clear? Did you find any errors? Did it help you understand what was going on? Did you come here due to a probllem? Did you use this information to try and solve a problem? Did this help you solve your problem? And, anything else you wish to say.
Keywords:
catalog sync,
danlrblog,
lightroom,
lightroom classic,
lr,
lr sync,
LR Sync Problems,
LR Sync Stuck,
lrc,
Troubleshooting LR Sync,
Un-syncable images
Comments
No comments posted.
Loading...
|