OPERATIONAL DEFECT DATABASE
...
...
BugZero updated this defect 207 days ago.
You are unable to RECONFIGURE VRMS after upgrading to 8.X - ERROROperation FailedA general system error occurred: Failed to register VRMS.Operation ID: 88a7560b-f107-40e6-9476-489daf8da4191/13/22, 2:48:35 PM -0700 VR & vCenter logs shows the messages below. drconfig.log: --> Exception: vSphere Replication Appliance configuration error:vCenter Server extension configuration problem.--> Details: Unable to register extension in vCenter Server.--> [ msgId: com.vmware.vr.config.ext_config_failure; value: null; errorStacktrace : com.vmware.jvsl.cfg.ConfigException: Internal error.--> at com.vmware.jvsl.cfg.RegisterExtensionCommand.execute(RegisterExtensionCommand.java:153)--> at com.vmware.hms.config.helper.VcHelper.registerExtension(VcHelper.java:257)--> at com.vmware.hms.config.VrConfig.expressSetup(VrConfig.java:332)--> at com.vmware.hms.config.cli.command.ExpressSetup.run(ExpressSetup.java:58)--> at com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:305)--> at com.vmware.hms.config.cli.App.run(App.java:151)--> at com.vmware.hms.config.cli.App.main(App.java:209)--> Caused by: (vim.fault.AlreadyExists) {--> faultCause = null,--> faultMessage = null,--> name = null--> } vpxd.log : 2022-01-13T23:07:21.353Z info vpxd[07184] [Originator@6876 sub=vpxLro opID=73d3f128] [VpxLRO] -- BEGIN lro-15188940 -- AuthorizationManager -- vim.AuthorizationManager.updateRole -- 52c82293-e339-a4ad-9c25-7fb79e265962(529903de-cd2f-ff3a-3add-f0636826f490)2022-01-13T23:07:21.354Z warning vpxd[07184] [Originator@6876 sub=AuthorizeManager opID=73d3f128] Role with name 'HmsCloudAdmin' already exists2022-01-13T23:07:21.354Z info vpxd[07184] [Originator@6876 sub=vpxLro opID=73d3f128] [VpxLRO] -- FINISH lro-151889402022-01-13T23:07:21.354Z info vpxd[07184] [Originator@6876 sub=Default opID=73d3f128] [VpxLRO] -- ERROR lro-15188940 -- AuthorizationManager -- vim.AuthorizationManager.updateRole: vim.fault.AlreadyExists:--> Result:--> (vim.fault.AlreadyExists) {--> faultCause = (vmodl.MethodFault) null,--> faultMessage = <unset>,--> name = <unset>--> msg = ""--> }--> Args:-->--> Arg roleId:--> -1440203378--> Arg newName:--> "HmsCloudAdmin"--> Arg privIds:--> (string) [--> "System.Read",--> "Host.Hbr.HbrManagement",--> "VirtualMachine.Hbr.ConfigureReplication",--> "VirtualMachine.Hbr.ReplicaManagement",--> "VirtualMachine.Hbr.MonitorReplication",--> "HmsRemote.com.vmware.vcHms.Hbr.View",--> "HmsRemote.com.vmware.vcHms.Hms.Manage",--> "HmsRemote.com.vmware.vcHms.Hms.View",--> "HmsReplication.com.vmware.vcHms.Replication.View",--> "HmsDatastoreMapper.com.vmware.vcHms.Mappings.Manage",--> "HmsDatastoreMapper.com.vmware.vcHms.Mappings.View",--> "HmsDiagnostics.com.vmware.vcHms.Diagnostics.Manage",--> "HmsSession.com.vmware.vcHms.Session.Terminate",--> "Datastore.FileManagement",--> "Datastore.Browse",--> "Datastore.Config",--> "VirtualMachine.Config.AddExistingDisk",--> "VirtualMachine.Config.AddRemoveDevice",--> "VirtualMachine.Interact.PowerOn",--> "VirtualMachine.Interact.DeviceConnection",--> "VirtualMachine.Inventory.Register",--> "VirtualMachine.Inventory.Unregister",--> "VirtualMachine.State.RemoveSnapshot",--> "Resource.AssignVMToPool",--> "StorageProfile.View"--> ]
Multiple VRM roles found in linked vCenter
Removed 'com.vmware.vcHms' from the vCenter MOB Removed all the VRM roles from vCenter/s in linked mode Now, you should be able to successfully register the appliance.
5.25
Failed to register VRMS after upgrading to 8.X due to multiple VRM roles in vCenter5.25
ESXi host lost management connectivity during maintenance mode VMware NSX upgrade5.25
Applying individual product updates to VMware Cloud Foundation environments using Async Patch Tool (AP Tool)5.25
High Disk Usage in /var/log5.25
Troubleshooting Horizon 8 Edge Connectivity Issues
