Telerik Analytics
One question for everybody.
Phase One uses Telerik Analytics to monitor what we do with our Capture One. Are there any tools to look at that data? I am guessing it might give a clue as to why my app crashes on startup every time.
Thanks in advance.
Phase One uses Telerik Analytics to monitor what we do with our Capture One. Are there any tools to look at that data? I am guessing it might give a clue as to why my app crashes on startup every time.
Thanks in advance.
0
-
[quote="UCS308" wrote:
One question for everybody.
Phase One uses Telerik Analytics to monitor what we do with our Capture One. Are there any tools to look at that data? I am guessing it might give a clue as to why my app crashes on startup every time.
Thanks in advance.
Do you have more than one catalogue?
If so, can you try starting with the other one?
Or you should be able to start C1 with no catalogue.
You need to discover, at some point, whether the installation has a problem or the catalogue has a problem.
Do the log files offer any clues?
Grant0 -
Did you already try to start CO without opening the last sessions / catalogs?
Just keep the 'alt' key pressed when clicking and loading CO. CO will show the 'Recents' dialog.
If it starts well, CO is OK, start debugging your sessions / catalogs.
Regards,
Hans0 -
It is just that one catalog. It was working. Then it stopped.
From the logs.
11 -[ObjectContext objectsOfType:includeSubclasses:] + 34 (Capture One 9 + 2902705) [0x103367ab1]
11 -[ObjectContext objectsOfType:includeSubclasses:matchingKeysAndValues:queryOperator:findAll:] + 36 (Capture One 9 + 2902747) [0x103367adb]
11 -[ObjectContext objectsOfType:includeSubclasses:matchingKeysAndValues:queryOperator:findAll:includeTransient:] + 1725 (Capture One 9 + 2904478) [0x10336819e]
11 -[SQLite syncReading:error:] + 275 (Capture One 9 + 2342645) [0x1032deef5]
11 _dispatch_barrier_sync_f_slow + 594 (libdispatch.dylib + 67988) [0x7fff98804994]
11 semaphore_wait_trap + 10 (libsystem_kernel.dylib + 69550) [0x7fff8fbeffae]
*11 semaphore_wait_continue + 0 (kernel + 1029504) [0xffffff80002fb580]0 -
Please contact our Support team, so they can get you up and running again. 0 -
I have two threads on this forum for this issue. My bad.
I'll end this by saying that the catalog was created on a rad array attached via thunderbolt. I moved ( copied the catalog to local hard drive), after using it a couple of times it wouldn't open. I moved the catalog ( copied ) back to the raid array and it worked again.
So I think I will stop moving catalogs around.0
Post is closed for comments.
Comments
5 comments