When attempting to add a new Automation Server under an Enterprise Server that already has one or more AS servers attached it results in an "Object already exists" error
Object already exists
Domain: Data access
Info:~/System/Server Communication/Models/xxxxxxxx/Members/xxxxxxxxx in module Run Db manager
xxxxxxxx = Global Unique Identifier (GUID)
The AS that is being added has been restored from a backup created from one of the servers that are already configured under the ES resulting in a duplicate GUID.
The GUID underlined in red in the screenshot above is the duplicated Id.
When restoring a backup into an AS that came from a different AS, with the intent of re-using the configuration, make sure to select the 'Restore configuration with new IDs' check box. This will ensure that a new GUID is assigned to the AS
Please note that the restore function to re-use configuration data from a backup set is supported for all Building Operation supported protocols, except for BACnet and b3 BACnet.
To read more see Web Help