vSphere Replication

 View Only
Expand all | Collapse all

a general system error occurred: failed to register VRMS

williamkarl

williamkarlOct 14, 2021 05:20 PM

jasonHDC

jasonHDCDec 21, 2021 09:07 PM

  • 1.  a general system error occurred: failed to register VRMS

    Posted Aug 11, 2021 07:50 PM

    Hello,

    I kept getting error when configure vsphere replication appliance 8.4. Any idea what's wrong and how to fix this. Please help as it is really urgent task that I have to complete today. Here are the errors:

    ERROR
    Operation Failed
    A general system error occurred: Failed to register VRMS.
    Operation ID: bef61197-acf3-46ac-bffd-d45739f9217d
    8/4/21, 10:19:38 AM -0700

    ERROR

    Http failure response for 

    Https://x.x.x.:5480/configure/requrestHandlers/getUpdateInProgress:401  Unauthorized



  • 2.  RE: a general system error occurred: failed to register VRMS

    Posted Aug 11, 2021 09:02 PM

    Thread reported, asking moderators to move it to the area for vSphere Replication.



  • 3.  RE: a general system error occurred: failed to register VRMS

    Broadcom Employee
    Posted Aug 12, 2021 12:44 PM

    Hi  ,

    It is reporting '401  Unauthorized' error. If you are using Firefox, please try clearing cache or a different browser to see if similar errors are reported.

    Hope that helps.



  • 4.  RE: a general system error occurred: failed to register VRMS

    Posted Oct 14, 2021 05:20 PM

    i have same error using chrome 



  • 5.  RE: a general system error occurred: failed to register VRMS

    Posted Nov 22, 2021 09:21 AM

    my enviroment vc 6.7u3  VR8.4  is ok,but vc6.5u2 vr8.4 failed to register VRMS



  • 6.  RE: a general system error occurred: failed to register VRMS

    Posted Dec 02, 2021 12:39 PM
    ERROR
    Operation Failed A general system error occurred: Failed to register VRMS.
    Operation ID: cf7cf994-ce72-49ef-b060-928d4b821504
     
    I am also getting the same error using all browsers,
     
    Any 1 with a solution please share
     
    vsphere repl 8.4.0
     


  • 7.  RE: a general system error occurred: failed to register VRMS

    Posted Dec 12, 2021 07:39 AM

    Hi 

    Did you manage to get assistance with solving the error ? If yes please share. I am also getting the same error when I try to register vsphere repl appliance to vcenter with embedded psc



  • 8.  RE: a general system error occurred: failed to register VRMS

    Posted Dec 21, 2021 09:07 PM

    Same error here,  Any ideas on how to fix?



  • 9.  RE: a general system error occurred: failed to register VRMS

    Posted Jan 14, 2022 11:45 AM

    Same error here ...

    vCenter: 7.0.3 Build 19067387

    Site Recovery Manager: 8.5.0 Build 19066897

    vSphere Replication: 8.5.0 Build 19067387

     

    ERROR
    Operation Failed
    A general system error occurred: Failed to register VRMS.
    Operation ID: 6d842552-6366-4848-8c18-f5dde693f607

     



  • 10.  RE: a general system error occurred: failed to register VRMS

    Posted Feb 17, 2022 07:27 PM

    Operation Failed A general system error occurred: Failed to register VRMS.

    i am also getting this error any solution 



  • 11.  RE: a general system error occurred: failed to register VRMS

    Posted Feb 17, 2022 09:57 PM

    Try using the IP address instead of the appliance name at the last step of the reregister process.

    Worked for me.

    I think it is an issue with the generated certificate.

    https://kb.vmware.com/s/article/76476


  • 12.  RE: a general system error occurred: failed to register VRMS

    Posted Apr 17, 2022 03:02 AM

    There is 8.5.0.2 bug.

    Roll back to the existing version and reinstall to 8.5.0.3.

    https://docs.vmware.com/en/vSphere-Replication/8.5/rn/vsphere-replication-8503-release-notes.html
    NEW VRMS registration fails with an error after upgrade
    If you upgrade from vSphere Replication 8.3. x to version 8.5.0.1 or later, the VRMS configuration from the VRMS Appliance Management User Interface fails with the following error:


    I solved the problem like that.



  • 13.  RE: a general system error occurred: failed to register VRMS

    Posted Apr 23, 2022 01:50 AM

    I installed 8.5.0.3 and still have the problem!



  • 14.  RE: a general system error occurred: failed to register VRMS

    Posted Apr 23, 2022 06:11 PM

    Solved by installing 8.4.0.5 FYI for anyone.



  • 15.  RE: a general system error occurred: failed to register VRMS

    Posted Jun 04, 2022 04:29 PM

    I used lsdoctor after some logs in /opt/vmware/hms/hms-configtool.log was yelling about a cert mismatch.

    I had updated the dns settings on vCenter a bit ago and I guess it generated new certs and left old thumb prints, after running lsdoctor fix and rebooting vCenter vmrs registered first hit. 

    https://kb.vmware.com/s/article/80469



  • 16.  RE: a general system error occurred: failed to register VRMS

    Posted Sep 20, 2022 12:01 PM

    Just regenerate the vSphere Replication Appliance Certificate from the Vami Page and then retry. It will work. Any Version



  • 17.  RE: a general system error occurred: failed to register VRMS

    Broadcom Employee
    Posted Mar 11, 2023 07:03 AM
      |   view attached

    This problem can happen when you don't have proper DNS resolution.

    You can select Custom ( for the option - Local host ) and then below box provide the IP address of VRMS.

    Please see the attached screenshot

     

     


  • 18.  RE: a general system error occurred: failed to register VRMS

    Posted Mar 19, 2023 03:23 PM

    i try to do follow this guide, but not success, does anybody has another idea in this case



  • 19.  RE: a general system error occurred: failed to register VRMS

    Posted Jun 28, 2023 06:02 PM

    Hello

    In case anyone is still having this issue, try the following:

    In my case, I was connected via VPN to the environment and although I could access both the VC and VR using FQDNs, I kept having the issue mentioned in this thread, so I eventually logged into a server inside the VMware environment and retried re-configuring the appliance and this time it went through without any issues. I suspect it was something to do with the proxy server.