Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
Registration of vCenter backup proxy fails with PHOENIX127
Registration of vCenter backup proxy fails with PHOENIX127
Updated over 10 months ago

Problem description

Activation of vCenter backup proxy fails with Error Code: PHOENIX127 - Error: vm-mor is not found for uuid: 420fe0c8-96bc-a268-6210-09edb133a5c4 (#10000007f) (Error Code : PHOENIX127)

Cause

The vCenter backup proxy registration can fail in two instances of incorrect configuration:

  1. Incorrect vCenter credentials

  2. Presence of the same vCenter backup proxy in another organization

Resolution

Scenario 1: Incorrect vCenter credentials

Error

Log Name: main_service.log

Location on Backup proxy: /var/log/Phoenix

Please enter the authentication token generated from Phoenix to enable communication to Phoenix cloud.

Activation token : 22827-2851-3601-c58613ef014254a6b16524236e87fd4b496e2fc0dbdecf67db32084ee03c9568

Registration failed with error:

Activating backup proxy, this may take some time....

Please Ensure that Backup Proxy detail is updated and vCenter detail is correct.

Error: vm-mor is not found for uuid: 420fe0c8-96bc-a268-6210-09edb133a5c4 (#10000007f) (Error Code : PHOENIX127)

Solution

Update the vCenter credentials. For detailed instructions, see the How to update vCenter credentials over a vCenter backup proxy from Phoenix Management Console article.

Scenario 2: Presence of the same vCenter Backup Proxy in another organization

You see this error if the backup proxy is registered with the vCenter (FQDN Name or IP address or vCenter Servername ) in different organizations.

.

Error

Log Name: main_service.log

Location on Backup proxy: /var/log/Phoenix

[2019-03-26 10:13:19,386] Output:

Solution

Register the vCenter backup proxy in one organization with the FQDN name, vCenter Server name and with the IP address in the other.

Did this answer your question?