Error: "Could not commit object '{Name of object}' because another object with the same name and type already exists under object '{Name of parent}'. (FWB 00026)"

Symptom

  • BOBJ Promotion Task, Package Promotion Task, Rollback task ends in warning

  • In the warning logs you find those two kinds of logs :

    1[8/11/22 12:16:02 PM] - '{Name of object}' (Folder, CUID : {CUID of object}) not properly imported. 2[8/11/22 12:16:02 PM] - Cause : Could not commit object '{Name of object}' because another object with the same name and type already exists under object '{Name of parent}'. (FWB 00026) 3 4[8/11/22 12:16:03 PM] - '{Name of object}' (Folder, CUID : {CUID of object}) not properly imported. 5[8/11/22 12:16:03 PM] - Cause : Could not commit object number {id of object} because parent object with CUID {Parent CUID} does not exist.

Environment

  • Product: 360Plus

  • Product version: irrelevant

Cause

The target CMS already contains some elements, one of them has the same name as the one we are trying to promote or rollback. However this existing element was created by hand and as a result does not have the same CUID.

Resolution

If you are running the BOBJ Promotion Task

Edit your task and check Overwrite by name for all selected types of objects :

If you are running Rollback task in Simple Replication mode

  • You can for the first run try the Full Synchronization mode, however this mode may remove some objects from your target CMS.

  • You can rename all the folders with the error FWB 00026 or move them to another folder

If you are running Rollback task in Simple Rollback mode

  • You can rename all the folders with the error FWB 00026 or move them to another folder

Last updated over 1 year ago