'Session database could not be read error' while opening
I have finally got round to updating from C14 to C15Pro, received my license key earlier, activation all seemed to be fine but when I start the program all I get is the following error:
'Session database could not be read error'
and then nothing happens.
(Win XP if that helps)
'Session database could not be read error'
and then nothing happens.
(Win XP if that helps)
0
-
and just tried to install, activate and run on my internet PC that is running Vista and I'm getting the same error. 0 -
Same error here after upgrading from 5.1.2 to 5.2 (Windows XP SP3) ☹️ 0 -
The first target of my suspicion would be the session file (typically *.col*). If you use the default session, either delete Capture One.col* files or create a new session to see what is happening. 0 -
Ha!
buy that man a pint 😄
I deleted both the .col file and session file and all is working, thank you.0 -
Hi Paul_E,
The problem exists as soon as you power on an external drive with pictures (and C1 is open) and after shutting down the external drive. Then after closing and reopening C1 you will get a popup (named SessionPersistency) with the message "object reference not set to an instance of an object, at P1.C1.Compinents.SessionPersistency.SelectSession (Session s)".
You're solution (creating an new session) works fine.....until you start an exernal disk again and then the problem restarts. The problem did not exist in version 5.1.2 (I went back from 5.2 to 5.1.2) so it must have something to do with changes in version 5.2.
René - The Hague - The Netherlands0 -
Hi Paul_E again,
💡 Re-reading the other posts I think my problem is not the same, because my problem is not the session database but the sessionpersistency.......I've created a support-case.
René0 -
Rene, don't work on external disks with Capture One if you want a reliable setup. 0 -
Hi Paul,
It worked for almost 5 years and now there is a upgrade to version 5.2 and it stops working. When I downgrade to version 5.1.2 everything is working again. 😕
René0 -
Hi René, hope you can sort this out with support. 0 -
[quote="Ren�91" wrote:
It worked for almost 5 years and now there is a upgrade to version 5.2 and it stops working. When I downgrade to version 5.1.2 everything is working again. 😕
Since there is great potential with external devices for a wide variety of diversity, even the smallest change in the software (likely made to address an access issue that is unrelated) can have a big impact on unforeseen hardware variances. We may be able to narrow down the variation with your external device but ultimately the advice is going to be to Store Data on the External Device and WORK off of the local boot drive. This will avoid such errors and in the end provide you with faster operation of the software.0 -
Hi everybody, especially Drew!
Yesterday I purchased an upgrade from CONE4 to CONE5PRO. After the installation i also received the dreadful message "Session database could not be read error". Since it already happened during the upgrade from CONE 4.0 to CONE 4.1 I knew that there is a bug in the installation procedure.
Here it is, how it works:
PhaseONE suggests to deinstall the old version of CONE and perform a fresh installation of a new version. This is fine, BUT the deinstallation routine does not remove some old files, scattered around your computer. Notably these are the user.config files, that are stored in this path:
C:\Documents and Settings\User\Local Settings\Application Data\Phase_One\CaptureOne.exe_Url_××××××××××××××××××××××××××××××××\4.5.22945.0
for the CONE 4.5 and correspondingly for every version of CONE that has been fresh installed or upgraded. I have three directories: one for CONE 4.0, one for CONE 4.1, and one for CONE 4.5. There is a user.config file in each of these directories. (×××××××××××××××××××××××××××××××× is a hidden name, related to the activation code.)
In addition to that there is another directory:
C:\Documents and Settings\Nikolaj\Local Settings\Application Data\Phase_One\CaptureOne.exe_Url_××××××××××××××××××××××××××××××××\5.2.41190.0
containing another user.config file related to the new installation of CONE 5.2.
Installation routine also creates a file Capture One.col during the installation here:
C:\Documents and Settings\User\My Documents\My Pictures\Capture One Library
And this file is the source of all troubles. If the installation routine finds a file Capture One.col in this directory, it creates ANOTHER file with the same name and attaches the extension corresponding to the actual version of the CONE. Therefore I found three files in this directory:
Capture One.col
Capture One.col45
Capture One.col50
In the user.config there is a correct path entry for the Capture One.col×× file:
<setting name="SessionPath" serializeAs="String">
<value>C:\Documents and Settings\User\My Documents\My Pictures\Capture One Library\Capture One.col50</value>
Now, there is obviously an issue (bug) that CONE doesn't read the correct Capture One.col×× file if there is a Capture One.col file present in this directory.
The solution:
Simply delete ALL files Capture One.col×× from the directory
C:\Documents and Settings\User\My Documents\My Pictures\Capture One Library
That's it. And, Drew, please notify the PhaseONE development department to rectify this bug which is crawling around here for at least two years.
Otherwise I would like to express my extreme satisfaction with the CaptureONE 5.2. I have Nikon D70, D200, and D700 cameras and I found the camera profiles producing a bit too contrasty and a bit cold pictures. As promised in the advertisement of the new CONE 5.2 the profiles for the Nikon DSLRs have been completely rewritten. Now they produce top quality results. Even with the default settings I get perfect pictures without any additional adjustments -- really great!
Best regards to all,
Nikolaj0 -
Hi Drew, [quote="Drew " wrote:
[quote="Ren�91" wrote:
It worked for almost 5 years and now there is a upgrade to version 5.2 and it stops working. When I downgrade to version 5.1.2 everything is working again. 😕
Since there is great potential with external devices for a wide variety of diversity, even the smallest change in the software (likely made to address an access issue that is unrelated) can have a big impact on unforeseen hardware variances. We may be able to narrow down the variation with your external device but ultimately the advice is going to be to Store Data on the External Device and WORK off of the local boot drive. This will avoid such errors and in the end provide you with faster operation of the software.
I'm always working from my local drive, so that's not the problem. The problem with the 5.2 upgrade is that....when C1 5.2 is opened and I start my external drive (without doing anything from within C1 5.2 regarding the external drive)...it becomes a part of the session and after disconnecting the external drive it's clearly still a part of the session so.......after closing and reopening C1 5.2 I get a fault message witch won't go away because the session is missing the external drive. Creating a new session only helps as long as I don't start the external drive again. The problem wasn't in version 5.1.2 and before.
I've created a support case so lets hope they can find what's the problem with the 5.2 upgrade.
René0 -
[quote="NN892472" wrote:
And, Drew, please notify the PhaseONE development department to rectify this bug which is crawling around here for at least two years.
Nikolaj,
When skipping versions the data necessary to translate from one version the next is not available. For example, going from 4.1 to 4.8.3 will result in this error. That is not necessarily a bug but rather a side effect of not staying up to date with the software. If you keep up do date you should not see this error, if you don't then it is a small nuisance that can easily be remedied.
However, that is not to say that it can't happen when staying current. There are other variables that can result in the error when updating from 5.1.2 to 5.2. Such a "variable" is the case with Rene.
Réne,
I have picked up your case and followed your directions. Although I trust that the process by which you can recreate the issue is successful for you, I cannot recreate the error and have forwarded your case/procedure to the test department for further investigation.
If anyone has an issue similar to Réne, please create a support case but keep in mind the specifics of Rénes issue as it is not the same as the OP.0 -
Hi.
I have the same problem as Rene` (Session Persistency) C1 5.2 As long as the external drive is powered, everything works fine, but as soon as I close C1 and disconnect the ext. drive I get the same message when I reopen C1. When I close C1 and connect the Ext.drive and again open C1, everything works fine. Version 5.1.2 didn`t have this problem. Using Windows 7.
Jan E.0 -
Hi Jan Erik,
I've already created a support case en support has confirmed that they can recreate what is happening and that there is a fault in the Session structure. They are working on it so we'll have to wait.
René0 -
Nikolaj's solution posted earlier worked for me today:
"Simply delete ALL files Capture One.col×× from the directory
C:\Documents and Settings\User\My Documents\My Pictures\Capture One Library"
Thanks Nikolaj
I'd been ignoring this issue for the previous few days, decided today to try to "fix" it. Tried uninstalling, reinstalling Capture One 5.2 to no avail.
Googled the error and came across this thread.
I normally have my external drive powered OFF since I rarely use the external drive. Based on this thread I powered ON the external drive, started Capture One 5 and did not get the "Object reference..." error.
Hmmm...now that I think about I may have looked for/worked on some pictures on my external drive from within Capture One a few days ago.
Exited Capture One, deleted files per Nikolaj's instructions, powered OFF the external drive, started Capture One, message box pops up saying I need to chose either default directory or QUIT, chose default, no error code, select picture folder on internal drive to work from.
Have now exited and restarted Capture One 5.2 a couple times now and it is operating normally, that is loading the previously worked from picture folder (located on my internal hard drive).0 -
i got same problem with 6.2.1 version exp
i del old ver 5 .colxxx files all related to phase one folders / reg.
thay i install fresh
and i got this error
so i search net i find this link so i do what u sugest i del all Capture One.col**
and no change , still have error and he crate only this file Capture One.col50
but stops on load 160mb and sit there forever
plz help0 -
Had this problem as well today after a crash of CO Pro 6.2.1. I clicked OK in the dialog with that message and got the Open Session dialog. I selected the default session and could work normal.
If this does not work, delete both CaptureOne.col50 as well as the preference file (user.config). For details see
http://www.phaseone.com/en/search/artic ... nguageID=1
Scroll down for the user.config file.0 -
i did that (del config file + col50)
and now no errror but soft still hangs and wont start (he says on 160 mb like before)0 -
[quote="krunoslav" wrote:
(he says on 160 mb like before)
Where does it say that?0 -
in taks menager .
edit**
solved
i deleted all phase one data from pc (reg too)
and install on other hdd and all oki now 😊)=
tnx for help0 -
Great. Thanks for feedback. 0 -
I have the same error message of 'session database could not be read'.
If I delete the .col or .col50 files as suggested, does this mean I delete all the adjustments and variants that I have created within the session related to the RAW files? If not, how can i access these again ?0 -
[quote="NNN634396612819710931" wrote:
I have the same error message of 'session database could not be read'.
If I delete the .col or .col50 files as suggested, does this mean I delete all the adjustments and variants that I have created within the session related to the RAW files? If not, how can i access these again ?
All adjustments and variants are stored in .cos files, which are located in the image folder/CaptureOne/Settings50 sub folder. The *.col50 session file does not contain image adjustments but information about the session like Favorites and Albums as well as Session Folders.
After deleting the session file create a new session in the same location with the same name as the previous one and you're done.
You can test the procedure with a dummy session first if you like.0 -
[quote="Paul_E" wrote:
[quote="NNN634396612819710931" wrote:
I have the same error message of 'session database could not be read'.
If I delete the .col or .col50 files as suggested, does this mean I delete all the adjustments and variants that I have created within the session related to the RAW files? If not, how can i access these again ?
All adjustments and variants are stored in .cos files, which are located in the image folder/CaptureOne/Settings50 sub folder. The *.col50 session file does not contain image adjustments but information about the session like Favorites and Albums as well as Session Folders.
After deleting the session file create a new session in the same location with the same name as the previous one and you're done.
You can test the procedure with a dummy session first if you like.
Thanks, sorted now 😄0
Post is closed for comments.
Comments
25 comments