Troubleshooting Tip: How to resolve the FortiManager error 'Object already exists in the ADOM' on Global Database association
| Description | This article describes how to resolve an 'Object already exists in the ADOM' error received from FortiManager while executing a task to assign a Global Database policy package to an ADOM. |
| Scope | FortiManager. |
| Solution | In FortiManager with the Multi-ADOM feature enabled (a document explaining this feature is provided at the end of this article), navigate to Global Database ADOM -> Policy & Package. There is a Global Database and other Global Policy Packages are eventually created. Try to push one or more Policy Packages to an ADOM:
A task will appear in a window with Report Progress. If the task fails and shows the error 'Local Adom already has object fw_addgrp name: xxx' (where 'xxx' is the object name), there are two possible scenarios:
To search for the 'xxx' object on the Destination ADOM, navigate to Destination ADOM -> Policy & Objects -> Objects Configuration -> Firewall Objects -> Addresses:
The issue can be solved by resetting the UUID of the object 'xxx' on the CDB database (which is the object configuration database).
To do this:
config firewall addrgrp edit "xxx" unset uuid next end
Note: It Is necessary to lock ADOMs before undertaking the steps described. For an explanation, see this section of the FortiManager administration guide.
Related documents: Checking FortiManager databases - FortiManager administration guide. Managing policy packages - FortiManager administration guide. Checking FortiManager databases - FortiManager upgrade guide. Technical Tip: How to check FortiManager database integrity prior to upgrade. |


