Issue
When attempting to attach an Enterprise Server to a parent Enterprise Central, the error "Server name not unique" is encountered, despite the Enterprise Server having a unique name.
Product Line
EcoStruxure Building Operation
Environment
- Building Operation Enterprise Server
- Building Operation Enterprise Central
- Building Operation Automation Server
- Building Operation Automation Server Premium
- Building Operation Automation Server Bundled
- Building Operation Edge Server - Standard
Cause
The error may arise due to either the server's name not being unique or one of its child servers' names not being unique.
Resolution
To resolve this issue, ensure that the server's name is indeed unique, and also verify that the names of the its child servers are also unique. For example, if an Enterprise server "ES1" has a child Edge server named "Edge_1" attached to Enterprise Central "EC", and another Enterprise server "ES2" also has a child Edge server named "Edge_1", it cannot be attached to "EC" until the child Edge Server is renamed to ensure uniqueness.
