Temporarily unable to repair corrupt catalog

i'm running the current version of lightroom. it is giving me a dialog box that says:
temporarily unable to repair corrupt catalog
lightroom encountered problems reading or writing from disk when attempting to repair catalog
the operation may succeed in future attemps
if you wish to try again, please first check available disk space and close all other applications
each time i try, the same dialog box appears.
the corrupt catalog is located on a 1tb drive, 554gb used / 357gb free
what can i do to fix this?

I presume you don't have a recent-enough catalog backup (?)
I bet you won't let that happen again..
Anyway, depending on what's wrong with the catalog, you may be able to recover develop settings (only) via a plugin called WreckHover (free, by me).
In addition to catalog, settings may be stored in:
* xmp if you've saved metadata (if not, I bet you won't let that happen again either) - recovered when importing new photos, or reading metadata (Library menu) of already-imported photos.
* exported versions (if exported with all metadata) - you can recover settings from those via the same plugin: WreckHover.
Note: you'll need to restore a backup catalog first, or start a new one if no backups (really?).
Good luck,
Rob

Similar Messages

Cannot repair corrupted catalog.

My Mac crashed in the middle of editing images in Lightroom 5. It just completely froze (no keyboard lights, no cursor moving, etc.) and had to have a hard shut down. I didn't get the option to submit a crash report. When I reopened at first it said it couldn't write to the catalog because it was on an external drive, but the second time I opened the catalog it simply said that it cannot open due to an unexpected error. I looked online for solutions and I do not have a .lock file in the folder (so it's not that) and when I try to open it while checking for catalog integrity it says to repair it, but then says it is temporarily unable to repair corrupt catalog. I've tried copying the catalog to a new location to see if that would do the trick, but no dice. Does anyone have any suggestions!? I just lost a week's worth of work from my friends' wedding! Argh!

I presume you don't have a recent-enough catalog backup (?)
I bet you won't let that happen again..
Anyway, depending on what's wrong with the catalog, you may be able to recover develop settings (only) via a plugin called WreckHover (free, by me).
In addition to catalog, settings may be stored in:
* xmp if you've saved metadata (if not, I bet you won't let that happen again either) - recovered when importing new photos, or reading metadata (Library menu) of already-imported photos.
* exported versions (if exported with all metadata) - you can recover settings from those via the same plugin: WreckHover.
Note: you'll need to restore a backup catalog first, or start a new one if no backups (really?).
Good luck,
Rob

Cannot Repair Corrupt Catalog

I just switched to Lightroom today, spent the entire day migrating 25,000 images from Aperture. Just as I finished, I got an error that said the catalog needs to be repaired, but when I tried to repair it, Lightroom gave a message that it is corrupt and cannot be repaired. What can I do to fix this? I moved the images, so they're not even in the original folders anymore -- everything is in the Lightroom catalog. Since I just did this today, I haven't made a manual backup. Does Lightroom create backup catalogs? If so, where can I find them?

I did the old shut-down-and-reboot a few times, but the third time it worked. I was able to repair the catalog. Frightening that Lightroom is so unstable that this would happen. I had (and still have -- not giving up) high hopes for my new photo cataloging program.

I try to drag a photo folder into lightroom 4 on my MAC, lightroom fails to open and a 'Corrupt Catalog Detected' screen pops up. Clicking on 'repair catalog' does not work either. Any suggestions?

I try to drag a photo folder into lightroom 4 on my MAC, lightroom fails to open and a 'Corrupt Catalog Detected' screen pops up. Clicking on 'repair catalog' does not work either. Any suggestions?

I'll have to get a better instructor on deleting the preferences since when I've doen it in the past nothing is there when I open LR the catalog is gone. I assumed that was what was supposed to happen so I start importing all over again. But that is a different issue...
The problem has been happening since at least the beta of 3 came out and I saw other posts back then saying they had similar issues but I assume it was a beta thing... But since the full version came out and through each incremental change I haven't seen an improvement. If anything it has gotten a little worse with time.
I have to try to be careful to not be in a hurry and start clicking around in the catalog as it seems fragile until it has cataloged all the photos in the library. When starting you will see the numbers populate the folders very slowly and I try not to click on a folder that hasn't had the number of photos pop up yet. Also draging the slider down to see more of the cataloge can have the same affect and crash the system.
I wish I had more to go on.. I believe it may be a resources issue but as I went from 3-4 Gig I thought it would get better. I don't have big programs running but did have outlook and word running in the background along with firefox and chrome.
And yes it only happens on this HP desktop (it's 2+ yrs old) and may be showing it's age a bit. My laptop which has less resources doesn't have the issue.. I have them sharing the catalog. (not at the same time) just when I'm working in other places in the house.
Jeff

Can't tranfer pics from iPhoto to photo shop elements keep getting cant be completed because current catalog is corrupt attempt to repairing file- catalog...dialog

CCan anyone show me hoe to repair my catalog?

thnks Barbera I believe that's the problem ...every time I try to import the new pics I put in my iPhoto to my elements organizer
after it goes through all the pics to be impotred to the organizer ,it leaves me that message I stated earlier about a corupted file..I'm going to try what you told me about the repairing process and go from there ...I'll be in touch to let you know If that fix the problem....thx again....

LR2 Experienced System Crash & Corrupted Catalog - Need Help!!!

We are using: Mac OS X Version 10.5.8
Background on Lightroom Use:
The size of the catalog in question is 296 MB.
Pictures on an 8GB smart card were being uploaded into lightroom and simultaneously moved into a folder on an external hard drive at the time of the crash. (During this download, the imac screen gave us a very scary...."Death Veil" that started at the top and slowly covered in a downward motion the entire screen, freezing up the computer completely.)
The error message said we needed to restart the computer using the restart option or shut the computer down using the on/off switch.
Since the computer was "frozen" we were unable to access the restart option so we hit the off switch, holding it down until the imac shut itself down.
After waiting for approximately a minute, we restarted the imac.
The imac started as it usually does, however, when we opened Lightroom2, the following message appeared:
After Selecting the "Repair Catalog" Option the following message appeared:
Other catalogs are operating properly in LIghtroom.
We have no available backup and are looking for someone who can assist with
perhaps fixing the corrupted catalog. (Literally, thousands of hours)
Mahalo Nui Lo

If you ever ran "Save" on a lot of images, you'll have all your edits and metadata for those images, and if you ran save recently on the whole catalog of images, you'll be pretty well off. In such a case, I'd start a brand new catalog, and Import in place all the images.
However, assuming the worst, that the above avenue won't yield much, one particular Adobe employee, Dan Tull, is a whiz at repairing catalogs, and you may get it done by sending the catalog to him. From a post long ago: Dan Tull can be contacted at dtull-at-adobe.com .. .. note that @ has been substitued with -at- in above email address .. I haven't seen Dan in this forum for a while, so it's not a for sure thing.
With best wishes,

Unable to repair degraded Virtual disks in Storage Spaces under Hyper-V 2012 R2 Core

Hi all,
I am finding myself in the following conundrum. I have a storage pool under Hyper-V Core, with 2 2TB Seagate drives.
One of the drives completely died (wouldn't spin up, tried it in a different box, still to no avail). I sent it in to Seagate for warranty replacement, got the new drive. Installed it and went through the notions of adding it to the pool and retiring the
one that was with "Lost Communication" status.
Tried to repair the virtual disks that are showing as "Unhealthy-Detached", quickly get 100% complete, but the repair didnt work.
The storage pool is in degraded state.
Looks like metadata is corrupted.
Followed this post to upgrade Storage Spaces to latest version:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/eead59e9-5e49-4bb6-8cbb-1dafddd9576b/unable-to-repair-degraded-virtual-disks-in-storage-spaces-2012r2?forum=winserverfiles
Still, to no avail.
Couple of questions:
1) Is the data on the 3 virtual disks in state "Unhealthy: Detached" not recoverable?
2) How can I get the storage pool back to "healthy"?
Any help will be greatly appreciated.
PS C:\corefig> Get-PhysicalDisk | ? OperationalStatus -ne OK | fl
ObjectId : {1}\\HV001\root/Microsoft/Windows/Storage/Pr
oviders_v2\SPACES_PhysicalDisk.ObjectId="{95
42513c-a0d4-11e3-8123-806e6f6e6963}:PD:{7e22
245f-0cf6-11e3-b1db-806e6f6e6963}"
PassThroughClass :
PassThroughIds :
PassThroughNamespace :
PassThroughServer :
UniqueId :
AllocatedSize : 1218696970240
BusType : Unknown
CannotPoolReason : In a Pool
CanPool : False
Description :
DeviceId :
EnclosureNumber :
FirmwareVersion :
FriendlyName : PhysicalDisk-1
HealthStatus : Warning
IsIndicationEnabled :
IsPartial : False
LogicalSectorSize : 0
Manufacturer :
MediaType : UnSpecified
Model :
OperationalStatus : Lost Communication
OtherCannotPoolReasonDescription :
PartNumber :
PhysicalLocation :
PhysicalSectorSize : 0
SerialNumber :
Size : 1999575711744
SlotNumber :
SoftwareVersion :
SpindleSpeed : 0
SupportedUsages : {Auto-Select, Manual-Select, Hot Spare,
Retired...}
Usage : Retired
PSComputerName :
PS C:\corefig> get-physicaldisk
FriendlyName CanPool OperationalS HealthStatus Usage Size
tatus
PhysicalDisk4 False OK Healthy Auto-Select 73.75 GB
PhysicalDisk0 False OK Healthy Auto-Select 1.82 TB
PhysicalDi... False Lost Comm... Warning Retired 1.82 TB
PhysicalDisk2 False OK Healthy Auto-Select 930.75 GB
PhysicalDisk3 False OK Healthy Auto-Select 74.53 GB
PhysicalDisk1 False OK Healthy Auto-Select 1.82 TB
PS C:\corefig> get-virtualdisk -friendlyname 'Data' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2229cf-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = CF29227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 548413636608
DetachedReason = Incomplete
FootprintOnPool = 1096827273216
FriendlyName = Data
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1099511627776
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Backups' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e22255e-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = 5E25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 743566213120
DetachedReason = Incomplete
FootprintOnPool = 1487132426240
FriendlyName = Backups
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1649267441664
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Music' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2238b9-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = B938227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 39728447488
DetachedReason = By Policy
FootprintOnPool = 79456894976
FriendlyName = Music
HealthStatus = Unknown
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = True
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 161061273600
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =
PS C:\corefig> get-virtualdisk -friendlyname 'Videos' |FC
class CimInstance#ROOT/Microsoft/Windows/Storage/MSFT_VirtualDisk
ObjectId = {1}\\HV001\root/Microsoft/Windows/Storage/Providers_v2\SPACES_Virt
ualDisk.ObjectId="{9542513c-a0d4-11e3-8123-806e6f6e6963}:VD:{3debf056-01f1-11
e3-b1d6-001fbc081884}{7e2225bc-0cf6-11e3-b1db-001fbc081884}"
PassThroughClass =
PassThroughIds =
PassThroughNamespace =
PassThroughServer =
UniqueId = BC25227EF60CE311B1DB001FBC081884
Access = Read/Write
AllocatedSize = 223606734848
DetachedReason = Incomplete
FootprintOnPool = 447213469696
FriendlyName = Videos
HealthStatus = Unhealthy
Interleave = 262144
IsDeduplicationEnabled = False
IsEnclosureAware = False
IsManualAttach = False
IsSnapshot = False
LogicalSectorSize = 512
Name =
NameFormat =
NumberOfAvailableCopies =
NumberOfColumns = 1
NumberOfDataCopies = 2
OperationalStatus = Detached
OtherOperationalStatusDescription =
OtherUsageDescription =
ParityLayout = Unknown
PhysicalDiskRedundancy = 1
PhysicalSectorSize = 4096
ProvisioningType = Thin
RequestNoSinglePointOfFailure = False
ResiliencySettingName = Mirror
Size = 1759325978624
UniqueIdFormat = Vendor Specific
UniqueIdFormatDescription =
Usage = Other
WriteCacheSize = 0
PSComputerName =

Hi omon_77,
You can first refer the following step by step third party article and KB:
Replace Failed Disks and Repair JBODs for Storage Spaces in Windows Server
https://technet.microsoft.com/en-us/library/dn782852.aspx?f=255&MSPPError=-2147217396
Replacing a failed disk in Windows Server 2012 Storage Spaces with PowerShell
https://www.hodgkins.net.au/storage/replace-failed-disk-in-storage-spaces-pool-with-powershell/
Step By Step: How to Replace Faulty Disk In Two-Way Mirrored Storage Tiered Space
http://charbelnemnom.com/2014/09/step-by-step-how-to-replace-faulty-disk-in-two-way-mirrored-storage-tiered-space-storagespaces-ws2012r2/
More information:
Storage Spaces - Designing for Performance
http://social.technet.microsoft.com/wiki/contents/articles/15200.storage-spaces-designing-for-performance.aspx
Storage Spaces Overview
http://technet.microsoft.com/en-us/library/hh831739.aspx
Windows Server Storage Spaces: What is it and why should I use it?
http://curah.microsoft.com/5049/windows-server-2012-r2-storage-spaces-what-is-it-and-why-should-i-use-it
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Photoshop Elements 9 Organizer corrupts Catalog with program crash in offset 000253da

I have just installed Photoshop Elements 9 on a Windows PC (no previous version was installed) but when I try and load photos into the organizer either from a camera or photos already on hard disk I get the following error shortly after Organizer has generated the thumbnails :
Elements 9 Organizer has encountered a problem and needs to close
Error signature
AppName photosopelementsorganizer.exe AppVer 9.0.0.0 ModName tbb.ddll
ModVer 2.2.2009.1011 Offset 000253da
Following this error the program closes and the catalog is left in a corrupt state so that when Organizer is restarted it crashes again with the same error. The only way to get Organizer to start cleanly is by creating a new catalog in the Catalog Manager window by pressing [Ctrl] [Alt] and [Shift] in the Welcome Window when starting Organizer. Repairing the catalog does not resolve the corruption.
I have tried un-installing Photoshop Elements, then re-installing, downloading the latest updates from Adobe and then loading in just one photo from either my camera (Pentax k-x) or a file on the Hard Disk, but still get the same catalog corruption.
Can anyone help? The Organizer is unusable with this fault. My Windows XP operating system is at the latest fix level and all other software on this machine is extremely robust.
My system information is :
Elements Organizer 9.0.0.0
Core Version: 9.0 (20100905.m.9093)
Language Version: 9.0 (20100905.m.9093)
Current Catalog:
Catalog Name: Catalog Dave 6
Catalog Location: C:\Documents and Settings\All Users\Application Data\Adobe\Elements Organizer\Catalogs\Catalog Dave 6
Catalog Size: 129KB
Catalog Cache Size: 25KB
System:
Operating System Name: XP
Operating System Version: 5.1 Service Pack 3
System Architecture: AMD CPU Family:6 Model:10 Stepping:0 with MMX, SSE Integer, SSE FP
Built-in Memory: 959.5MB
Free Memory: 230MB
Important Drivers / Plug-ins / Libraries:
Microsoft DirectX Version: 9.0
Apple QuickTime Version: 7.13
Adobe Reader Version: 9.3
Adobe Acrobat Version: Not installed
CD and DVD drives:
D: (DVD+RW RW5240 BUS: 1 ID: 1 Firmware: 1.19)

Try the solution here:
http://feedback.photoshop.com/photoshop_family/topics/photoshop_elements_9_cd_program_purc hased#reply_5626978

Unable to 'Repair Disk' due to Error message

Routine check on the state of my HHD using Disk Utility - Permissions chks all ran fine and good, but not completing the Verify Disk process. The log file (below) was generated:
_Verifying volume “Macintosh HD”_
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
*Incorrect number of Extended Attributes*
Checking volume bitmap.
Checking volume information.
*The volume Macintosh HD needs to be repaired.*
*Error: The underlying task reported failure on exit*
1 HFS volume checked
*Volume needs repair*
unable to Repair Disk unless the full Verify Disk process has finished, is there an easy fix option, or does it signify a bigger problem?

Were you booted up from your install disk when you ran Disk Utility? If not, you'll need to try that and see if the disk can be repaired. If it can't, and you don't have a recent clone that is not damaged to replace the contents of the startup disk with, then Disk Warrior is the best option.
Francine
Francine
Schwieder

DiskUtility unable to repair

For a few months now, whenever I run "Verify Disk" on Disk Utility, it's given me a message saying something about BitMap having problems, and telling me to run Repair. Unfortunately, when I run repair, it tell me it is unable to repair the disk.
Just recently, I also got this message after "Verify Disk" not only turned up bad results, but it couldn't finish verifying.
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
*Volume Bit Map needs minor repair*
Checking volume information.
Checking volume information.
t",0)
*(It should be 3822613 instead of 3822612)*
*The volume Macintosh HD needs to be repaired.*
*Error: The underlying task reported failure on exit*
*1 HFS volume checked*
* Volume needs repair*
First of all, what can I do about this? Secondly, I don't have the money to buy Disk Warrior or similar software. I'm also totally fine with re-installing the OS as long as it will totally solve the problem, and I have a foolproof way of backing absolutely everything (this includes emails) up.
Thoughts? I really need help.

Disk Utility cannot repair the drive that booted the computer. Grab your OS installation disc or your system restore disc and boot up with it. After you get to the screen where you choose your language, go up to the menu bar and find the option to run Disk Utility. Now you can repair the drive because you didn't start up with it.

Corrupt Catalog Files. Can anyone help please?

My computer shut down unexpectedly, and now Lightroom 5 is giving me and message stating Corrupt Catalog Files. When I try to repair as suggested it says it has encountered problems reading or writing from discs when attempting to repair. Can anyone help please?

How recent is your backup?

Lightroom 5.5 corrupt catalog detected

LR 5.5 has corrupted my entire catalog. LR will not open. It appears to have occurred after I sorted my database by number of stars. Is there a tool or precedure to fix this?
Thank you.

Hello,
I managed to recover my broken catalog and recovered (most) of my development. I described it in my blog, but it is only availible in german language (google translate may help you) right now. http://mein-lightroom-tag.blogspot.de/2014/02/einen-katalog-reparieren-welchen.html
If you have a lot of developments you might try to repair your catalog... Good Luck!

Lightroom Corrupt Catalog problems- Help!

Lightroom Corrupt Catalog problems reading/writing from disk when attempting to repair - Help! I have my LR box in hand and my product keys and license info but can't find the disk. I'm assuming this is the only way to repair. Suggestions, Comments are welcome and appreciated.
Thanks in advance!!!

Corrupt catalog will not be fixed by re-installing the Lightroom software (although if I were you, I'd still find that disk!)
If I were you, I would first check a recent backup of your catalog file, and see if that will open (double-click on it in your operating system). If that opens properly, I would just use that file.
If it doesn't open properly, then one trick that sometimes works is to open a blank catalog in Lightroom, then File->Import from Another Catalog and point to the catalog file.
And if that doesn't work, please write back with a lot more details, including operating system, version of Lightroom, and much more detail abou

PSE7 Organizer Corrupt Catalog?

I think my catalog must have gotten corrupted, but not sure.
Can't get my sync to work properly with on line backup. I have been trying for about two weeks, now.   It used to work.
It keeps wanting me to tell it which picture I want to keep, the one on the computer or the one on line, yet NO MATTER WHICH CHOICE I MAKE, it comes back about an hour later asking the same question.
Tried writing down the file names, then manually go to both my computer and on line storage and delete both files.
Tried repairing the catalog even though it said there were no problems.
Tried optimizing, and checking thumbnails.
I have so much time invested in this program, I'd like to figure out an answer.
Can you help?

Your idea seemed to help for awhile. I saw more of the arrows in green than I have seen in a long time.
However, there is one picture that has come back 3 times and another twice. Each time I instructed the Resolve Conflicts window, choosing the X on my hard drive. I believe that means it should remove it from on line backup, right? (by the way, there is no thumbnail of a picture -- just blank space)
In the past hour the total of files ON MY HARD DRIVE and he total of files in ON LINE BACKUP    h a s   n o t   changed.
I did a lot of clean up of files the past few weeks, (deleting doubles and pictures I decided I didn't want to keep) but none of the deletions had any effect on the on line files. 902 MORE FILES ON LINE than on my computer.

Repair corrupt catalogue in new Lightroom CC?

Can I get some help/instructions on how to repair a corrupt catalogue in the new Lightroom CC please?

Try repairing the catalog. The catalog can be repaired by going to File->Manage Catalogs. Select the current catalog and then repair/optimize the catalog.

Temporarily unable to repair corrupt catalog

Similar Messages

Maybe you are looking for