Session cannot be imported

lewisl

• February 08, 2016 03:42

I have a session that created with C1 9.0.3 that cannot be imported by C1 9.0.3.

I have no idea why. The session will open. All of its images are present with their adjustments, metadata, etc. Nothing wrong with it that appears when using it in C1.

Close the session.

Open a catalog. The session cannot be imported.

Create a new catalog. The session cannot be imported.

There is no message or warning of any kind. Choose File/Import Session. Navigate to the session and in the file import dialog box choose the <name>.cosessiondb file. The import button becomes active. Click. The processing circle flashes for less than a second.

Nothing happens. Nothing has been imported.

I can't figure it out. I have closed and reopened C1. Next I will try restarting the computer.

I am trying to decide whether I can trust C1. It has good capabilities but many corner cases and lots of fragility. This is just the latest.

0

• 

  lewisl

  • February 08, 2016 03:56

  Well, my work around was to add the folders to the library folders and then sync them--showing the import dialog to make sure include adjustments was checked.
  
  C1 seems very fragile because of years of adding features and increasing complexity without cleaning up the product's concepts.
  
  It's clear that the underlying plumbing mostly works but with 3-4 ways of doing file handling there seem to be ways that are blocked with no clear indication why.
  
  This is the first time a session would not import and if I am to trust sessions I'd still like to understand why it wouldn't import. Happy to provide any and all details that can help diagnose.
  
  Thanks.

  0
• 

  SFA

  • February 08, 2016 04:02

  Two thoughts.
  
  Firstly I wonder if maybe there is a lock file somewhere or a rogue process that is leading the importer to think that there is something happening that does not allow it to start.
  
  Have you tried re-booting the Mac as well as re-starting C1?
  
  
  
  Secondly I would create a Support Case and seek advice from the Support Team. They are usually pretty quick to reply.
  
  Being as this is primarily a User to User forum a Support case is a wise move. You cannot be sure that a user who has pertinent experience of the problem will drop my, thought one or two might do so - assuming anyone else has had the same issue at some point.
  
  HTH.
  
  
  Grant
  
  ETA: You posted in the time I was replying to your first post ... soooo .... ignore the first line (not relevant now but ....) and create the support case as suggested.
  
  I agree with your desire to understand what has happened and why you want to understand it if possible.

  0

Post is closed for comments.