Help with C1 Pro 7.1 Crash on Startup
While debugging a C1 Pro 7.1 problem with Technical Support, they advised me to do a clean uninstall of C1, which I did. I reinstalled and everything went as planned.
But when I launch C1 now, I get an error that says:
Catalog folder "/Users/Bob/Pictures/Capture One Catalog.cocatalog" is not writable. Please choose another catalog folder.
When I click OK, C1 crashes.
Has anyone else seen or solved this problem? I have a ticket in with Technical Support now, but its the weekend.
Mac OS X 10.8.2
Mac Pro
But when I launch C1 now, I get an error that says:
Catalog folder "/Users/Bob/Pictures/Capture One Catalog.cocatalog" is not writable. Please choose another catalog folder.
When I click OK, C1 crashes.
Has anyone else seen or solved this problem? I have a ticket in with Technical Support now, but its the weekend.
Mac OS X 10.8.2
Mac Pro
0
-
Bob,
The first step I recommend is to run "Repair Permissions" via disk utility multiple times (until you come back with no reported results) and then reboot. If this is something you haven't done regularly, I would also suggest making it a monthly habit.- Close all open/running applications.
- Open Disk Utility from the Finder (Applications -> Utilities -> Disk Utility)
- Select the partition where your OS is installed (probably "Macintosh HDD")
- Press the "Repair Disk Permissions" button.
- Rinse & repeat until you have zero (or as close to zero reported incidents as possible after multiple tries)
- Reboot
- Check back with C1 and let us know how it goes.
Good luck!0 -
Yep, I did all that. No help, it's still crashing no matter how I launch it. I've launched it holding down option, launching it by itself, drug the catalog file onto its icon - none of that helps.
I also checked permissions specifically on the folders involved and I have read/write/execute permission all down the chain.
Still stuck.0 -
Bob,
A look from another angle.
Open the catalog file (right-click > Show Package Contents). Locate the 'writelock' file. Remove it. Close the Finder (this is optional) and start CO7 again.0 -
[quote="Paul_Steunebrink" wrote:
Open the catalog file (right-click > Show Package Contents). Locate the 'writelock' file. Remove it. Close the Finder (this is optional) and start CO7 again.
That's a good idea! I should have thought of that.
But rooting around inside the catalog package with Path Finder, I don't see a writelock file, even a hidden file. ☹️0 -
Can you create a new catalog in your Pictures folder? If that works, you can create one and move the contents of the ill-fated catalog folder to the new one. 0 -
[quote="Paul_Steunebrink" wrote:
Can you create a new catalog in your Pictures folder? If that works, you can create one and move the contents of the ill-fated catalog folder to the new one.
No. I can't get C1 to launch at all.0 -
Can you start CO 7 with the Option/Alt key pressed, so that it will open the Recent dialog? 0 -
[quote="Paul_Steunebrink" wrote:
Can you start CO 7 with the Option/Alt key pressed, so that it will open the Recent dialog?
No, I tried that, too. I does the same thing. Says I can't access the catalog, doesn't let me pick or create another, and crashes when I click OK.0 -
You could move the catalog to another location and try to start with Option key. If it still crashes, I would remove the preferences (again) and install CO7 again. 0 -
[quote="Paul_Steunebrink" wrote:
You could move the catalog to another location and try to start with Option key. If it still crashes, I would remove the preferences (again) and install CO7 again.
Did all that, too.
I'll run through it again, to be sure.0 -
Dang!
Moved the catalog file, deleted the two preference files, deleted C1 and then reinstalled C1. Started C1 with option down (I have a Mac) and it did the same thing. It wants that catalog and it can't write to it. When I click OK, it crashes.
Frustrating.
Somewhere, somehow, C1 "remembers" that darn catalog and won't let go. Is there somewhere else to look?0 -
Have you let CO7 create a new Capture One Catalog? It will create one when you delete the previous one and start without preferences.
Also, you could start with a session and create new catalogs from there.0 -
[quote="Paul_Steunebrink" wrote:
Have you let CO7 create a new Capture One Catalog? It will create one when you delete the previous one and start without preferences.
Also, you could start with a session and create new catalogs from there.
C1 will not let me create a new catalog. And it will not create one itself. As soon as I OK the error dialog, it crashes. Even after deleting the preferences.0 -
I'm sorry to hear that you're still experiencing issues with this.
I'd try one more thing, which is admittedly a long shot - clear the batch queue.
To clear the batch queue, you need to locate directory and just empty it. The directory is located at/Users/[Username]/Library/Application Support/CaptureOne/Batch Queue 5.1/
Like I said - it's a bit of a long shot, but if Capture One previously crashed while you were processing out files, and now won't load, then jobs jammed up in the batch queue could be the culprit.
If that doesn't do the trick then the next best step (if you haven't already done so) is going to be creating a support case directly with PhaseOne. No worries though - these guys are good at what they do, and generally respond within a couple of hours.
They are almost certainly going to ask for a copy of the catalog file, as well as your system log files.
You can find the log files here:/Users/[Username]/Library/Logs
You may not have all of these, send along anything that looks relevant and the PhaseOne crew will be able to help out.- CaptureOneCC.log
- CaptureOneIC.log
- CaptureOneICP.log
- com.phaseone.captureone.log
- com.phaseonecaptureone7.log
Good luck & let us know how it goes!0 -
I had no batch files.
So I've opened case ID: 121314
Thanks for the help!0 -
You could try with another user account on your system (preferably create a new one). Log in and see what happens. This is to rule out any issues in your user profile. 0 -
[quote="Paul_Steunebrink" wrote:
You could try with another user account on your system (preferably create a new one). Log in and see what happens. This is to rule out any issues in your user profile.
OK, a little progress, I suppose. I logged in as my Test user and CO7 didn't complain about the catalog and let me open it. But then I get the dialog to set to try the demo. I'm a registered CO4 user, and CO7 knows that and says I have to quit and relaunch CO7. I've seen this before and it used to be fine. Now, when I select Try and click OK to relaunch, CO7 quits. When I restart it, it asked for the same relaunch, and that's what happens now on every launch under the Test account. It's stuck in that loop.
Back in my regular account, CO7 still doesn't like the catalog and crashes on OK, just like before.
Stumped.0
Post is closed for comments.
Comments
17 comments