Lightroom 3 corruption

Hi,
I had Lightroom 3.2 set up on my laptop (XP SP2). I went of on holiday and used it to set up a new catalougue for the photos I was taking while on holiday. That worked fine until Wednesday when something happened and Lightroom kept locking up on me. I have tried various things without success so on my return, I decided to remove Lightroom and start from scratch. I have done so (with 3.6 like on my desktop) but it still locks up. I was working from a removable drive so I have disconnected that drive on the basis that it should start as a fresh installation with a blank catalogue. Having removed and reinstalled again, it still locks up.
I would be grateful for any advice.
Thanks.

Do you get an error message? Do you get a blue screen? Do other programs work when LR locks up?
Try deleting your preference file. http://forums.adobe.com/message/4306647

Similar Messages

  • 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

  • Lightroom corrupting RAW files? Hardware issue?

    I've started having some issues with RAW files being corrupted when I open them in Lightroom. I've done a lot to troubleshoot and narrow down the symptoms, and here is what I can tell you. If anyone has any ideas for how to solve this, I'd really appreciate it!
    Equipment
    Canon 7D, 1 32GB CF card, 1 4GB CF card
    Lenovo Laptop, Win 8; Lightroom 4
    Dell PC, Win7, Lightroom 5
    Here's what the corruption looks like in my Library view. Note that all of the photos are the same. I just rapid-fired a bunch of shots down the hallway to test this out.
    I first noticed the corruption on the PC, pulling photos from the 32GB card. I bought a new hard drive (SSD hybrid), installed a clean version of Windows 7, and upgraded to Lightroom 5, then the 5.3 update. I re-downloaded some photos from the 32GB card, and they still show up corrupted. So here is my further testing:
    I shot a series of photos like shown above on the 32GB card, downloaded them on the laptop with a new USB cable. The photos look good.
    I shot a series of photos on the 4GB card, downloaded them to the laptop with the same cord, they look good.
    I imported the same photos photos from the 4GB card and from the 32GB card on the PC with my existing Lighrtoom Catalog and they are corrupted.
    I created a new Lightroom Catalog on the PC and downloaded the same photos from the 4GB card and from the 32GB card on the PC and they are corrupted.
    So what gives? I think we can rule out corruption or issues on the hard drive, the OS, the USB cable, and both of the CF cards. It baffles me that a new HD, clean OS install, new catalog, new USB cable, and upgraded Lightroom haven't solved the problem. Is it possible that there is some other part of the hardware on my PC which is corrupting the files?
    I'd love some insight if folks have any ideas!
    Thanks,
    Adam

    Was this ever figured out AdamCohn?  I have a very similar issue.  I have actually watched two photos over the last two days become corrupt while viewing them in Lightroom.  I am not suggesting LR is the cause (as I know this is almost always hardware related) but it has happened right in front of my eyes while LR is interacting with the images (I believe).
    Scenario:
    Images were
    * Imported into LR on different days (about a week apart)
    * Imported to different hard drives during import (one an SSD, another to a typical HDD)
    * Behaving normally in LR until corruption (i.e. previews were built without issue, was able to develop and export images. Showed fine in Finder).
    After viewing the images in Loupe view and watching them flip instantly to a visual mis-mash similar to what you showed the images were permanently screwed.  The appear the same way in Finder and in Photoshop
    I have not noticed any other issues in any other app or area of the system.  Everying seems to be running smoothly.
    Troubleshooting:
    * Memory tests:
      - Built-in Apple memory test (normal + extended).
      - MemTest (as described here: MemTest for Mac OS X Tests your RAM). Ran it twice, all tests passed.
    * I am running some HDD checks now, but with the two images being on two different drives I suspect the likelihood of this being a drive issue is extremely small.
    Suggestions?

  • Lightroom Corrupt Files

    Within the last couple days, I have come across an issue in Lightroom. When transferring photos from PhotoMechanic to Lightroom, the file becomes corrupt. The issue comes when the file is brought into Lightroom (and even Photoshop).
    I have an inkling it is something to do with my computer. I have used multiple memory cards. And tonight following the game, a colleague of mine imported the photos onto his computer through both PhotoMechanic and Lightroom with no issues to any image.
    Equipment:
    Canon 1Dx
    MacBook Pro (Retina, 15-inch, Early 2013)
    Here's what it looks like in my Library view:
    Here is how the file looks in PhotoMechanic (left):
    Lightroom is updated to the latest 5.7 version and Camera Raw is updated to the latest 8.7 version. My colleague, who's computer everything worked correct on, was using the same version of both programs.
    I can rule out that it is not the memory cards, camera body, memory card reader. I feel that it is something within my software or the laptop itself.
    Any help would be appreciated.
    Thank you,
    Brace

    It will not be the software. BTW Photomechanical just uses the jpeg previews in the file not the raw data.
    Are you sure it is not the car reader or cable?? How did you rule this out??
    I would suggest the ram may be faulty or the hard drive is failing but probably ram. Take it to Apple.

  • LightRoom corrupting issue

    All of a sudden I'm having weird color issues in LightRoom 5.7.1.  running on Mac Yosemite. 
    I'm getting blue and red spots popping up on my images but the raw images are unaffected and I do not see this issue in Photoshop.  Any ideas?Lighr

    The reason for this is your have the overexposed and underexposed areas warning on in the histogram. If you look at the histogram you will see the right and left indicators highlighted.
    If you click on them it will toggle on and off. The blues indicate areas of total underexposure and the reds totally blown highlights.  

  • Files get corrupted in Lightroom 4, through 4.4

    So I was going to comment on one of the other posts about the corrupted files but it was soooo long I decided to start a new one.
    This should give me a hint that it is not HARDWARE....
    To start with I am shooting a Canon 5d mkIII and RAW(.CR2) files
    A slight kink in everyones generic answer that it is a hardware issue; I reproduced this on two computers using the same .cr2 files copied from the same original downloaded files.  Lightroom corrupted files on import on both computers.
    Also to test the answer it was corrupt before it went into Lightroom.  I always copy the raw .cr2 file to my laptop and then to a external drive from the laptop directory, not from the compact flash.  I looked at a .cr2 file with Photoshop and it was fine.  Then I imported that same file with all of the other .cr2 files in the directory into Lightroom 4 and it was corrupt along with many others. 
    My disappointment is that when I tried to open the same .CR2 file, that was fine a moment earlier with Photoshop, it too was corrupted.  I thought Lightroom was non-destructive to the original file.
    I deleted that .cr2 file and restored the backed up file that was a copy of the original and imported that single file into Lightroom and it was now fine.
    Sorry but not acceptable.

    Replying to myself:
    I digged into some reverse-engineered CR2 specifications on the net and found 5 things:
    Canon uses a lossless compression in their CR2 files. So that suspicion was confirmed.
    The algorithm does not seem to have changed substantially in later models. So that suspicion was not confirmed.
    Before doing the compression, the raw photo is divided into vertical slices. Usually 2 or 3 slices, it seems, though I am not sure). This seems to explain why we sometimes see a corrupt lower quadrant of a Canon photo.
    According to one source, the image is "interlaced" before compression, so all lines with RG information are kept together, as are all lines with GB information. Based on that, I would expect to see photos with every second line corrupted, if we could see the photo prior to demosaicing. But since we only see the photos after demosaicing (which involves combining information from several lines), that is not really relevant.
    The compression algorithm used is Lossless JPG which uses Huffmann encoding for compression. This seems to me like a method which has good corruption potential.
    The long version of my reasoning for the corruption potential of Lossless JPEG + Huffman encoding (just skip it if it is too boring):
    I have heard about Huffman encoding many times before, but I have never bothered to find out how it works. This thread was a good reason to bother, so I finally did it.
    Lossless JPEG works by predicting the value of each pixel based on the pixels above it and to the left of it. The difference between the actual pixel value and the prediction is then stored as a prediction error. The original pixel values can then be thrown away because the raw decoder can precisely reconstruct them from the prediction errors and knowledge of the prediction method used.
    This means that it is only necessary to store the prediction errors in the file. Even though the original pixel values will be very different, a lot of pixels will have the same prediction error (close to zero). This makes it easier to compress the prediction errors than the original pixel values.
    The prediction errors are compressed using Huffman encoding which works sort of the same way as international dialing prefixes (this is a comparison I have come up with myself):
    There are more than 100 countries in the world, so we sometimes have to use a 3 digit prefix. But we don't use 3 digit prefixes all the time. For example, USA is +1 and Denmark is +45. So when you punch for example '+4512345678', how does the phone system know that the international prefix part of the number is exactly +45 and not +4 or +451?
    The answer is that one international prefix is never used as the first digits in another international prefix. So +10, +11 ... +19 and +100, +101 ... +199 are never used as international prefixes because USA already have used +1, and +451, +452 ... +459 are never used because Denmark have already used +45.
    Huffman encoding works in the same way. Instead of having a lookup table with dialing prefixes of different length and their corresponding countries, it has a lookup table of bit codes of different length and their corresponding prediction error. Each bit code can never be used again as the beginning of a longer bit code so the encoder will always know where one bit code ends and the next begins, even though they are of different length.
    This means that the well predicted pixels can be stored with just a few bits instead of storing them as a full 14 bit value. Just like USA can be dialed with +1 instead of using full 3 digit code of +001.
    But it also means that decoding will fail miserably if just one bit is switched. Switching one bit in a bit code will usually mean that the length of that bit code will be misinterpreted, and that means that the decoder will look for the start of the next bit code in the wrong place. So from that point in the bit sequence, we can expect everything to go wrong.
    (Sorry to be so long winded. But reading about Huffmann is like getting a new tool - I just have to use this knowledge for something.)

  • Bug - Lightroom 3 - CD/DVD drive corrupted

    I have an issue that has been tested and proven to be Lightroom related whereas installing Lightroom, and updating to v 3.3 has caused my cd/DVD RW drive to be lost and corrupted.
    The following notes and  timeline are a little long, but they fully explain the situation. If  anyone has had this issue or knows about a fix I would appreciate a  reply:
    I will also add that I am a little peeved at the tech for Adobe customer support because he tried to brush me off after a few basic steps and told me the problem was a Windows issue. He said that Lightroom was installed on thousands of PC’s, and if the problem was Adobe’s there would be other people with the same issue… That was a presumptuous statement; as there is always the first case of a bug, and just because I was the first one to either have or report this problem, it did not justify Adobe leaving me cold. There is now a case number on this issue after further testing and my insistence that he escalate the case because I had already determined that it occurred at the precise moment I installed Lightroom. the Adobe Case # is 0181989673
    Problem Timeline:
    After installing Lightroom 3, I discovered that CD/DVD Re-Writer drive was not working for Lightroom exports, I was seeing the notice at the bottom of theexport window stating “Disc Burning is not supported by lightroom on this computer” (The same as in the V 2.2 Bug)… As well, I looked in Windows > MyComputer, and the CD/DVD RW drive was missing.  I looked to the device manager. The CD/DVD Writer was listed in the tree but had a yellow exclamation notice. I Confirmed Error Code (I beleive it was code 31) for Driver not loading properly or corrupted.
    I did some research and found the following information at http://support.microsoft.com/kb/982116
    I followed the instructions as listed below (inset)... Timeline continued after.
    Your CD drive or DVD drive is missing or is not recognized by Windows or other programs:
    Problem description;
    Your CD drive or DVD drive is missing or not recognized by Windows or other programs, so you cannot play or access a CD or DVD. This issue might have occurred after you installed, uninstalled, or updated a program or Windows Vista.
    Windows XP
       1. Click Start, and then click Run.
       2. In the Open box, type regedit, and then click OK.
       3. In the navigation pane, locate and then click the following registry subkey:
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE 10318}
       4. In the right pane, click Upper Filters.
          Note You may also see an Upper Filters.bakregistry entry. You do not have to remove that entry. Click UpperFilters only.If you do not see the Upper Filters registry entry, you still might have to remove the Lower Filters registry entry. To do this, go to step 7.
       5. On the Edit menu, click Delete.
       6. When you are prompted to confirm the deletion, click Yes.
       7. In the right pane, click Lower Filters.
          Note If you do not see the LowerFilters registry entry, unfortunately this content cannot help you any further. Go to the "Next Steps" section for information about how you can find more solutions or more help on the Microsoft Web site.
       8. On the Edit menu, click Delete.
       9. When you are prompted to confirm the deletion, click Yes.
      10. Exit Registry Editor.
      11. Restart the computer.
    Now go to the "Did this fix the problem?" section.
    Did this fix the problem?
    Is the drive listed?Windows 7 Click Start , click Computer, and then see wheth...
    Is the drive listed?
    Windows 7
    Click Start
    Collapse this imageExpand this image
    Start button
    , click Computer, and then see whether the drive is listed.
    Windows Vista
    Click Start
    Collapse this imageExpand this image
    Start button
    , click Computer, and then see whether the drive is listed.
    Windows XP
    Click Start, click My Computer, and then see whether the drive is listed.
    If the drive is listed, try to play or access a CD or DVD.
    If you can play or access a CD or DVD, you are finished with this article.
    If you cannot play or access a CD or DVD, you may have to reinstall some programs. Some programs might not be able to use your CD or DVD drive until you reinstall those programs. If the problem occurs again when you install or uninstall those programs, contact the manufacturer of the program to see if an update is available that solves the problem. Some examples of programs that might be affected are:
        * iTunes software by Apple
        * Nero software by Nero Inc
        * Roxio Creator software by Sonic Solutions
        * Zune software by Microsoft
    After reinstalling your programs, if you can play or access a CD or DVD, you are finished with this article.
    After performing above procedures the CD/DVD drive loaded (Plug and Play) successfully and was recognized at a basic level. I re-installed the authoring software (Ashampoo Burning Studio 6). At this time I could read and write to DVD via Ashampoo; but still, I could no longer write to either CD or DVD via Windows XP.
    Also at this time; I could still no longer write to CD or DVD via Lightroom 3.3 using export and choosing CD/DVD… Lighroom was still listing at the bottom of the export window “Disc Burning is not supported by lightroom on this computer”.
    This brings me to the point at which I called Adobe Support; Case # 0181989673
    Adobe tech had me perform the following:
    Pull     the preferences folder out of Lightroom 3.3 folder and re-start Lightroom…     Problem still present
    Open     Lightroom from the Administrators User account; import a photo and try to     export and burn to CD/DVD… Problem      still present
    At this time the tech told me it was a Windows issue; NOT an Adobe issue; and that I would need to take it up with Microsoft, or just export to hard drive and burn to CD/DVD afterward using authoring software.
    I immediately told the tech that was NOT acceptable because this issuewas caused by installing Lightroom 3.3; and although the problem now existed in Windows; that did not wash Adobes hands of it. I requested that the case been escalated to a senior tech… I did not at all appreciate the idea of being left in the middle and I also did not appreciate the notion of having a CD/DVD writer that was buggy and not performing as it should.
    He told me "Lightroom was installed on thousands of PC’s, and if the problem was Adobe’s there would be other peoplewith the same issue"… To me, that was a STUPID statement; as there is always the first case of a bug, and just because I was the first one to either have or report this problem, did not justify Adobe leaving me cold.
    The     tech decided to try creating a new Windows XP user account as     administrator and re-test Lightroom for burning to CD/DVD… Problem still present
    Tech     instructed me to un-install and Re-install Lightroom. I un-installed     Lightroom. After taking screen shots of my preference settings (since I     would need to re-set all settings again). I uninstalled Lightroom.
    At     this time; though the tech did not think of doing it; I decided to try and     burn to CD/DVD via Windows to see if the problem was gone after removal of     Lightroom. Now, with Lightroom removed, I can write to CD/DVD in the     conventional way using drag and drop via Windows.
    I      told the tech what I had done; proving that this was in fact related to      Lightroom. He stated the case would be escalated and gave me the case      number.
    I hope this taught the tech a lesson in troubleshooting and hope he will not be so quick to assume “Not an Adobe issue” as the exact cause of this anomaly has not been determined yet... Now I have not re-installed Lightroom yet. I would like for the senior tech who takes this case to contact me to give me further instruction because I have no reason to believe re-installation will not cause me problems again and want the tech to witness the result.

    This problem has been resolved. I haven't heard from anyone else who has had the same issue, but in the event anyone does I can say what corrected it and I have a theory of what might have happened. Originally I installed Lightroom from the disk and after installation chose to update. After this is when the problem with the CD/DVD drive showed up. The tech at Adobe said they did not know what could have caused it, but recommended re-installing Lightroom to see if it happened again.
    I did some research and found information at Peachpit: Having trouble burning CD/DVDs in Lightroom 2.2?
    about a bug that was present in version 2.2 where the installation executable was accidentally installing the 64 bit drivers on the 32 bit system... The 64 bit drivers were corrupting the installation... On a hunch that it could be a similar issue, I downloaded Lightroom version 3.3 from Adobe and installed it rather than installing from the original CD. I did the install following the same instructions on the Peachpit post which was to double-click the Adobe Photoshop Lightroom 2 folder, then double-click the setup32.exe file rather than double clicking the default installation executable.
    I did not prove the above theory of the version 2.2 bug to be the cause, but the problem I had with the CD drive appeared after the original installation and went away after I uninstalled that installation of Lightroom. Now after re-installing as explained; the problem is gone.

  • Using Lightroom 5.7, Raw files become from my Nikon D810 become corrupted when I select them to view or edit.

    .Updated to Lightroom 5.7 to accommodate the Nikon D810. Upon importing RAW files to the files become corrupted when they are selected to be viewed or edited.
    I am using Windows 7, 64 bit, with 8 GB Ram.
    Any help would be appreciated.

    There are several likely sources of corruption, and video card would be far down on my list of possible suspects.
    The transfer from camera card to hard disk is the most likely place for problem, either the card reader or USB cable can go bad. Another likely source of problems is the computer's hard disk is starting to fail. The camera card itself may be bad. And lastly, the memory in the computer may be malfunctioning.

  • Lightroom and corrupted tif files.

    For some reason, now when I right click on tif file in windows I'm getting a pop up box that states;
    Explorer. Tif:corrupt file.
    This applies to all tif files on all drives.
    I first noticed this with imported to lightroom from raw pef files, processed and then exported from light room.
    it also includes files opened from Pentax RAW files, processed with ACR and CS2 then saved as tiffs.
    any ideas?
    Simon.

    No. I'm running XP and my files are Pentax PEF raw files and tiffs created from these.
    Tiffs opened from a cd are fine - as are tiffs copied to my PC from cds. It's as if windows has decided that there is a problem with all tiffs on the machine.
    double clicking them - they open fine in CS2.
    If I right click to get the menu - then the error message clicks in.

  • Images getting corrupted in Lightroom 4.2

    I have experienced this aswell. As mentioned in:
    http://forums.adobe.com/message/4138626
    and http://forums.adobe.com/thread/948417?tstart=0
    My lightroom has after two weeks of playing with a fully working raw file corrupted it.
    This is what the photo looked like originally http://500px.com/photo/14737987
    As of today, I tried to reexport it with a diffrent watermark, the raw file corrupted. It exports a corrupted jpg and when I delete the .xmp metadatafile and try to import it again (same happens with it now when trying to import it to photoshop) the raw file now renders as corrupted in all software.
    I have tried every possible way to reimport it, its just plain broken. If this should happen to my whole portfolio I would cry.

    Here's evidence that LR is rewriting an entire JPEG file when I add metadata and do Save Metadata To File, just as Rob has described.
    First, I imported a JPEG in which all the metadata had been stripped using Exiftool.  Exiftool's dump shows that the image data starts at around hex offset 10:
    Immediately after importing, I did Save Metadata To File, and the image data now starts at around hex offset 0cf0:
    Next I added a short caption and did Save Metadata To File, and the image data now starts at around hex offset 0dd0:
    I used the Microsoft Sysinternals' Process Monitor to trace file reads and writes to the JPEG file while LR was doing Save Metadata To File, and that confirms it is writing the entire 1 MB file:
    Obviously, if there's a hardware fault anywhere in the path from the disk to memory and back, the contents of the image data could get corrupted.
    And just as Rob has patiently explained, the fact that the file could get rewritten doesn't constitute any criticism of LR.

  • Any new fixes for corrupt images in Lightroom 4.4?

    I have seen many threads on this and tried a lot of the tings people say to try. But I do get corrupt images in Lightroom. I currently have an AMD FX-8150, 32GB ram, 2 SSD Raid0 + USB3.0 drives as backup.
    Drive and Memory:
    Note, I only keep up to the last 3 shoots on my SSD, the rest are stored on my USB3 drives. Any time I import files to the USB drive I get no corruption. Now that would imply that I have bad drives, I have run diskcheck and contacted Muskin and they had me run some disk checks, speed tests, +other things and identified that the drives are running fine with no issues and this has to be a software issue.
    I have run memtest86+ with no errors, also ran memtest86+ with my memory in another machine with no errors.
    To rule out the card reader:
    When I just copy files from my CF Card to a folder using explorer all images import fine and you can even open every image in photoshop with no issues. As soon as you add those files already copied to the HD to lightroom, they start to corrupt. I just recently used the windows explorer method and added ~400 images to lightroom, all images imported fine, when I later accessed lightroom(Today), about 10% of those images are not corrupt.
    Does anyone have any suggestions? Could it be because I use Raid0? Or even SSD drives?
    This is quite annoying and I would like to get things fixed.

    jproductions111 wrote:
    Usually when Lr renames the photos as you saw kianjillwedding-19, Lr changed the name from IMG_1968. Thats may have something to do with the corruption.
    I don't see how. Renaming shouldn't change anything on disk except, well, the name - and of course update a bunch of things in the catalog.
    jproductions111 wrote:
    I will get back to you if the problem continues but everything still seems to be fine in Lr5, even after letting Lr rename all the photos with my current(today's) import of 700 images.
    OK - thanks.
    jproductions111 wrote:
    I know you don't believe its software
    ~impossible it's Lr4 software. Theoretically possible, but highly unlikely. As I said, Lr4 should never be rewriting those files, and therefore essentially can not corrupt them. I mean, its possible that it got it's brains scrambled, and went ahead and rewrote them, for god-knows why or just for the he|| of it - because some bits seemed to be set wrong..., thus invalidating the assumption that it's not rewriting them. It's just that this scenario is the least likely. I mean, Jeff Schewe has given me spankings more than once before, for even bringing it up, since it's so unlikely...
    jproductions111 wrote:
    maybe Lr 4 was causing some sort of bug to make the hardware malfunction
    Although theoretically possible, I'd still venture to guess that's not what happened.
    jproductions111 wrote:
    this is not happening to my in Lr5.
    Didn't you also change your disk drive situation around just before you started using Lr5?
    jproductions111 wrote:
    But I am keeping my fingers crossed.
    Me too - please keep us posted...
    R

  • Lightroom 3 Corrupting .CR2 RAW files on import

    I have never used RAW files before yesterday.  About to shoot a wedding in a couple days so desperately need a fix or at least some advice for a workaround. 
    Here's my hardware list:
    Canon 7D
    SanDisk Ultra II 2 & 4 GB CF cards
    Windows 7 64x
    Internal card reader, not some flimsy USB thing
    Lightroom 3
    Problem:
    After importing .CR2 RAW files using Lightroom 3, not Bridge, I found that some (not all) of the images appear to be corrupted.  On the camera they look fine. 
    For a short moment, in Lightroom, they look fine, but then after clicking the thumbnail they instantly develop strange corruptions, like pink/yellow/opaque static. 
    This is not one of my photos, but the corrupted image looks just like this: http://thekuipers.org/images/IMG_2279.jpg
    Used some advice and downloaded Fast Picture Viewer, which allows me to view the .CR2s in the folder I imported to, and MOST of them look fine now.  Reimported to LR and now only like 8 of 200 images are corrupted.  They still export to .jpg as corrupted.
    I had formatted my CF cards immediately after importing, only to find the corruptions after.  Using Stellar Phoenix Photo Recovery to try to reimport manually the residual data from CF cards.  Will know if that works soon.

    From previous posts on this forum there are several things that can cause this type of corruption on import; faulty, CF cards, card reader, cable, and RAM.
    On my system it turned out to be faulty ram. Since changing my ram I have not experienced any further problems.

  • Lightroom 1.4 catalog corrupted after installing/uninstalling 2.0

    Hi all,
    I have about 10,000 images in my catalog, including thousands of edits made in the last week. I installed version 2.0 yesterday, but because of numerous problems (very slow, slider problems, etc) I got rid of it and tried to revert to 1.4.1
    Unfortunately, ever since doing so, somehow my database has become corrupted and I can't regularly export catalogs. Sometimes they work, most times they don't. Most of my edits are very substantial and I've spent days working on a few of them so I can't risk anything major. I never had the opportunity to backup the catalog either (backups were turned off by default on this install).
    SO. Is there ANY possibility of un-corrupting this database or have I just lost months of work keywording ?

    Which is fine, but it's the version 1 catalog that has corrupted. I deleted the version 2 catalog after removing the software from my PC. I'm able to navigate within my catalog and make changes, etc, but exporting anything is hit or miss, and more hit than miss. If I choose to export x number of images as a catalog it will start the process, but within about 3 or 4 seconds will error out saying "Lightroom wsa unable to export the catalog. Unrecoverable error when generating export catalog." Nothing further to aid in troubleshooting.
    This never happened before I installed the new version of the software. V2 seems to have modified it in some way upon import, or else co-incidentally something else happened to it at the same time. Either way, I can't export several groups of altered Nikon NEF images. I tried exporting the catalog without including the actual image files but no-go there either. The originals are safe (thank goodness), but the edits can't be moved, and some of them took hours of tweaking to accomplish.

  • Lightroom 1.4.1 Has anybody experienced corrupt print driver using Mac OS X Tiger

    Hi folks,
    I am starting to pull hair out! Whilst nearing the end of a print run for a wedding customer, my HP B9180 has begun to print what looks like dark lines on 'some' areas of my prints. I have done all that I can to resolve this but to no avail! i.e. Ink levels OK. Printer test sheet perfect. Print heads re aligned and cleaned anyway. Print done from Mac itself, such as iPhoto and 'Preview' - result= perfect print. Go back to Lightroom and the same happens, I am at a loss and just eight images away from finishing the job!! HELP!
    Any ideas gladly received. Is it worth trying a fresh install of Lightroom? Any one had a similar experience?
    Paul
    Oh yeah: B9180 printer (with latest firmware). MacBook Pro running OS X Tiger and Lightroom 1.4.1.
    A perfect combination for about a year . . .up until now!

    I don't recall reading any previous reports matching your description. Have you tried deleting the LIghtroom preference file to see if that helps. Occasionally, it can become corrupt.
    See linked article for location of preference file http://forums.adobe.com/thread/358041?tstart=0

  • 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.

  • LightRoom 1.3.1 corrupts DVD/CD-ROM device driver

    There is a device driver corruption bug in the new LightRoom 1.3.1, and it is observed if you upgrade from LR 1.3.0. Following a reboot after the updating installation of LR 1.3.1, the device driver for an external USB DVD/CD-ROM device will get corrupted, as noted in the Windows Device Manager. This was not a problem with any of the prior upgrades of LR from 1.0 through 1.3.0.
    My environment is Windows XP Professional SP-2 on a Lenovo X60s ultra-light laptop. This laptop does not have a DVD/CD-ROM device built-in because of it size. So, I have an externally powered DVD/CD-ROM player/burner device that plugs into one of the USB ports. As long as I am using LightRoom 1.3.0, everything works fine for whenever I plug-in and access my external USB DVD/CD-ROM drive. I can leave the external device plug-in and reboot, or use the USB dismount of the device and reboot and then plug-in the device, or any combination of these steps and the external device will continue to work.
    When I install the LR 1.3.1 upgrade, as long as I don't reboot, I can run LR 1.3.1 and it will work fine and so will the external device. I can dismount the USB DVD/CD-ROM device and then plug it in again and it will still work fine and so will LR 1.3.1, just so long as I do not reboot after installing LR 1.3.1. As soon as I reboot the computer, even if done immediately after only installing LR 1.3.1, and regardless of whether or not the external USB DVD/CD-ROM device is plug-in, after the reboot, the Device Manager will indicate that the device driver for the DVD/CD-ROM device is corrupted.
    In order to isolate the cause of my device driver corruption problem, I had utilizing the Windows Restore Point capability. I am able to step back to a very recent Restore Point where LR 1.3.1 had not yet been installed, and I am able to plug in and dismount at any time my external USB DVD/CD-ROM device and always be able to use it without any problems. I can also reboot the computer and the USB DVD/CD-ROM device will continue to work without any problems, whether it was left plugged in or if I hot plug it in after the computer has fully rebooted.
    For the record, I used different files and different methods for updating LR from 1.3.0 to 1.3.1. One method was to use the update feature within LR. Other methods used included two different downloaded *.EXE files to do the update without LR open. No matter which method was used to update to LR 1.3.1, the corruption of the device driver was always the same after a reboot.
    I also did test installs to be sure that other applications didn't cause the same problem. I can confidently report that I updated four other applications and rebooted and the USB DVD/CD-ROM drive continue to work just fine. One of the updates was the latest Adobe's Flash Player.

    Yu may want to review your system to see if you are getting the same error as I did. If not, then just send them the correct information.
    Here is exactly what I wrote - you just need to change what CD/DVD drives you have on your system:
    'I can not get either of my CD/DVD drives to work. I have tried to uninstall and reboot system for Windows to pick them up. I can not rollback or update the driver as it is not finding the files. They see the drives under Computer Management, but I get this error: "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)"
    I need to have the inf files and do not have access to the cd you sent as all the drivers are down. Can you resend the inf files for the "CD/DVD 1" & "CD/DVD 2"?'
    Hope this helps - Dan

Maybe you are looking for