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.

    • Related Articles

    • Promotion & Backup of BusinessObjects UNX Universes and Users — Design Behavior and Synchronization Logic

      Overview When promoting or backing up UNX universes and users with 360Plus, you may notice that UNX files are always overwritten and that user timestamps change frequently. This behavior is by design on the BusinessObjects side and cannot be modified ...

    • 360Suite - REPO003: Error while updating the backup repository structure

      Symptom Error when running a backup task, specifically after a 360Suite upgrade or a reinstallation of the application using the same database. Error : "REPO003: Error while updating the backup repository structure" Environment 360Suite Any DBMS ...

    • SQL Anywhere: JZ0C0: Connection already closed

      Symptoms When running Web Intelligence (WebI) jobs in SAP BusinessObjects connected to a SQL Anywhere (Sybase) audit database, the job may fail with the following error: JZ0C0: Connection already closed. This results in WebI job crashes and ...

    • 360Plus backup repository size calculation

      Introduction This document explains how to estimate the size of the 360Plus backup repository. The retrieved information comes from performance tests ran in our Dev labs and customers environment. The numbers may change depending on SAP ...

    • How to leverage 360Plus

      Overview This article explains how to leverage the 360Plus module. 360Plus helps you define backup strategies, search and compare backup copies, restore objects from backups, recover deleted content through the recycle bin, and automate SAP ...