Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

HELP: COP7 Crashes upon opening.

Permanently deleted user
Hi,

COP7 crashes every time I try to open a particular catalog. I've tried reinstalling COP7 as well as replacing the catalog with a backup copy. Nothing has worked, it just crashes a few seconds after opening. It works fine with other catalogs though. Any help appreciated.

Thanks,
Matt
0

Kommentare

11 Kommentare

Datum Stimmen
  • mli20
    There are numerous recent reports of corrupt catalogs and sessions:







    Technical support on these issues appear to be non-existing.

    Cheers,
    Mogens
    0
  • NN206299UL
    Sounds like a corrupt catalogue to me - have you tried starting it up whilst holding alt? This will give you the option of starting a new catalogue or session before the application opens. then at least you can either rebuild or trouble shoot the old one.
    0
  • Permanently deleted user
    I have opened other catalogs just fine, so I do believe it's a problem with the catalog. But as stated, I installed a backup copy of the catalog and the problem still exists.
    0
  • Paul Steunebrink
    Did you a verify on the catalog (File menu)?
    0
  • Permanently deleted user
    I just did that and the catalog verification came back ok/green/database verification ok. I tried to open it and COP7 crashed again. I've sent about 20 crash reports to Phase One A/S an no one has even replied.
    0
  • SFA
    [quote="MTMStudios" wrote:
    I just did that and the catalog verification came back ok/green/database verification ok. I tried to open it and COP7 crashed again. I've sent about 20 crash reports to Phase One A/S an no one has even replied.


    System generated crash reports or did you open a support case?

    If you have not opened a support case I would do so. I would not expect a response from a system generated crash report that pops up at the time of the failure (if I properly understand what you have been sending).


    Grant
    0
  • Permanently deleted user
    I've opened a support case as well. I'm just curious why the system reports would include a name,email address and description fields if no one is going to reply to the user. Anyway, the problem still persists even though I've installed backed ups of the catalog several times. COP7 seems to not be able to connect to that catalog and just shuts down.
    0
  • SFA
    [quote="MTMStudios" wrote:
    I've opened a support case as well. I'm just curious why the system reports would include a name,email address and description fields if no one is going to reply to the user. Anyway, the problem still persists even though I've installed backed ups of the catalog several times. COP7 seems to not be able to connect to that catalog and just shuts down.


    Re the failing backups ...

    Logically that would suggest that either the backups were also flawed or the problem is not withing the catalog database itself but relates to something it is attempting to connect to. Perhaps something from a "recently opened" or "recently used" record where that something is not around and, for some reason, is not trapped by the application or OS coding.

    Of course the actual problem may not be at all logical!

    By way of an example, albeit on a windows system, there were examples of parts of some applications failing simply because the default printer for the terminal had been changed. That one took a while to find - who would have guessed it? From what I remember the code failing was in the intermediate development tools rather than the application code - but the writers still had to find a way around the intermediate code problem since they had no way of ensuring that got fixed.

    It may be time to consider whether there are any specific yet seemingly unrelated changes that may have happened around the time you noticed the problem. If it is something as obscure as the printer issue there is a good chance that the log files, no matter what level of detail is being put out, won't help in making the connection.

    I assume you can't start up with one catalog and then successfully change to the problem file?

    I'm not a catalogue user so have no specific suggestions for you but one never knows when a random discussion might throw up an idea to investigate.


    Grant
    0
  • Permanently deleted user
    I can start up another catalog, but when I switch to the problem catalog, COP7 crashes. I notice that it is not connecting to the catalog before the crash.
    0
  • mli20
    [quote="SFA" wrote:


    System generated crash reports or did you open a support case?

    If you have not opened a support case I would do so....

    Grant


    Within the system it's the proper thing to do, but in all practicality it appears pointless.

    I have been waiting for meaningful help re. a corrupted catalog for a full month: None has been forthcoming.

    That's a 100+ manhours investment down the tubes.

    Currently I'm preparing to again use my previous DAM-system, in fact I just purchased an upgrade. Another pile of work, but at least I know it to be bulletproof. There's a time to cut your losses.

    Cheers,
    Mogens
    0
  • Permanently deleted user
    I just wanted to follow up on this-

    I kept importing backups from the corrupt catalog until I could finally get COP7 to stop crashing. However, it still doesn't behave normally. At first it would somehow cause the catalog to be damaged because once I closed and re-opened, it would again crash. I've resorted to selecting File > Verify Catalog and then selecting "Verify and Close" as a way to close the catalog. If I just close it normally by closing COP7, the catalog again becomes damaged and COP7 will crash upon opening it. Stability fix please!
    0

Post ist für Kommentare geschlossen.