Lightroom wont startup, catalog issue?

When I try to launch Lightroom5, i get a box with "Confirm" at the top and the following inside:
The Lightroom catalog named "Lighroom 5 Catalof" cannot be opened because it is not valid. Would you like to select a different catalog?
THe catalog is not recognized as a valid catalog.
The catalog can be found at
C:\Users\(mycomputer)\Pictures\....\Lightroom5 Catalog.lrcat
Options given as a button is "Choose a different Catalog"    "Exit"
I have tried to choose another, but nothing I have picked works.
WHAT IS GOING ON HERE?!  It worked just fine last week!
Please and thankyou for any help,
B

Went from bad to worse, eh?
Removing toolbar crap shouldn't do it, but ya never know...
Once upon a time, a left-over lock file would keep Lr from starting, but Lr5 is much smarter in that regard (it checks whether the lock corresponds to a real instance of Lr already running, or is just a bogus "left-over" lock file).
Anyway, I'd definitely try re-installing Lightroom, if rebooting your machine doesn't help.
PS - Install Lr5.2 from a download, rather than the CD version (assuming it's 5.0) - it's less buggy.
Rob

Similar Messages

  • Lightroom 4.1 catalog issues.

    I came back from holiday and booted up Lightroom 4.1, which seemed fine. I downloaded the new files, keywording as usual, as DNG files into a subfolder. When quitting Lightroom I backed up as usual. When I next booted up Lightroom my image subfolder was empty, as were the majority of my other folders. The photos are there but Lightroom cannot see them and they are not recorded as missing but when I tried to reimport some folder contents they are grayed out as suspected duplicates. I have backup going back for ages but loading up another early catalog showed the same behaviour. As I have in excess of 100,000 images in the catalog I don't want to have to reimport or build a new catalog, with attendant keywording, if I can avoid it. Am I missing something?

    Some things to try:
    1. Make sure you have selected "All Photographs" in the Catalog Panel
    2. Turn filters off (Ctrl-L once or twice)
    3. If those don't work, select a file name of a photo that had been previously imported into LR, by looking at your photos via your operating system, and then ask Lightroom to find that exact file name
    Oh yeah, just in case Jasonized didn't say it strongly enough ... DO NOT RE-IMPORT, this is a TERRIBLE idea except as a very last resort (which situation we are nowhere near at this time)

  • Lightroom CC wont startup after installation on mac

    lightroom CC wont startup after installation on both my mac's, it only hows a splash screen at startup.
    I have tried to restart the computer
    Anybody know what to do ?

    I'm having the same issue and the log out and back in trick is not working for me.
    I've just installed and when I try and launch the application, i see the splash screen for a split second and then the application crashes.
    It is happening on both of my Retina MacBook Pros.
    One is: Late 2013 Retina 15" MBP - 2.6 i7 - 16GB RAM - 1TB SSD - NVIDIA GeForce GT 750M 2GB
    The other is Early 2013 Retina 15" MBP - 2.7 i7 - 16GB RAM - 256 SSD - NVIDIA GeForce GT 650M 1GB
    Same behavior on both.
    I've uninstalled and reinstalled. I've trashed pref files. Not sure what else to do.

  • Lightroom 5 Catalog Issues

    I've been a LR user since v2 and I've never had any significant catalog issues until LR5.  This isn't so much of a question, more of a statement which I am hoping someone at Adobe reads.  The issues I've recently encountered are as follows...
    Issue 1)  LR5 fails to import Panoramas created in Photoshop CC
    - Select several photos in LR5, right-click and select Merge to Panorama in Photoshop.
    - Once pano is created, click save in Photoshop and then exit.
    - Merged photos fail to appear in LR5.
    - In Finder, navigate to folder and verify newly created panos are saved (as PSDs) in the same folder as source images = Yes
    - In Photoshop, verify "Maximize Compaitibility" setting is checked = Yes
    - In LR open the Import dialog to attempt to import the missing Pano just created.  The pano image is found but is grayed out and I am presented with a message that the photo already exists in the library.
    - Attempt to syncronize folder... LR thinks all 10 photos are missing but sees 11 new photos to add (11 because the of the pano).  Syncronization removes the 10, then adds them back to the catalog but fails to add the 11th, the Pano file.  Successive attempts at sychronizing the folders yield the exact same results (see Issue 2).
    Issue 2)  LR5 thinks all my photos are missing (photo missing message under histogram)
    - Attempts to syncronize a folder yield 100 missing photo and 100 new photos found (100 is just an example).
    - Syncronization removes the missing photos and adds the exact same photo right back to the catalog, however the problems persists.
    - Successive attempts to synchronize the folder yield the exact same results (100 photos missing and removed, 100 new photos added).  LR is stuck in a loop.
    Issue 3) LR5 not creating the correct folder in my folder structure on import.
    - Import is configured to create a new folder for each day (e.g. 2013-07-25) within a year folder (e.g 2013).
    - Upon import LR5 tells confirms it will create a 2013-07-25 folder within the 2013 folder, however upon import the it is actually created in the root photos folder at the same level at the 2013 folder.  In other words, Photos/2013-07-25/ instead of Photos/2013/2013-07-25.
    No photos were ever moved.  No changes to the folder structure were made inside or outside of LR.  And no changes to import pre-sets have been made.
    I've seen issue number 2 on two seperate computers with completely different catalogs.
    I was able to resolve my issues somewhat by importing new photos and manually specifying where in my 2013 folder they are to be stored.  Doing so seemed to remind LR where my photos were and the issues listed above appear to be resolved for now.  That said, I am still receiving the "Photo is Missing" error under the histogram, although the photo counts when I attempt to synchronize the folder(s) are now correct (0 photos missing, 0 new photos to add).

    This has been where Adobe asked people to post bugs but with the demise of the online photo hosting photoshop.com website that shares the same domain name, new user creating may not be working, but you can try:
    http://feedback.photoshop.com/photoshop_family
    Issue 2) is something I’ve seen—the erroneous Missing Photos indication even though I was working on the photos, and exporting them and printing them just fine, without ever having created a smart preview.  I’m glad I read this because I might not have thought about doing a synchronization and having LR5 removing and re-adding the photos, wiping out my edit history.   I can say that the photos I saw as missing, before, are now properly indicated as online so it may be a temporary condition that can be remedied by restarting LR or restarting the computer, though I’ve not really investigated carefully, since it only happened once.

  • Strange Catalog Issue or bug. Help, photos disappeared help?

    My images disappeared in the catalog. They are not missing, they are just not visable. I think there is a bug in the Fliter section.
    Let me explain. I have one Main folder with 5 Sub folders. All those folders contain random amounts of images. (i.e. the path would be...  Photo/2010/BeachShoot, or Photo/2008/PartyPics... etc).
    I imported 5 years of images, hence 5 Sub Folders. I was randomly flagging images to be rejected with the 'x' key. Basically routine maintenance... flag so many, then call up only the rejected photos in the grid view, select all, then delete. Remove the Flag Filter... repeat process over and over...   Basic, simple work...
    Now... doing the exact some thing.. I removed all Flag filters and my images are no longer appearing in the catalog. I tested, by turning on flags, off flags.. etc. The images did not accidentally get deleted. I checked my hard drive location. Images are there. I rebooted the machine, I opened up another catalog, to trick it back... did not work. I tried to re-import the images.. but it says they are already in the catalog.
    Strange part: On the Left Sidebar window, under Catalog "All Photographs" it shows the correct number of photos in the catalog. However... the strange part... Under "Folders" in the Left Sidebar beneath Catalogs my Main Folder shows "Zero" number of images. But, if I click on a sub root folder where the images reside, they number changes from Zero to the correct number of images and my images reappear on the screen as normal..
    The work around... click on every subfolder...
    The solution... Unsure? Help!
    john
    Strange Catalog Issue or bug. Help, photos disappeared help?
    System: Mac OS X 10.7.2
    Lightroom 3.6

    We all get there sometimes Glad it was so easy!
    Beat

  • Lightroom 4.4 video issues, I think it may be a windows 8 issue.

    I am not sure when this started happening or what has changed.  I went to import some video and in the import dialog box all my video files show "Preview unavailable for this file" in the thumbnail in the grid view.  And if I try to import them i get a dialog box with a message that says Import Results > Some import operations were not performed. > There is a problem with the video file (1) > [Filename].AVI
    I am currently using windows 8 and I have imported video to this catalog before from the same camera.  The video plays fine in the video players(windows media player, quicktime, and the new video app on windows 8 that is the default player in the OS).
    I went throught the http://helpx.adobe.com/lightroom/kb/troubleshoot-video-issues-lightroo m-4.html and did all those suggestions.  I am now turning to the forums before I reach out to support.
    Has anyone else run into this issue or a simililar one that may be able to give me a workaround or solution?
    I am a cloud subscriber and all my programs are up to date.  Windows is current, all players are current, and this specific catalog has .AVI files in it from the same camera and the firmware on the camera has never been updated since I started shooting video.
    Thanks,
    Alex

    I had the same problem -- also on Windows 8. I was trying to import .MOV files from an Olympus OM-D E-M5 into Lightroom and got the error you mentioned.
    I believe it was a problem with my QuickTime installation. I was using an unofficial distribution of QuickTime called "QT Lite", and apparently it doesn't play well with Lightroom. Uninstalled that, installed the latest QuickTime and video imports started to work.
    Unfortunately I then ran into this other problem, which sometimes causes video editing to fail: http://forums.adobe.com/thread/972420

  • G5 Wont Startup

    Hey Guys!
    So I have a G5 tower that wont startup. Heres whats going on:
    -When I try to start it up normally it gets to the spinning grey wheel then turns off.
    -Resetting the PRAM does nothing. I might need a new PRAM battery but I'm not sure if that explains the symptoms. I ordered a new one though, should be here soon.
    -When I try to boot off a Tech Tool Pro DVD I get a kernel panic screen, that says You need to restart your computer. Hold down the Power button blah blah blah... The text on the screen ends with BSD process name corresponding to current thread:kernel_task
    -Tried to boot off the Tech Tool DVD with the HD unplugged, same error.
    -When I try to start up in safe mode it stays on the spinning grey wheel for a couple of minutes, then turns off.
    -In single user mode ran fsck -y and it returns:
    disk0s3: I/O error.
    Invalid node structure
    (4,275)
    **Volume check failed
    /dev/rdisk0s3 (hfs) EXITED WITH SIGNAL 8
    and then says
    'PowerManagement emergency overtemp signal. Going to sleep!'
    Over and over.
    -I reset the nvram in open firmware earlier, which did nothing, but now when I try to start up in open firmware the screen just stays black and nothing happens.
    -Earlier, booting in verbose mode would return some errors, then shut down immediately, but now its just goes to a black screen as well.
    -Resetting the PMU didn't do anything.
    -Switched the RAM around, so I'm pretty sure its not a problem with the RAM, or the RAM slots.
    Any ideas on what's going on or what I should do next? Or should I just wait for the new PRAM battery? Thanks for helping!

    Any areas I should concentrate on?
    CPU heatsinks, Video card, RAM, Fans, Power supply.
    about a foot away from my 10' sub. Could that have caused the damage?
    I wouldn't think so, at least yet.
    So how would I go about fixing the HD? TDM maybe?
    Yes, but I think we have to take care of the heat issue first.

  • Lightroom wont start after crash

    hi..
    playing with lightroom3 i had a bsod during building a webgallery..
    since this crash lightroom wont start any more.. lightroom starts directly in the webgallery screen and then lightroom tries to rebuild the webgallery previews, the mouse coursor turns into the waiting icon and lightroom gets lightgray and isnt responding any more.. no chance of klicking cancel on this action or switching screens, cause lr is not responding...
    i tried to start without a catalog or with a fresh new one -> the same...
    can i start lightroom in the defalut library screeen?? or is there a lightroom action cache which i can delete???
    i am using lightroom3 x64 on win7
    thanks

    thanks... but it needed also needed a windows restart (dont know why) after deleting the prefs....
    now its working again
    thx
    hopefully my new imac will arrive soo...

  • Hi can anybody help please. I am having terrible problems trying to use my Nikon D7100 to tether. I have downloaded the latest Lightroom updates and also checked my firmware which is also the latest avaiable and still Lightroom wont detect my camera!

    Hi can anybody help please. I am having terrible problems trying to use my Nikon D7100 to tether. I have downloaded the latest Lightroom updates and also checked my firmware which is also the latest avaiable and still Lightroom wont detect my camera!. When I use a friends Canon camera it works every time!

    Hi Keith thanks for your reply I have Lightroom 5.7.1 64 bit and my Nikon's firmware is version 1.02

  • Why is Lightroom 6/CC catalog not registered under classes?

    The LR6 catalog file, .lrcat, no longer shows Lightroom's icon, does not appear under HK_CLASSES_ROOT in the registry, nor on the Windows file association list. Having said that, LR6/CC loads the catalog normally and can be started by double-clicking the .lrcat file. So, the question is probably purely academic as functionality does not seem to be impaired.
    (In my case, LR CC has been installed on two machines, replacing LR5.7: desktop running Win7 and laptop running Win8.1. LR6's (upgraded) .lrcat does not show as the default LR file on either machine. Lightroom 5's catalog did.)
    Mark

    So I spent all evening experimenting with different things in Lightroom to try and improve performance and found 1 solution that worked.  Although I'm not sure why.
    I understand that a design decision was made to render thumbs on the fly.  Fine.  But what I couldn't understand was why it took so incredibly long.  I mean the process was literally locking up my entire machine every time I touched the scroll bar.
    The ONLY thing I could get to clear up the problem was to select the top level folder in my catalog, and export the entire catalog as a new catalog.  For export I did NOT choose to export the image files or the previews since I only wanted to keep my database (image adjustments, keywords, etc).
    Upon opening this newly created catalog, of course everything was slow because there are no previews for anything.  Fine.  So I chose to render standard sized previews for a couple of the folders in the catalog (about 150 photos each).  And then lightroom became extremely fast for browsing and scrolling through thumbnails on those particular folders.
    What I can't undertand is why rendering standard sized previews on my old catalog (same photos, same folder) does not improve performance, yet doing it for the new catalog which should be an exact copy DOES improve performance.
    The only thing I can think of is that my original catalog must have either been corrupt or there may be some upper limit on how many previews Lightroom can handle gracefully?  Since I had standard previews for my entire catalog before.
    I'm going to try and render standard sized previews on my entire new catalog tonight and see if the performance remains snappy.  But something is definitely not right here.

  • Cant locate my hard drive...wont startup

    hello
    Ive been reading through problems where machines wont startup...only the flashing icons and clicking...still I cant find a solution...is my machine finally failing
    Ive tried inserting the installation disk and reinstalling it but the destination window is empty [i dont see my disk]...please help with a fix...
    Message was edited by: marAz14

    marAz14 wrote:
    Ive been reading through problems where machines wont startup...only the flashing icons and clicking...still I cant find a solution...is my machine finally failing ?
    A flashing disk icon means the bootloader that starts up your Mac can't find a suitable startup disk. Something happened to the internal HDD to cause this, the damage may be repairable or not.
    Ive tried inserting the installation disk and reinstalling it but the destination window is empty [i dont see my disk]...please help with a fix...
    It can't see the disk for the same reason that the bootloader couldn't. Let's try to see if it is fixable before reinstalling everything and losing all your settings. Since you already are able to start up from the Install CD/DVD, go to the Utilities menu and select *Disk Utility*. There, check and see if the HDD device appears on the left column. Under and indented you should see the volume by name.
    If the device does not appear, then it is really hosed and you will need a new one.
    If it appears, with or without the volume, it means it is damaged but may be repairable. Click on the device and do a *Repair Disk*. If it says there are errors, repeat *Repair Disk* until it comes out clean with no more errors. After that, reboot and see if the Mac will start up correctly. When it does, run Disk Utility again (it is found inside the startup volume's Utilities folder) and do a *Repair Disk Permissions*. If all is well, you'll be a happy camper and your Mac will live to see another day.
    If you can't get the *Repair Disk* procedure to come out without errors, it means that the damage is more severe and Disk Utility can't repair it. You can either get heavier duty tools, like TechTool Pro or Disk Warrior, or you can choose to format the HDD and reinstall afresh. Note that you will lose everything. If you decide to format and the formatting has errors, it also means the drive is permanently damaged and will need to be replaced.
    Let us know how it turned out and welcome to Apple Discussions.

  • I have been interested in how lightroom uses the catalog so was poking around a backup of the catalog. I found it rather concerning that although the database (catalog) is pretty well designed, there is no referential integrity defined or enforced.

    I have been interested in how lightroom uses the catalog so was poking around a backup of the catalog.  I am a database administrator and I found it rather concerning that although the database (catalog) is pretty well designed, there is no referential integrity defined or enforced. This is non-standard practice and could well be the source of corrupt catalogs I have seen many people complain about. I would strongly recommend the developers modify the catalog and adopt best practices if they want to improve the stability of Lightroom and the catalog.

    I would imagine that data integrity is not enforced for performance reasons. In a closed environment like LR where the application has complete control over the data, enforcing data integrity may not be worth the performance hit. Often what is done in an environment like this is to have data integrity on in test environments which would expose data integrity bugs but where the impact of performance is low. In "production" it is then turned off to get as much performance as possible. I would say there are many more complaints about performance than corrupt catalogs. And corrupt catalogs are more likely due to interruptions in writing to the catalog (like crashes, backups or dropbox activity while LR is running, etc). Data integrity would not help in these cases as they are outside the databases control.

  • Lightroom 5 auto import issues with nikon d90

    Hoping someone can help answer my question - I am wondering if Lightroom 5 has any issues with the auto import or tethering feature using a Nikon d90? I was using Lightroom 2 and the auto import feature has no issues with my d90. After I installed Lightroom 5 (Cloud App) and ran it for the first time, the first thing I used was the tethering feature and it worked great for 4 shots. I turned my camera off and then back on again and LR would not recognize my camera any longer for tethering. What's strange is that it will detect it for "Importing from Device" option. So, I went to plan two which was to auto import and that wasn't working at all. I am at a loss. I have a shoot coming up this weekend and need for one of these options to work. Any help is appreciated!!!

    I use a D90, but I have never tried tethered shooting with it. Other users might have some suggestions for you, but looking at the list of supported cameras for tethered shooting the D90 is not "officially" supported in Lightroom. So you're probably on your own to find solutions. I know this isn't a lot of help.

  • My Most important Lightroom CS5.5 Catalog won't open

    My Most important Lightroom CS5.5 Catalog won't open. I guess it didn't shut down properly. I called support and was not allowed to speak with technical support. I have hundreds of hours of work which are lost if I cannot open it. The error says: "Unexpected error opening catalog. The catalog could not be opened due to an unexpected error." Please help. Please.

    Hal
    I am getting the same error.
    I am new to LightRoom but already have some "important" photos edited and catalog in LR.  I do not have a catalog with a .lock extension but rather an "unexpected error" as above.  I tried your suggestion but was unable to open any of the three backup catalog files I have.  (I did rename the existing .lrcat before I copied a new lrcat file to the default directory. 
    I would appreciate any other suggestions you might have.  I can not even open LR with this error.  How do I create a new catalog?  The button "Create a New Catalog" take me to a folder but does not seem to create necessary file.

  • Disk Utility wont startup

    I'm trying to start Disk Utility (under mac os 10.4.8, intel) but it wont startup. It bounces one time in the dock and then dissapers.
    I tried a copy of an other computer, but the same problem. I Repaired Permissions in the terminal. I've reset my P ram.
    This didn't work at all. Anyone an idea?

    Wow, that's not good.
    The first four bytes of a "Universal" Mach-O loadable object and/or executable should be (in hexadecimal representation, which is what the "0x" prefix signifies):
    <pre>0xCAFEBABE</pre>
    but instead, it's saying that the first four bytes are:
    <pre>0xCC8B45D0</pre>
    In other words, the internal data of the file has been altered or is otherwise incorrect so that it's unusable.
    Before doing anything else, I would, if you haven't already done so, startup from your Install DVD/CD and use Disk Utility to make sure your disk directory checks out okay. Use the Verify/Repair Disk buttons to do this. How to repair this problem short of an Archive and Install is a bit tricky.
    What exactly did you try copying from another Mac? That could work, but you need to make sure that you only copy it from a Mac of the same architecture: Intel-Mac to an Intel-Mac and PowerPC to a PowerPC Mac. Note that the Disk Utility application itself is most likely fine, there's no need to copy that. What you want to copy is the /System/Library/PrivateFrameworks/DiskImages.framework/. Copy that "DiskImages.framework" folder from another Intel-based Mac and put it into the /System/Library/PrivateFrameworks/ folder on your (damaged) Mac. Replace the existing copy. (You'll need to click the "Authenticate" button to enter your password in order to accomplish this). Then try launching Disk Utility to see if it will launch successfully.
    Hope this helps....
    Dual 2.7GHz PowerPC G5 w/ 2.5 GB RAM; 17" MacBook Pro w/ 2 GB RAM -   Mac OS X (10.4.8)  

Maybe you are looking for

  • Invalid parameter value Error while Extending PoReqDistributionsVO

    Hi, My Requirement is to restrict user from enetring certain values in a field in iProcurement Page based on some condition. The attribute on which I have to place the validation is CodeCombinationId and the VO name is PoReqDistributionsVO. So, I ext

  • Pr to po attachments

    Hi, We are attaching documents in the PR using " Serice for objects" functionality. Can we transfer those document to PO when we create referencing this PR. Is anyone aware or used this type of funtionality. any idea on the BAPI name. Thanks Sekhar

  • Wild card search option

    Is the Wild card search option availble in flex.

  • Manually controlled slide show?

    I'm feeling like a bit of an idiot since it seems to me that I should be able to do this, and that it should be in an obvious place ... but I can't find it. I would like to set up a slide show that advances on a mouse click. I can do what I want by s

  • How to transfer iMac photos to iphone 5S, how to transfer iMac photos to iphone 5S

    New to IMac and Iphone so question is "How do I copy photos from IMac to Iphone 5S?"