LR must quit because Catalogue named lighroom Catalogue .lrcat is not writable and cnnot be opened.

Etc. Holding down the ctrl key etc. does not help. I recently lost most of my computer software, etc. - a disaster that I finally had to have a professional sort out (it included a disc failure and so on). I have reloaded everything, including my Photoshop CS3 and every thing works! So I thought I should reload the Photoshop Lightroom too. I did so but NO Joy. When I want to open it I get the message as mentioned under subject! There was not a lot of photos in the previous version before the computer failure, and most of the photos were backed up in the PS.CS3.How do I get the proper Catalogue opening? Would just reloading the entire LR again work. Or do I need to delete the LR software and then start over. Of course I would prefer to just make the version that I have now work! I use Win XP Pro, 2 G of ram, etc. Thank you for any suggestions or help. Roy.

If you have Catalog backups you can open your last back up: File > Open Catalog. If not, it sounds like you lost your Catalog.
If you still have your photos and you wrote the xmp data to them when you worked on them in LR, you can import them into LR and your adjustments, keywords, etc. will be written into the new catalog.
If you do not want to automatically write the xmp data to your files due to performance issues, be sure to do it manually so that xmp data is stored with your files.
It is critical to back up your photos and Catalog (at least 4 catalog backups--I have had 2 backups fail, but the 3rd one saved me) on separate disks, and have an off-site backup as well. I also suggest another backup on DVDs. Without backups you should plan on losing everything on your computer every so often. My last disk failure was so complete that data could not be recovered at all--no problem I had my backups.

Similar Messages

Why do i get the following message when i attempt to open my backup file for lightroom cc? "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened". This message just started coming up after downloadi

why do i get the following message when i attempt to open my backup file for lightroom cc? "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened". This message just started coming up after downloading lightroom cc (previously using lightroom 5)...am i backing up properly or not???

Open Pictures folder and move the files named lrcat-journal and lrcat.lock to Desktop.
Make sure that , they are not inside Pictures folder any more and try to open backup from Lighrtroom and check..
Any LRcat file with .lock extension , move it to Desktop.

Photos must quit because the photo library has become unavailable or its data is corrupt

Hello,
As many of you, I've installed photos. This is my problem: I am an enthusiastic photographer that keeps around 10K photos per year (approx. 60GB), and while I have several years of pictures, I've just get the last 5 years. To be honest, I never liked iphoto to organize my pictures, I rather use Picasa. The way how pictures get organized, the poor effects tweaks to photos, the lack of freedom to keep an online folder...etc.
But with this new Photos, well, what the heck let's give it a chance.
It seemed cool, all my devices connected, iCloud (very limited storage though), new nice quick effects... the organization of pictures also seemed improved. the UI as usual with apple apps, pretty neat and clean.
Did I mentioned that I have several hundreds of GB of pictures? Well, a detail, I keep it in my time capsule to have them handy when I need it. With picasa, I just need to ensure that time capsule is waked, and pictures get recognized at once.
With photos, I've tried with 1 year, 10,000 pictures and.... very disappointed, it shutdown every 1 minute saying "Photos must quit because the photo library has become unavailable or its data is corrupt"...
Do I missing something here? is this supposed to be better than iPhoto? Time Capsule is not able to send steady signal to get my library online?

Not sure exactly whats going on with that given how new Photos is. But, Picasa works because differently than Photos because it doesn't use a centralized library. Picasa will just scan the entire computer and reference it in that location. Photos libraries, while sometimes problematic, are superior because as you've experience moving all the content is as simply as moving a single file.
Suggestions I would try:
Make sure Photos is quit. Hold down Command + Option on keyboard and click Photos icon to launch. Keep holding until you get a dialog box about repairing the library. Proceed with repair.
Move the library, if size permits, to your local HD on the computer and attempt to open and use.
Create a new library by holding Option on keyboard and launching Photos. Choose to create a new library and make sure it's placed in your ~/Pictures folder. If that works you know its library specific.
Right click on the external drive (also accomplished by holding Control when click), choose get info on the drive. Bottom of new window expand (if not already) the sharing and permissions section. Click lock icon and provide administrator password. If available, which it should be if using same drive for a Time Machine backup, check box to ignore permissions.

Error message: Photos must quit because the photo library has become unavailable or its data is corrupt.

I suddenly get this error message when trying to open and use Photos. "Photos must quit because the photo library has become unavailable or its data is corrupt."
I can't find a solution to fix the problem.

The only version of iPhoto that works with 10.10.3 is iPhoto 9.6.1 which must be downloaded from the App Store. What version of iPhoto do you have installed?

What to do when photos tells me it must quit because of corrupted files

clicked on photos and it opened to tell me it must quit due to corrupted data, what can I do to get to me photos?

You need to update your profile - you state thee that you have OS X 10.8.1
Try backing up your Photo library an launching Photos while holding down the option and command keys and repairing the Photos library
LN

Unexpected performance of Firefox in Windows 7, namely minimize/maximize/close buttons not working and unable to move/resize window.

I have been using FF for a while now. My main computer was WinXP-32, though I recently bought a new laptop with Win7-64 installed. This problem was never experienced on my WinXP machine.
Brief description of problem:
After a time of having FF up and running, the minimize/maximize/restore/close buttons in the top-right no longer work as expected and, if not maximised, I cannot move the window around my desktop nor resize the browser window. When clicked, the buttons will
rapidly flash on and off continuously without appearing to perform any noticeable function other than temporarily hogging CPU cycles. I've found that clicking (sometimes double clicking) in the main browser window then mousing over the buttons again seems
to stop them flashing, though does nothing else.
To minimize/maximize/restore/move/close the window(s), I have to right-click on the relevant tab in my taskbar and pick the desired option. Occasionally, however, even this doesn't work and the right-click menu will disappear as soon as I move the mouse
over it after right-clicking. 'Show desktop' is a temporary fix for minimising windows and 'ALT + F4' or 'CTRL + W' for closing windows or tabs. This isn't satisfactory and to move or resize a window, I have to close the window in question (sometimes all other
windows too), reopen it and do what I need to do, though sometimes even this is only a very short fix. If I have to close all the windows, FF will sometimes keep running for a while afterwards, even though no windows are actually open - simply ending the process
via the windows task manager will fix this though is only a work-around, not a fix.
One thing I have noticed is that if I manage to move the browser window (when not maximised), for a short period afterwards I can often resize the window successfully. This is more likely to occur if the browser window is not flush with the edge of my screen
once moved.
I've tried to include as much information as I can - most of which was determined after several minutes/hours of playing around with different scenarios, trying to manually reproduce particular problems or simply through sheer luck of happening to click
in the right place at the right time! I hope there is a reasonably fix for this at some point in the not-too-distant future.
I noticed in some of the threads at another site where people have voiced problems similar to mine, that a link to 'ObjectDock' was discovered in some cases. I do have 'ObjectDock 1.90 Plus' installed on my machine and use it in many ways and so decided
to see if I could find a connection between the two. I have uninstalled, tested, and reinstalled both programs in a multitude of ways, though could find no conclusive correlation between having both bits of software running or installed at the same time and
the problems I am experiencing. In my case, at least, this does not appear to be an answer.
Also, in another thread on this site, someone suggested there might be a link with AVG Anti-Virus Free (I have version 9.0.819) though I've tried uninstalling it and its various add-ons in several different combinations, with no noticeable improvement.
Sorry for such a long question... If you need to know anything more, just let me know!
- James
System Information:
Operating System: Windows 7 (64 bit)
Firefox Version: 3.6.3
Application Basics
Name
Firefox
Version
3.6.3
Profile Directory
<button onclick="openProfileDirectory()"> Open Containing Folder </button>
Installed Plugins
about:plugins
Build Configuration
about:buildconfig
Extensions
Name
Version
Enabled
ID
Update Service
1.2
true
[email protected]
Java Console
6.0.17
true
{CAFEEFAC-0016-0000-0017-ABCDEFFEDCBA}
Adblock Plus
1.2
true
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Download Statusbar
0.9.6.8
true
{D4DD63FA-01E4-46a7-B6B1-EDAB7D6AD389}
Cooliris
1.11.6
true
[email protected]
FoxTab
1.3
true
{ef4e370e-d9f0-4e00-b93e-a4f274cfdd5a}
Save File to
2.0.1
true
[email protected]
1-Click YouTube Video Downloader
1.4
true
[email protected]
British English Dictionary
1.19
true
[email protected]
Tab History
1.0.7
true
{84417002-6445-49b4-9fd7-1ef48240fa41}
Universal Print
0.4.23
true
{BE2100B3-1D80-48eb-ACCF-D26750644378}
Active Stop Button
1.3.0
true
{9e96e0c4-9bde-49b7-989f-a4ca4bdc90bb}
Fission
1.0.9
true
{1280606b-2510-4fe0-97ef-9b5a22eafe41}
Smart Bookmarks Bar
1.4.3
true
[email protected]
Compact Menu 2
3.1.1
true
{57068FBE-1506-42ee-AB02-BD183E7999E4}
Menu Editor
1.2.6
true
{EDA7B1D7-F793-4e03-B074-E6F303317FB0}
Locationbar²
1.0.5
true
[email protected]
RealPlayer Browser Record Plugin
1.0
true
{ABDE892B-13A8-4d1b-88E6-365A6E755758}
AVG Safe Search
9.0.0.812
true
{3f963a5b-e555-4543-90e2-c3908898db71}
Searchbar Autosizer
1.4.5
true
{655397ca-4766-496b-b7a8-3a5b176ee4c2}
Open Bookmarks in New Tab
0.1.2010043001
true
[email protected]
Remove New Tab Button
1.0
true
[email protected]
New Tab Homepage
0.4.2
true
{66E978CD-981F-47DF-AC42-E3CF417C1467}
SwiftTabs
0.3.6.8
true
{5F4EC95A-FFA8-11DE-898C-667D55D89593}
Tab Kit
0.5.8
true
[email protected]
Hide Find Bar
1.3.1
true
[email protected]
Toolbar Buttons
0.6.0.8
true
{03B08592-E5B4-45ff-A0BE-C1D975458688}
Java Console
6.0.19
true
{CAFEEFAC-0016-0000-0019-ABCDEFFEDCBA}
View Cookies
1.10.1
true
{8F6A6FD9-0619-459f-B9D0-81DE065D4E21}
Adobe DLM (powered by getPlus(R))
1.6.2.63
true
{E2883E8F-472F-4fb0-9522-AC9BF37916A7}
Modified Preferences
Name
Value
accessibility.typeaheadfind.flashBar
0
browser.history_expire_days.mirror
180
browser.places.importBookmarksHTML
false
browser.places.smartBookmarksVersion
2
browser.startup.homepage
http://www.bath.ac.uk/
browser.startup.homepage_override.mstone
rv:1.9.2.3
browser.tabs.closeButtons
0
browser.tabs.tabMinWidth
77
browser.tabs.warnOnClose
false
extensions.lastAppVersion
3.6.3
network.cookie.prefsMigrated
true
network.http.pipelining
true
network.http.pipelining.maxrequests
50
network.http.proxy.pipelining
true
places.last_vacuum
1271706454
privacy.sanitize.migrateFx3Prefs
true
privacy.sanitize.timeSpan
0
security.warn_viewing_mixed
false
security.warn_viewing_mixed.show_once
false

Hi Kossa,
You can also check if the issue occurs in
Clean Boot. If the issue disappears in the Clean Boot environment, you can continue to narrow down which entry is causing the issue.
Besides, uninstall it and re-download
a fresh copy of FireFox to check the result. If the issue still exists, create a new user account to see if it occurs.
If the issue persists, you can contact Mozilla Support directly and use Internet Explorer (IE) during the time.
J
Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise,
regarding this product's performance or reliability.
Regards,
Linda

How do I open an " not writable" catalogue?

I just upgraded my processor and OS to Windows 7. I reinstalled Lightroom 3. When I try to open a catalogue, I get an error message that it cannot be opened because it is not writable. Any suggestions?

There are at least three reasons for that:
a) You don't have write permission for the drive the catalog sits on. This is a feature in Win 7: for each drive you have to give yourself full permission. Right-click the drive in question, go >Properties >Security tab and highlight your log-on name. You should have check marks for "Full Control", "Modify", and "Write".
If you don't, click on <Edit>, make sure that you name is highlighted and check the boxes "Full Control", etc.
BTW you also have to do this for the drive your photos are on, i.e. for every drive that Lr uses (also think Lr cache).
b) Lr requires enough free space on the hard drive where the catalog sits in order to be able to write to it. If there isn't enough free space left, you ge the message that the catalog is not writeable.
c) Lock-file: When Lr is open there is a lrcat.lock file that sits right besides your catalog. It prevents that Lr is opened in two instances because that would create problems with the catalog. The lock file should NOT be present when Lr is closed, but sometimes it doesn't disappear for reasons unknown to me. With Lr closed check if you see a lock file (same name as your catalog but with ending "lrcat.lock"). If you do, send it to the Recycle Bin / Trash Can. Don't delete your catalog, the .lrcat file!

I open Imovie that i bought on the app store but it isnt being responsive an di have to force quit because it wont open

I open Imovie that i bought on the app store but it isnt being responsive an di have to force quit because it wont open

If you got disks with your system then you use software update to update. If you purchased the software from to app store or it came pre installed with no disks the you get updates via the app store under purchased software.
Upgrades must always be purchased
LN

I have the latest downloadable version of LR5. It crashed while it was createing 1:1 previews during an import. After a Win7(64) restart, it shows a message that LR needs to quit because it can't read the preview files and it will try to fix it the next

I have the latest downloadable version of LR5. It crashed while it was createing 1:1 previews during an import. After a Win7(64) restart, it shows a message that LR needs to quit because it can't read the preview files and it will try to fix it the next time is launches. I get the same message the next and every subsequent time it launches so I can't launch LR at all now.
I get that the preview file got corrupted somehow. Is there some way to fix this problem without building a new catalog?

Use Windows Explorer to open the folder containing your catalog. You will see a folder with the extension .lrdata. You need to delete that folder and then start Lightroom again. Lightroom will generate a new previews folder.

Premiere Elements 9 must quit due to atioglxx.dll

Hello forum,
Two years ago I bought a new PC consisting of:
System: Motherboard ASUS P5Q3
Intel[R] Core[TM2]Duo CPU
        E8500 @ 3.16 GHz
        Clockspeed 3.17 GHz
        RAM 3.3 Gb (4 Gb installed)
Windows XP 32 Home Edition Version 2002 SP3
Graphics card (see text):
        Gigabyte GV-RV577SL-1GD
        ATI Radeon HD5770/PCI-E.2.1
        1 Gb GDDR5/128bit
        (review at http://www.tweaktown.com/reviews/3506/gigabyte_radeon_hd_5770_silent_cell_1gb_video_card/i ndex.html)
Problem:
        After I have specified a projectname after having selected New Project during the startup of Premiere Elements 9 (PRE9)
        a Windows message is popping up after about 10 seconds saying that within PRE9 there is a failure and PRE9 must quit.
        It showed the following signature of failure:
Appname: Adobe premiere elements.exe App.ver: 9.0.0.0
ModName: atioglxx.dll
ModVer: 6.14.10.9901
Offset: 00088e2e
And a failure report is generated with the choice to send it to Microsoft or not.
When I repeat the above mentioned procedure then I see every time the same Windows message within a second.
About one startup out of five to ten PRE9 startups is going wrong in this way. Seems a bit random to me.
If I rename atioglxx.dll into e.g. a_atioglxx.dll then no failure is generated!
It seems if PRE9 does not need this OPEN_GL file or it no longer recognize it as an OpenGL or it simply ignores it.
(atioglxx.dll is described in http://dll.paretologic.com/detail.php/atioglxx)
In the original configuration the PC was equipped with the graphic card ASUS EAH3650 PCI-E 2.0 with the Radeon HD3600 serie.
With this card, PRE9 reacted exactly the same way as described above.
That was the inducement to look for another graphic card.
After an advice (newer chipset, newer/other drivers) of a computercompany I have purchased this Gigabyte GV-RV577SL-1GD a two days ago.
This card needs a external supplyconnection (6-pin plug). The power supply is provided with such a cable and is connected to the card.
But it has not helped to avoid the crash of PRE9.
So it seems to be not the graphics card.
If I look on the AMD support site for the newest driver version for both cards,
Radeon HD3000 serie and the Radeon HD5000 serie, then I see that
the newest driver version is exactly the same for both cards.
I have installed this new version (Catalyst 11.3). It did not fix the issue.
The MoBo has also the newest driver.
I have done a try with a very small NVIDIA card. With this card there were no PRE9 crashes.
But a NVIDIA driver for this card has also not a atioglxx.dll from ATI.
I still prefer also for another reason to choose for this Gigabyte card. And I suppose that a AMD Radeon HDxxxx card also should work.
I am not involved in how a dll file is interacting with a graphic card or application.
So I can not say which component is causing the crash. Is it PRE9, is it the card, the driver
or a perhaps a timing problem anywhere?
The Adobe helpdesk was involved and has analysed e.g. the Windows DXDIAG and MSinfo32 but could not help me further.
Thank you in advance for your suggestions.

Thank you Bill and Nealeh,
Thank you for your help so far.
Meanwhile I have again installed Windows XP+updates+newest hardware drivers etc.
I also installed the update for Premiere Elements 9 to 9.01
I found also a newer driver for the video card and installed it (AMD version 11.4)
All these actions did not lead to the solution to avoid that Premiere Elements 9 (PRE9) crashes randomly.
With the Trial version of PRE9 the same result
By the way to quit PRE9 I used Alt+F4.
But accidentally I pressed Windows(Start)+F4.
This action causes that the Project Name menu pops up (not mentioned in the Help File of PRE9). In fact PRE9 returns one step back.
And that is more convenient than to start every time the program by clicking on the PRE9 icon for investigating this issue.
So I could immediately answer this "New Project" window by clicking on the OK button.
I do not give it an other name so I answer YES on the "Overwrite"question and PRE9 finalises the starting up procedure.
When PRE9 does not crash I use Alt+F4 to quit the program.
Then to try I used only F4 and I saw that it creates the same effect as Windows(Start)+F4.
So I could rapidly repeat between the "New Project" window and the moment that PRE9 has finished
the starting up procedure by only using F4 on the keyboard.
And it is still the case that when PRE9 is crashing for the first time after having switched on or rebooted the computer , then PRE9 freezes for about 7 ...10 seconds before it crashes. But eventually next crashes happen immediately.
Besides from my experiences somebody else for me have tested this issue on a HPMEDIACENTERPC with Windows XP SP3 etc. and with a video card with the Radeon HD 3600.
And he experienced exactly the same crash with PRE9. Also a conflict with atioglxx.dll.
But he scored a succes by deleting all ATI files, but only installing the displaydriver and not the Catalyst.
So if that helps is it worth to put this issue to AMD for further investigation?
And is it known to you that F4 is causing to open the "Project"window in PRE9?
Thanks a lot for your reaction.
Kees

HT201210 (The iPhone "Named" cannot be restored at this time because the iPhone software update server could not be contacted or is temporarily unavailable.) can anyone help me with this issue, every time i try to restore it will come up like this error m

(The iPhone "Named" cannot be restored at this time because the iPhone software update server could not be contacted or is temporarily unavailable.)
can anyone help me with this issue, every time i try to restore it will come up like this error message.

Restore the iPhone when connected to iTunes by cable.
Still the same TS1275?
Is your iPhone jailbroken?
Or
Has your computer ever been used to jailbrake or downgrade (Tinyumbrella) any iPhone?

Acrobat 8.1 dont opend and work in the new Win 8.1? What I can do? Dont want buy the new version. Programm must worked because it buyed 2008. E-mail: erhuovi@metasport.fi

Acrobat 8.1 dont opend and work in the new Win 8.1? What I can do? Dont want buy the new version. Programm must worked because it buyed 2008. E-mail: [email protected]

Hi jyvaskyla.fi,
You are posting on acrobat.com online service forums.
Kindly post this query in Acrobat forums:Acrobat
Regards,
Florence

I can't shut down my MacBook Pro. I'm getting the following message: "The Finder can't quit because some operations are still in progress." How can I determine what is running?

I can't shut down my MacBook Pro. Each time I try, I get the following message: "The Finder can't quit because some operations are still in progress." How can I determine what is running?

Yea,
I bought an original CRT iMac two day's before they were launched, which got the reseller into trouble, and had it replaced by APPLE.
This was a great learning process for me dealing with the glitches. :-)
I LOVE MAC. Now own 4 and on my 10th. in 15 years + 7 bought for family.
Cheers,
Tom

System Preferences "Must Quit and Reopen" No "Open in 32-bit" Option to Uncheck

Everything worked fine when I had 10.7. But I still updated to 10.8 when it came out. I spent quite a while trying to figure out why I couldn't use many of the preferences in the system preferences. I kept getting the message: "To use the ____ preferences pane, System Preferences must quit and reopen." Quitting and reopenning sends me on an infinite loop.
I've scowered the support communities and found no help. The communities kept saying I should go to the System Preferences file in Applications, go to Get Info, and uncheck a box that says "Open in 32-bit Mode." Unfortunately, I have never had that box. Today I updated to 10.8.4, hoping that this would finally get fixed. It was not.
Is there any solution I'm missing?

Just got same problem.
#1. There is no Box, under Label or anywher to uncheck or check.
#2. The device I want to use does not have an update driver. What I really need if for the Box to check or uncheck which should be there according to Apple Help.
#3. I tried this, resetting the whole computer's kernal extension by using a Terminal command (although I don't like doing that). It didn't work. sudo systemsetup -setkernelbootarchitecture i386
So I reset it to: sudo systemsetup -setkernelbootarchitecture x86_64
But emphasize, again, I don't like doing SUDO commands in Terminal.
So...Anything else to try?
Thanks for any info that might help.

To use the "Users & Groups" preferences pane, System Preferences must quit and reopen.

When I try to access some of the system preferences in Mavericks I get an error pane that states "To use the “Users & Groups” preferences pane, System Preferences must quit and reopen."
Has anybody had this problem and if so what is the fix?

Usually happens if you opened one that was 32-bit. Then, you need to revert back to 64-bit.

LR must quit because Catalogue named lighroom Catalogue .lrcat is not writable and cnnot be opened.

Similar Messages

Maybe you are looking for