3

I have the following error when publishing a component:

Phase: Deployment Prepare Commit Phase failed, Unable to prepare transaction: tcm:0-890101-66560,
         org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta],
         org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta], Unable to prepare transaction: tcm:0-890101-66560,
         org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta],
         org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta]

This is the same topic addressed in: Publishing failed in stage Committing Deployment SDL Tridion 2011 SP1 - HR1

I've tried everything, I've already applied the accumulative hotfix CD_2011.1.1.83467, I edited the component and removed all binaries component and I still getting the same error.

The weird thing is I'm getting the error only in one publication, in the others I'm able to publish this component without any error.

Do you have any idea what else can I do ??

2 Answers 2

1

You can do a test by creating a new broker db and publishing the same item to it. If it's successful then it could be a metadata is corrupted in the original broker db

1
  • Hi Rober,Thanks for your answer, but no, I can't create a new broker db, but i think the same, the metadata for this item could be corrupted. I solved it creating a new component.
    – Carolina
    Commented Oct 1, 2014 at 13:51
0

Sometimes this problem occurs when you get backup of CMS DB from Live environment but not of Broker or vice versa. so tcm-id gets out of sync. if you create component having tcm-id 180-12345, but that id already exists in broker and associated metadata tables, it will throw the above constraint violation.

Solution: take backup of both db or take CMS backup and republish content on empty Broker DB (preferred approach)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.