Error: "Failed to unregister vCenter Server. Real networks from this vCenter Server are still referenced" while unregistering old vCenter from VMware Cloud Director.
search cancel

Error: "Failed to unregister vCenter Server. Real networks from this vCenter Server are still referenced" while unregistering old vCenter from VMware Cloud Director.

book

Article ID: 397667

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • There are no Provider Virtual Data Centers associated with that vCenter.

    Error: [ ########-####-####-####-############] Failed to unregister vCenter Server "####". Real networks from this vCenter Server are still referenced.

  • This solution covers the scenario of migrating from an old vCenter Server to a new one, which already has all networks connected as they were on the old one.
  • For the scenario where you simply want to unregister this vCenter and remove all its resources from VCD, please see KB 404252

Environment

VMware Cloud Director 10.5.x
VMware Cloud Director 10.6.x

Cause

This issue might be caused by existing External Networks that still reference the associated vCenter in VCD.

Resolution

Check and remove any remaining External Networks referencing the concerned vCenter.

If after deleting all the external networks from VCD UI the issue still persisted, contact Broadcom Support and note this Article ID (397667) in the problem description. For more information, see Creating and managing Broadcom support cases