Enterprise Server Cannot Be Added to Enterprise Central Due to Duplicate Unique ID

[Hernan_Urueña]

Issue

When adding an Enterprise Server (ES) to an Enterprise Central (EC), the following error is displayed: 

"Cannot add a server to the system with an already existing unique ID"

Product Line

EcoStruxure Building Operation

Environment

Building Operation Enterprise Server

Building Operation Enterprise Central

Cause

The Enterprise Server has the same Globally Unique Identifier (GUID) as another Enterprise Server in the system.

The GUID is a unique identifier associated with the server configuration and database structure. An Enterprise Server that has been cloned may retain the original GUID, resulting in a duplicate unique ID within the system.

Changing the GUID of an Enterprise Server by restoring a backup with new IDs is not supported due to system integrity and object referencing constraints within EcoStruxure Building Operation.

Resolution

Restoring an Enterprise Server with new IDs (GUIDs) is not supported.

To create an Enterprise Server with a unique GUID:

1. Set up a new Enterprise Server instance.
2. Use the Export/Import feature to transfer supported objects from the existing Enterprise Server.
3. Manually recreate any settings or objects that cannot be exported.

Retaining Historical Trend Data

If historical trend data must be retained when rebuilding the Enterprise Server, the following options may be considered. These options are outside supported migration procedures and should be validated before use.

Option 1: Export and Import Trend Log Data/ Extended Trend Log Data (XML)

• Export trend log data/Extended Trend Log Data from the existing Enterprise Server to XML. Right Click on the Trend or Extended Trend log and select "View" and open it in "In Trend Log List" view. 
  

• When exporting, ensure that the configured record count includes the full history that must be retained. For example, if the export is limited to 500 records, only those 500 records will be included in the XML file.
  

• The XML data can then be imported into the corresponding Trend log/ Extended Trend Log created on the new Enterprise Server. Please ensure that the newly created Trend Log or Extended Trend Log retains the same configuration and bindings as the existing Trend Log/ Extended Trend Log configuration.  Right Click on the Trend Log/Extended Trend log created on the new Enterprise Server and select "Modification" - "Import Log Data" and navigate through the pop-up and select the required exported "Xml file". This process must be performed for each trend log requiring historical data retention.
  

Option 2: External Log Storage

If External Log Storage is being used, a similar migration approach may be possible.

Additional considerations may apply depending on how the external database is linked to the original Enterprise Server. Validation and testing are required to determine whether any dependencies exist that could impact functionality after migration.

Option 3: Export Trend Data to CSV

If the objective is to preserve historical data for reporting or analysis rather than maintaining the data within EcoStruxure Building Operation, trend log data can be exported to CSV and retained externally for use in applications such as Microsoft Excel or other reporting tools.

Important

• Test the selected approach on a representative trend log before proceeding with a production migration.
• Confirm that the retained history remains accessible and meets site requirements.
• There is no documented or supported method for preserving historical logging data when rebuilding an Enterprise Server with a new Device ID.
• Any method used to preserve historical data should be validated by the customer prior to production implementation.