Cannot access DB on Windows share after 2.5 upgrade

(8 posts)
  • malibu
    Member

    I have my database on a windows shared drive because I access it from a desktop and my laptop and I need the same sorting data.  This worked fine in ACDSee 2.0 but it does not seem to work with ACDSee 2.5.  Here is my sequence of events:

    - With ACDSee 2.0, created and used dir on shared drive just fine
    - Upgraded to ACDSee 2.5 on our desktop PC and went though restart / db conversion
    - Noticed on the desktop the DB had reverted back to the default place
    - Switched DB location to the shared drive and when starting ACDsee I now get a message 'ACDSee must close because it cannot access the database'

    So I thought.. Fine, what happened was when I upgraded it converted the local default database and not the shared one.  So I did the following:

    - Went to my laptop and did the upgrade, went through database conversion steps.
    - Switched the database location to the shared drive
    - Selected the 'database conversion' option from tools
    - Verified my shared database was in the dialog.
    - Conversion completed fine.
    - ACDSee restarted to complete the conversion and now gives message "ACDSee must close because it cannot connect to the database"

    Please fix this.  THanks.

    Posted On October 7, 2008 - 02:35 PM (1 year ago) (Permalink to this post)
  • Philip Weir
    Member

    The following may help.

    Delete the "Default" (....catalogs/25Pro/Default...) folder so that ACDSee can rebuild it on startup. Start ACDSee then go to Tools>Options>Database> Database location and set your shared drive as the location.

    Philip

    Posted On October 7, 2008 - 06:20 PM (1 year ago) (Permalink to this post)
  • malibu
    Member

    No this does not help.  ACDSee continues to attempt to access the database from the shared drive.  I know it's trying to access from the correct path because it is in the error message.

    Does ACDsee staff not read this forum??

    Posted On October 14, 2008 - 03:57 AM (1 year ago) (Permalink to this post)
  • Marc Sabatella
    Moderator

    malibu said:

    Does ACDsee staff not read this forum??

    They do at times, but the main purpose of this forum is to provide a place for users to help each other.  If you want to get ACD staff involved, you need to submit a support ticket.

     

     

    Posted On October 15, 2008 - 03:39 PM (1 year ago) (Permalink to this post)
  • newname
    Member

    malibu said:

     This worked fine in ACDSee 2.0 but it does not seem to work with ACDSee 2.5.  

     Imho this isn't a bug, it's a new feature.  v2.5 (335) doesn't accept UNC path (eg. \\server\resource) for DBPATH.

    As workaround you could map the resource to a new drive letter. v2.5 (335) does accept this.

    Posted On October 16, 2008 - 08:50 AM (1 year ago) (Permalink to this post)
  • mindleftnumb
    Member

    Do any of the new builds of ACDSee "accept UNC path for DBPATH"?

    I'd imagine many people use several computers at home to access the same photos and would like to share a database across those computers.

    I did find the following thread (http://community.acdsee.com/forums/topic/acd-pro-shared-on-network?replies=3#post-32533 ) but this is quite a cumbersome process to go through each and every time you do some photo management.

    Posted On January 16, 2009 - 08:59 PM (10 months ago) (Permalink to this post)
  • johndoe
    Member

    mindleftnumb said:

    Do any of the new builds of ACDSee "accept UNC path for DBPATH"?

    Works pretty well here. But it's anoying to ensure that the DB is not used by more than one user at any time!

     

    Posted On January 16, 2009 - 10:49 PM (10 months ago) (Permalink to this post)
  • mindleftnumb
    Member

    johndoe said:

    mindleftnumb said:

    Do any of the new builds of ACDSee "accept UNC path for DBPATH"?

    Works pretty well here. But it's anoying to ensure that the DB is not used by more than one user at any time!

     

    I bet. Unfortunately for me I have the same problem as the original poster. " ACDSee restarted to complete the conversion and now gives message "ACDSee must close because it cannot connect to the database" " . This always eventually happens on one of my machines and ACDSee must be reinstalled to resolve it.

    Posted On January 16, 2009 - 11:03 PM (10 months ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.