File Missing Error On Session Open
I've been moving my sessions over to a new RAID array and when I went to open one I received a strange error that a file was missing. 2 sessions exhibited this behavior but others open fine. The file specified looks like it has been truncated, but worse, neither of these sessions will open now. the file path is "G:\M68ZJR~1\RNXQSF~6\_HOILG~2\_MMWVA~F" The Session is in a couple subfolders of the G: drive, but the name does not line up with anything in this supposed missing file...….any ideas?
0
-
How do you open the session?
Do you use the Open command and browse to the new location of the .cosessiondb file? That should work.
Or do you use the list of recent sessions? That won't work after relocating the session.0 -
Thanks Paul. I have tried Doubl;e Clicking the file in File Explorer (nothing happens) and I have tried Opening the Session using the Open command on the C1 File Menu. That is what produces the file error. The Session I am trying to open does not even appear in the Recents menu at all. 0 -
I would create a new session file (.cosessiondb) for those two sessions who do not open properly.
A new session file is easy to create. Basically, you rename or delete the current session file and have Capture One create a new session with the same name (copy the name) in the same location as the old session.
Because of some magic, only the missing session file is created and all the files and folders plus adjustments are untouched.
Always have a backup, it is software you know 😉0 -
Thanks Paul. Ironically, creating backups is what I was starting to do when this happened. I learned the lesson the hard way very recently and was making the backups after losing a different, separate hard drive. I'll give that a go later today and report back, cheers! 0 -
[quote="NN635705310764820168UL" wrote:
I've been moving my sessions over to a new RAID array and when I went to open one I received a strange error that a file was missing. 2 sessions exhibited this behavior but others open fine. The file specified looks like it has been truncated, but worse, neither of these sessions will open now. the file path is "G:\M68ZJR~1\RNXQSF~6\_HOILG~2\_MMWVA~F" The Session is in a couple subfolders of the G: drive, but the name does not line up with anything in this supposed missing file...….any ideas?
That path looks like something internal to the RAID process OR the copy over has been scrambled somewhere in the temporary files. The tilda symbol reminds me of long name truncation in the old days, as if the file system is limited to 8 character names.
Is this a raid system within you system of an external drive array such as a NAS device?
Grant0 -
Paul, creating the new session worked, thank you very much. I never would have thought to do that!
Grant, it IS a RAID NAS Drive. I had opened the session but Capture One hit an error on shut down and the problem cropped up on subsequent openings. I actually wound up shortening the filename a bit on the new one, so I think maybe it DID have something to do with the truncation. To Paul's point about "the magic" I wonder if the session folder only keeps certain things inside and the rest of the settings and such are held in the folders themselves parallell to the CR2 files?0 -
[quote="NN635705310764820168UL" wrote:
To Paul's point about "the magic" I wonder if the session folder only keeps certain things inside and the rest of the settings and such are held in the folders themselves parallel to the CR2 files?
Yes, your edits to the images are saved in sidecar files in a subfolder of the image's folder.0 -
Thanks Paul. That helps me understand a lot better how it ll works. 0
Post ist für Kommentare geschlossen.
Kommentare
8 Kommentare