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)"

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)"

Symptoms

  1. BOBJ Promotion Task, Package Promotion Task, Rollback task end in warning.
  2. In the task logs, the following messages can be found:
Quote
'{Name of object}' (Folder, CUID : {CUID of object}) not properly imported.
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)
Quote
'{Name of object}' (Folder, CUID : {CUID of object}) not properly imported.
Cause : Could not commit object number {id of object} because parent object with CUID {Parent CUID} does not exist.

Cause

The target CMS already contains some elements, one of them has the same name as the one being promoted or rolled back. However this existing element was created manually (i.e. not through a previous promotion or rollback) and as a result does not have the same CUID.

Resolution

When running a BOBJ Promotion Task

Edit your task and enable the "Overwrite by name" option for all selected types of objects.

When running a Rollback Task with Simple Replication mode

Either use the Full Synchronization mode (for the first rollback run).
Info
Note: this mode may remove some objects from your target CMS. See our Backup Strategy documentation here.

Or rename or move to another location all the elements showing the "FWB 00026" error.

When running a Rollback Task with Simple Rollback mode

Rename or move to another location all the elements showing the "FWB 00026" error.