Corrupt LR Catalog!(?)

I´ve got 133.300 picture on a 2 TB HD. The catalog is on my laptop. Some of my pictures are only to be seen in the Library mode. When I go to Developent mode I´m told, that "The folder could not be found"
The píctures are counted in the keyword list.
Some has gone wrong with the catalog file - but what? And how can I fix it?
The problem occured after a sudden stop in backing up the catalog file caused by mistaken disconnection of my external HD.
Please help me
Thank you in advance.

Are there question mark icons on your folders, or question mark or exclamation point icons on your photos?
What version of Lightroom?
What operating system?

Similar Messages

Hyperlinks Corrupting in Catalog...Help...

I have indesign CS3...I have built about a 40 page book with navigation bar that is on the master page...
I have made buttons out of colored shapes, that i turned each into a button with a certain page as it's anchor...there is then a text layer an the page layer just above those buttons.
No matter how i export this as a PDF...the text layer above the buttons disappears...the tabs work, but not with text...
HELP...

Hyperlinks Corrupting in Catalog...Help...<br /><br />Thanks for the reply...Here is = <ahref=http://www.strongholdstudios.net/ee/images/CLIENTFILES/DESCRIPT.jpg><br />a visual explanation...TIA for the help...<img height=3D"1267" =<br />width=3D"1072" apple-width=3D"yes" apple-height=3D"yes" =<br />src=3D"cid:8EA760FD-8835-4683-A674-5D725C96E0F3"><br><div =<br />apple-content-edited=3D"true"> <span class=3D"Apple-style-span" =<br />style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =<br />Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =<br />font-weight: normal; letter-spacing: normal; line-height: normal; =<br />orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =<br />white-space: normal; widows: 2; word-spacing: 0px; =<br />-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =<br />0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =<br />auto; -webkit-text-stroke-width: 0; "><div style=3D"word-wrap: =<br />break-word; -webkit-nbsp-mode: space; -webkit-line-break: =<br />after-white-space; "><div>Sincerely,</div><div><br></div><div>Matthew =<br />Gaylor</div><div><br></div><div>Director of Design</div><div><a =<br />href=3D"http://www.strongholdstudios.net">http://www.strongholdstudios.net=<br /></a></div><div>C: 541.821.8208</div><div><br></div><div>"You name the =<br />style...</div><div>We make it your =<br />brand."</div><div><br></div><div><br></div><div><br></div></div></span><br=<br />class=3D"Apple-interchange-newline"> </div><br><div><div>On Feb 26, =<br />2009, at 5:25 PM, Kelly Vaughn wrote:</div><br =<br />class=3D"Apple-interchange-newline"><blockquote type=3D"cite">A new =<br />message was posted by Kelly Vaughn in <br><br> <b>InDesign Macintosh</b> =<br />--<br> Hyperlinks Corrupting in Catalog...Help...<br><br> =<br />Are those text frames set to non printing? Or or they on a non-printing =<br />layer? Or perhaps they the text frames themselves are buttons with the =<br />setting of "Hidden in PDF." <br><br>How about if you upload a screen =<br />shot to help us understand you better? I'm puzzled as to exactly what =<br />you mean. <br><br> <hr width=3D"200" align=3D"left">View/reply at <a =<br />href=3D"<a href="/webx?13@@.59b80d0b/0">Kelly Vaughn, "Hyperlinks Corrupting in Catalog...Help..." #1, 26 Feb 2009 5:25 pm</a>">Hyperlinks =<br />Corrupting in Catalog...Help...</a><br> You must visit the conference to =<br />reply. Email replies are not allowed and will be returned.<br> Use the =<br /><a =<br />href=3D"http://www.adobeforums.com/webx?280@@.59b80d0b!folder=3D.ee6b330">=<br />unsubscribe</a> form to cancel your email =<br />subscription.<br><br></blockquote></div><br>

Lightroom 3.6 Crashes and Corrupts My Catalog

I just updated to Lightroom 3.6 on my MacBookPro running OS 10.6.8. The application now acts weird in many ways, including slow scrolling through library grid thumbnails, blank thumbnails, no way to link missing photos to the corresponding files, and worst of all, crashes that corrupt the catalog. Can anyone help? This seriously affects my photography business, and I can't work without a functioning Lightroom catalog.
Thanks.

This morning I installed Lightroom 3.6 on my MacBook Pro with 2.66 GHz Intel Core i7 CPU and 4GB of RAM runnin OS 10.6.8 -- and it was unbelievably slow (beachballing while going between images in Library mode, etc.) and froze up twice in less than 10 minutes of use. Horrible! It seems to be even worse when opening in Develop mode.
I followed the link given in the thread above and downloaded LR 3.5 and installed it, which was a totally painless process, and (this might help the techs figure out what is wrong) it installed in FAR less time than 3.6. I did not have to delete 3.6 before downloading & installing 3.5, it just seems to have automatically overwritten/reverted to 3.5.
Cheers
Adam

Corrupt Lightroom Catalog

I was recently working on a Lightroom 4 catalog that was saved on a G-Drive when the hard drive failed. I was able to recover the catalog using data recovery software, but now when I try to open it, Lightroom says it's unable to open due to an unexpected error. I've tried renaming the catalog, importing from a new catalogue, and opening various ways, but nothing works. The catalog seems corrupt. Help! Is there any way to recover the catalog?

The message you are getting could be caused by the presence of the so-called lock-file. The purpose of the lock file is to prevent that a catalog file can be opened twice at the same time.
Therefore it should be present when a catalog has been opened with/by Lr. But the lock-file should be deleted (automatically) when the catalog has been closed by Lr. It happens sometimes that on closing of a catalog, the lock-file is not deleted, particularly when Lr does not close down but is interrupted by a crash or hardware failure. The lock-file then prevents any further opening of this catalog and Lr sends the message you are getting.
With Lr closed check in Mac Finder / Win Explorer if you can find a lock-file. The lock file sits directly besides (i.e. in the same folder) the catalog file in question.
The catalog is a file with the extension < .lrcat>; the lock-file has the extension < .lrcat.lock>
If - for instance - you have a catalog file named <123xyz.lrcat>, the lock-file would have the name <123xyz.lrcat.lock>.
If, while Lr is closed, you see a lock-file, delete it, i.e. send it to the Trash Can / Recycle Bin.

How do I repair a corrupted Organizer Catalog?

The repair function under "Catalog Management' seems to never finish. I get disk activity but no completion. The optimize function behaves the same way.

I had hoped that Catalog Restore from a Backup would fix what appears to be a corrupted Catalog and fix my shut down problem.
I guess I will need to go a different route to fix the problem. However, right now I am stumped as to which way to go. Catalog "Repair" and "Optimize" both appear to run forever.
Maybe I will just need to put up with the problem until something magic happens.
The "Bring Up Task Manager and Shut Down Photoshop" work around is workable. However, I fear the problem will progress.
I was here once before but I don't remember what fixed the problem. It may have been migration to a new computer.

Corrupted LR5 Catalog - help with SQLITE

Hi, I use LR5 on OSX and my catalog got corrupted when the hard drive filled up. As it turns out, backups stopped in April for some reason.
Techniques I've tried so far include:
1) look for back-ups
2) copy to a new location and use that file
3) import into a new file
4) have Lightroom repair it
5) restart the system....
I have been through the forums and it seems the only thing that seems to have a hope of succeeding is a SQLITE software to extract the data from the .lrcat file and to produce a new one with it. Unfortunately the little software is not very user friendly and I get about as far as "syntax error".
Does any one here have any experience with these things? Please let me know if you have any further ideas.
Regards,
Wolfgang

Hi Rob,
Thank you for getting me this far. It's taken for ever, but I am now the proud owner of a new .lrcat catalog.
However, Lightroom does not recognise it as valid and does not open it.
I am lost again and need some more ideas here. I hope its some minor formality or so.
Wolfgang

How to repair a corrupt LR catalog?

While I was importing photos from an SD card using a Promaster card reader using an iMac OSX computer, I suddenly got the spinning beach ball. After several minutes, I realized that the computer and LR program were completely frozen, and the only alternative was to turn the computer off. After I turned the computer back on, I ultimately got the message, "the LR catalog is corrupt and cannot be used or backed up until is is repaired. The box had 'repair operation' so I clicked on it and ultimately got the flat message , "The LR 2 Catalog' is corrupt and cannot be repaired at this time." I'm completely at a loss as to what to do at this point and would appreciate any advise.

Just remember to copy the backup somewhere else before you open it, so its not a backup anymore - otherwise you could end up trying to backup your backup into your backup and end up with a bigger mess than you had to begin with...

OK. I might have a corrupt LR2 catalog. What do I do now?

So, now it's taking me gobs of time to import anything into my new LR2 catalog. How do I fix this? I have run the utility on it and it's still in trouble. This was a library that I had upgraded from version 1.4. I've already done a lot of work in this new catalog and I don't just want to import the old one again. Is there some way I can export stuff and re-import it into a new fresh catalog?
Thanks.
Antonio

You could just export the entire catalog to a new catalog.

Can I delete these files (see screen shot) after a catalog restore?

I have Photoshop Elements Organizer version 9.0.3.0 and am running Windows 7 64-bit SP1.
After I got a new computer, I created a backup of my catalog (via the file drop-down menu in Elements Organizer).
I then restored the catalog to my new computer (via the same drop down menu in Elements Organizer). It went fine and my catalog is just as I left it.
Now I'm trying to clean up the look of things in my "My Pictures" folder (I'm a little OCD, lol). The restore made a folder within a folder within a folder... so I was wondering if I can delete all these files that the restore made? (see screen shot) This is the entire contents of one of the folders the restore created. The other folder just contained all my photos by themselves.
I don't know what all those folders do, so want to make sure they will not damage/corrupt my catalog or the organizer if I delete them. I will later make another back-up, of course. I'm hoping that all these files will just recreate themselves? I just want to delete them so I can get rid of so many excess folders in my "My Pictures." I just like to click "My Pictures" and have my pictures be RIGHT THERE. It's annoying to have to click through like 4 folders to get to them after this catalog restore.
Thanks for any guidance!

@99jon,
Thank you for your help! And, dang it, I did choose a custom location for the restore. The instructions I was following said to do that (I didn't really know what I was doing so I made sure to follow them to a 'T'). Looks like the file path for the catalog *is* pointing to that folder in the screen shot of my original question here.
So does this mean there is no way to delete them? I wish I could just start fresh (but of course still have my catalog with all my images and the right categories/keyword tags, etc). I don't mind the wait for regenerating things or moving things and stuff.
I don't remember ever seeing all those breeze files and cache files, etc, on my old computer. I never saw any files of the sort until I did the back-up.... of course, maybe that's because they were stored somewhere other than right inside "My Pictures?"

4_4 LR4 update corrupts cache?

I've been using LR4 since it came out, with few problems. Transitioned to a 64-bit computer (Win7) two months ago, and the few problems I had went away. And then.....(sigh) on April 15, I downloaded the latest update to LR4. Since then, Any catalog I open will get a corrupt cache error within a minute of opening - at which time it corrupts the catalog in use (and of course, it's not repairable). If anyone knows of a way to downgrade (and please do NOT say "reinstall") please advise. This is simply unusable at this point.

yes, the preview cache is easily fixed. But that's NOT the problem. when LR quits, I then reload, at wich point I'm told the catalog is corrupt. Attempt to repair, and it cannot.
Just got off the phone with Adobe - they are aware of the 4_4 problem (to me, that would indicate that they should pull it from downloads, but they haven't), and to "just reinstall".

Backing up Catalog problems

I have lightroom set to ask to backup my catalog after closing the program. Recently when asking to backup there have been some problems. The first dialog box shows up and I press backup. But then the same dialog box shows up again. If I press backup or cancel it corrupts that catalog every time. I don't know if this matters but my catalog and pictures are all on an external drive.

Hi,
Does your catalog consists of video files as well?
If yes, please try taking the backup without the video files.
Also, please go to Preferences (Ctrl +K) > Media Analysis Tab and un check all the boxes.
Relaunch Organizer and now try taking the backup.
Thanks,
Anwesha

Catalog file on a network drive - case/scenario proof?

I know this has been been in debate for years, but the local photog group I'm with is getting into a good discussion on why putting the catalog on a network drive should be a good thing.
So being the resident IT pro, I went on twitter and both Adobe and Pete Green both say there are some scenarios that influenced the decision not to allow such awesomeness but haven't backed up their claims at all.
Can anyone prove and/or provide the full list of the scenarios claimed by the LR team?
I have built a bulletproof server rig:
Full rack battery backup, dual & redundant links to the iSCSI array in Raid10 + high speed ECC caching + hot spares on a stacked set of switches (6 links - split 3 per switch) Dual bonded NIC's from the server (two links per switch)
The workstations have dual bonded nics (1 link per switch) SSD drives inside for improved caching and performance.
Case for failure? Small, very very very small. The reliability and availability level of the servers are spot-on for a robust system that runs at about 800MB/sec. If that's not enough, Lightroom needs some serious redesign.
I have run filemaker, directory replica, and MySQL database servers on just Mac Minis! Even after an accident with not plugging it into the correct side of the desk UPS, it is still running fine to this day. So, in my experience, the claims for corrupting the catalog due to server/network failure is no longer viable unless some newb photographer tries to use a LR catalog from a wifi shared hdd in the middle of a storm.
So, am I on the right track or what?

chattphotos wrote:
So, in a nutshell, the use of SQLite and no plans to cast to multi-user MySQL (the defacto standard of databases) is what is holding LR back from becoming a very useful multi-platform, team-friendly, and workshop-oriented editing suite.
No, look at what they're doing with Lightroom Mobile and particularly its browser-based sibling Lightroom Web, then consider where the underlying tech might allow them to go.

Lightroom 4.4: Only 3 thumbnails will display at a time in both Grid view and the Film Strip

Hi. I have Lightroom 4.4. and Windows 7--both of which have been working fine for several months. Starting a few days ago, however, thumbnails have refused to load for any NEW photos I import. They appear gray/blank in both Grid view and the film strip. However, if you click on any of the film strip thumbnails (while in either Grid view or Develop mode), that thumbnail and corresponding image WILL load--until up to three have done so. Then they begin disappearing again, allowing you to view no more than three images' thumbnails at any one time.
I can't review a shoot via Grid mode this way. I'm also afraid to use Lightroom while it's misbehaving, for fear of corrupting the catalog somehow (though all the images appear to be there). Searching this forum, I found several people who experienced having all of their thumbnails blank out and who were able to correct this by either reinstalling or removing their color profiling software. However, 1) I did this (and it didn't work), and 2) it isn't that all my thumbnails that have disappeared. All the thumbnails and images imported prior to the bug, still initially display correctly.* And I can get three thumbnails of the newer images to appear at a time.
*The asterisk is because after I poked around some more, I realized that if I opened other folders and began post-processing images from older uploads (vs. just viewing them), the thumbnails that initially displayed correctly everywhere also blank out and begin appearing in this up-to-three-at-a-time fashion.
Help, please?
With many thanks,
Rita

Alas, it didn't work. I did it twice--the second time rebooting the computer before starting Lightroom. I didn't expect the reboot to make a difference, but I did discover something else in the process: the second time I tried this, I accidentally opened a different catalog--and new photos imported just FINE into that one, thumbnails and all! For one moment I thought the reboot HAD made the difference. However, when I reopened the catalog I actually wanted, the original problem remained. Thumbnails don't load with import, and, when forced, only display up to three at a time.
So the problem seems specific to this catalog.
And yes--thank you for affirming that reinstalling Lightroom wouldn't work, either. (I forgot to mention that's what I had tried first. It didn't help--but it's nice to know it wasn't supposed to.)
Thank you so much for your reply. Do you have any other ideas, please?
With many thanks, truly,
Rita

Hard drive issues...running out of ideas...opinions?

Hello everyone!
Let me start by saying that I love all of my Apple products. I've been able to use an iPod mini, another iPod, an iPhone, a Powerbook G4 and a MacBook with no daily or otherwise recurring issue; however, the reason I now have a MacBook is because the Powerbook G4's hard drive died. Sad, but after 3 1/2 years of problem-free use in college...I could justify the upgrade.
I purchased the MacBook from my university at a nice discount back in March of this year (this was right after the newest batch was released). I was comforted by the fact that I'd more than likely have another 3-4 years before a replacement would be needed. Now, I'm not so sure...
One day last week, a tab that was opened in Safari froze up, and a song playing in iTunes began to hang. I attempted a force quit of both, but with no luck. Eventually I had no other option but to shut the computer down. Afterwards, I began getting the infamous flashing question mark upon booting back up. I realized that I'd probably had some damaged files as a result of the forced shut down, so I began working with Disk Utility/First Aid to correct the problem. Luckily, I had no important files or programs to worry about, so I went for the Erase option and hoped I could just re-install the OS.
Unfortunately it was not that easy. Now my hard drive is not showing up as Verified under the S.M.A.R.T. status, and the volume "disk1s2" will not mount. I tried everything I could find on these boards, still with no luck. So, I went for Disk Warrior today and crossed my fingers. When the menu finally loaded, there were 2 options in the drop down menu: the disk warrior cd, and an Unknown Drive. When I chose the latter, this is what I was met with:
Directory cannot be rebuilt due to disk hardware failure (-36,2268).
I'm almost convinced that I need a new hard drive. However, when I run the Apple Hardware Test, everything checks out fine. I ran it twice. Also, when I run a test on the hardware in Disk Warrior, I get this message:
This hard drive's built-in SMART diagnostics indicate the drive is functioning normally.
Now, with my old Powerbook G4, the hard drive doesn't even show up in Disk Utility. That I can understand. It needs to be replaced. But with this MacBook, all the tests indicate the hard drive is fine. The only blatent message about hardware failure I get is when I try rebuilding the directory with Disk Warrior. I know I'm probably just in denial, but when my computer is only 5 months old...I think I have the right.
So, what is your opinion? New hard drive for the 5 month old MacBook (grrr)? Or is there still hope left?

SMART diagnostics are by no means all-encompassing, so it's quite possible for a drive to pass SMART diagnostics but still be defective. My advice at this point would be to boot from the Installer, go to Disk Utility, and see if you can erase, or if that doesn't work re-partition (normally you'll choose to create a single partition) the drive. A badly corrupted disk catalog might not be reparable, but reformatting may work.
If that also fails, then the probability of the drive being defective is quite high and replacing it will probably be necessary. The tiny drives used in laptops are by nature of their very small components more prone to failure than are other drives, though as capacity and performance rise, even desktop drives are becoming more prone to breaking.
Hope this helps.

OBIEE/EBS R12 - works, except for one user - ORA-06512 error

OBIEE 10.3.1.4 / EBS 12.0.4
Oracle 11g
HPUX 11.31 64 bit Itanium
We are successfully using EBS integration with OBIEE, but for one user that we have created it doesn't work. When they try to access OBIEE from EBS we get this error in NQServer.log:
*[nQSError: 13011] Query for Initialization Block 'EBS Security Context' has failed.*
*[nQSError: 17001] Oracle Error code: 6510, message: ORA-06510: PL/SQL: unhandled user-defined exception*
ORA-06512: at "APPS.APP_SESSION", line 313
at OCI call OCIStmtExecute: call / 101507300 */ APP_SESSION.validate_icx_session('NIOWQbvOlCFpGilcGDvlBIY-:S').*
*[nQSError: 17011] SQL statement execution failed.*
This is when the query is run against EBS to authenticate the user:
select FND_GLOBAL.RESP_ID,
FND_GLOBAL.RESP_APPL_ID,
FND_GLOBAL.SECURITY_GROUP_ID,
FND_GLOBAL.RESP_NAME,
FND_GLOBAL.USER_ID,
FND_GLOBAL.EMPLOYEE_ID,
FND_GLOBAL.USER_NAME from dual
It is only for one user that has the problem. All others users work fine.
Has anyone else seen this problem?
Our EBS DBA has checked that the above sql can be run with the session set to the problem user, and compared with a user who can successfully connect to OBIEE. The results were the same for both.

I was on the wrong lines with this one.
The error in the NQServer.log was not from the problem user, it was a separate user.
The real cause of a specific user not being able to login was a corrupt web catalog (which we're still trying to resolve)

Corrupt LR Catalog!(?)

Similar Messages

Maybe you are looking for