Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Trouble with Multiple Users on one Catalogue

Comments

16 comments

  • Paul Steunebrink
    You might run a later version of CO than your partner. Even different versions of CO8 can cause this. Note that CO 8.2, released today, again updates the database. This means that if you would use 8.2, your partner also must use 8.2.
    0
  • Ade Hodgetts
    Thanks for the quick response.

    We are on the same Mac Pro as different users, so I would have thought the Version would have been the same? 😕

    Im downloading 8.2 at the moment to see if that helps sort the problem.

    Many Thanks

    Ade
    0
  • Paul Steunebrink
    If CO 8.2 does give the same problem, you perhaps like to share with how you share the catalog between 2 users on 1 system.
    0
  • Ade Hodgetts
    Paul, thanks for the reply

    I have just updated to 8.2 and still cannot load my catalogue as the 2nd user.

    I have placed the catalogue file in various locations.....

    my pictures with sharing on all catalogue folders - didn't work

    in the public folder of my user with full sharing - still no joy

    currently its on my media drive (internal 3tb drive on a cMP) and still getting "The catalog couldn't be opened due to a locking conflict. Please check permissions on the catalog folder."

    Both Capture Ones are updated to 8.2.

    Any ideas?
    0
  • Christian Gruner
    [quote="LongSticks" wrote:
    Paul, thanks for the reply

    I have just updated to 8.2 and still cannot load my catalogue as the 2nd user.

    I have placed the catalogue file in various locations.....

    my pictures with sharing on all catalogue folders - didn't work

    in the public folder of my user with full sharing - still no joy

    currently its on my media drive (internal 3tb drive on a cMP) and still getting "The catalog couldn't be opened due to a locking conflict. Please check permissions on the catalog folder."

    Both Capture Ones are updated to 8.2.

    Any ideas?


    Open the Catalog package with Finder, then delete the write lock file. You can now open the catalog. This usually happens whenever CO was not properly shut down, as it didn't get the chance to remove the file before shutdown.
    0
  • Ade Hodgetts
    Thanks Christian

    There is no write lock file inside the catalogue. So still have the same issue.

    Just as a thought, should the catalogue be in the Shared Folder outside of the user set up.....

    OSX>Users>Shared>Capture One

    Regards

    Ade
    0
  • Paul Steunebrink
    This sounds more like a permissions conflict. Please be aware, that when the catalog is placed on a folder by User A, and accessed and opened by User B, the catalog file/folder still is only fully read/writeable by User A only (very simplistic explanation). The user's Public folder is very restricted for other users, so that won't help either. Of course you can change the permissions from Finder, Get Info dialog. That is one option.

    Another option
    What you could try from CO8's point, is enable the 'Make new files writable by everyone' setting in Preferences > Images.
    0
  • Ade Hodgetts
    Paul

    I have had the writable new files checked in preferences from day one.

    The catalogue and all internal elements are read and write sharable with the 2nd user as well.

    Any thoughts on putting the catalogue at root level - OSX>Users>Shared>Capture One?

    Last thought - 2nd user only has standard user privileges - is this an issue?

    Thanks again for you help.
    0
  • Paul Steunebrink
    Forgot to mention this is my previous post. When User A copies a file/folder to the Shared folder, the copy inherits the permissions of User A, effectively restricting full access by User B. That is theory.

    When I do classroom trainings on Capture One, I prepare the training from my regular user account, say A, but give the training using a separate user account, say B. Just before the training I copy any catalog and presentation from A to B through the Shared folder you mentioned. However, as user B, I copy them again from the Shared folder to the home folders of that user B for permission issues.
    0
  • Ade Hodgetts
    Using the method you described, does that make the catalogue writable to both users on there log in from that point forward?
    0
  • Paul Steunebrink
    No, it is to show that I did (and do) take precautions to prevent permission issues.

    What version of OS X do you use and where are the images of your catalog are stored (assuming you have referenced images).
    0
  • Ade Hodgetts
    Paul

    Sorry in the middle of a very busy period with work.

    Yes the images are referenced. They are held in a 3tb internal drive on a new to me MacPro 5,1. The drive is a media drive only (Music, Films, Photos etc), OS X is on a separate internal SSD.

    Have tried placing the catalogue in the OS X level shared folder and allowing permissions for the 2 users and still no joy for the 2nd user!

    Very frustrating as an ex Aperture user. Never had this problem.

    Thanks again for trying to help me.
    0
  • sizzlingbadger
    The "Catalog" is an OS X package. I'm pretty sure that if you change the permissions on the package they don't get changed recursively within the package. This may be the issue your having.

    Make a new folder and put the Catalog in that folder. Select the folder and hit Command + I, go to the permissions panel for the folder and set permissions as required. Then click on the "gears" action button at the bottom of the "get info" popup and select "apply to enclosed items". This will change permissions recursively on everything in that folder.

    You can them move the catalog back out of the folder if you want.
    0
  • Ade Hodgetts
    Thanks Sizzling, will give that a go when I get 5 mins and report back.
    0
  • Ade Hodgetts
    [quote="sizzlingbadger" wrote:
    The "Catalog" is an OS X package. I'm pretty sure that if you change the permissions on the package they don't get changed recursively within the package. This may be the issue your having.

    Make a new folder and put the Catalog in that folder. Select the folder and hit Command + I, go to the permissions panel for the folder and set permissions as required. Then click on the "gears" action button at the bottom of the "get info" popup and select "apply to enclosed items". This will change permissions recursively on everything in that folder.

    You can them move the catalog back out of the folder if you want.


    Had an early start this morning and thought I'd try your fix whilst having a quick coffee!

    Even though its 5am - huge 😄 as it worked just as you said. Thanks very much for the tip, Badger.

    A good start to a Monday Morning
    0
  • sizzlingbadger
    Glad it helped, I wasn't 100% sure it was the issue but it just popped into my head when I was reading your post.
    0

Post is closed for comments.