Skip to main content

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

C1PRO7.2.2. Windows Users: Please PERFORM this SIMPLE...

Comments

4 comments

  • Wade Oram
    I after local adjustments I got (as the last two lines in the output):

    ...
    Database content error
    Database check FAILED

    There was no indication of why it failed.

    Additional to your request I performed a 'repair' at this stage and got:

    ...
    Fixing: Beginning context fixes
    No fix for: Invalid layer relationships
    ...
    Database repair FAILED

    As in your case, removing the adjustment layer resolved the issue - as you might expect given the nature of the issue as revealed by the attempted repair.

    Wade
    0
  • ronaldnztan
    Hi Wade,

    Please login and reference Case ID: 144356. From what I have read, performing a single, arbitrary modification on the local adjustment yield the same error message, yes?

    That should not happen. In other words, adding what ever edits onto a local adjustment layer should be error-free. Thank you for sticking with my video and for your patience.

    Something is wonky with the consistent "FAILED" message relating to "No Fix for Invalid Layer Relationships."

    Cheers,

    Ron
    0
  • ronaldnztan
    /* UPDATE */

    I was informed via the cast support that the team is investigating. They told me that people who were able to exactly reproduced the anomaly I observed and reported should log into their accounts and report it themselves with their hardware configuration.

    The more data P1 has, the more likely the company could flush the oddity and augment a solution in the next update cycle.

    Thank you for your time. I appreciate you.

    Best in health and "coolest" wishes,

    Ron
    0
  • ronaldnztan

    SOLVED!!!



    With the release of 7.2.3, the oddity has been fixed. I went back to my DUMMY catalog used to report the oddity and my same steps I repeated...I'm NO LONGER getting the failed messages. Thank you PhaseONE with the fix!
    0

Post is closed for comments.