Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

vSphere Replication Management Server connection fails with the error: Unexpected status code:404 (2007463)


  • When setting up vSphere replication, configuring the vSphere Replication Management Server (VRMS) connection fails
  • You see the error:

    VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is 'Unexpected status code:404"

  • This issue occurs when DNS or host names are configured in the environment


VRMS and VMware vCenter Site Recovery Manager (SRM) have been configured to use different addresses for the vCenter Server. VRMS is commonly configured for an IP address, whereas SRM is commonly configured for FQDN.
By default, VRMS enters an IP address for the vCenter Server, where as you likely use FQDN while configuring SRM.
During the SRM installation, vCenter Server is specified by DNS, while during VRMS configuration vCenter Server is specified by an IP address. These two must match. That is, if you use DNS (FQDN) in one place, use it in the other as well.


To avoid this issue, use consistent naming when configuring SRM and vSphere Replication. Use FQDN if possible. 

If you have already experienced this issue, reconfigure the VRMS to use the correct host name of vCenter Server:
  1. Log into web interface of each VRMS (https://x.x.x.x:5480) and click the Configure tab.
  2. Click Unregister from vCenter Server to unregister the VRMS.
  3. Reinitialize the VRMS database for both sides. Consult your database administrator or documentation on how to do this.
  4. Select Manual configuration for the database connection on the VRMS.
  5. Change the vCenter Server address to be consistent with what you used in the SRM configuration. Most times this is the FQDN of the vCenter Server.
  6. Fill in the other necessary fields.
  7. Click Save and restart Service.
  8. Configure the connection again. 


  • If you receive an error indicating that the local VRM Server is not connected to the local site, wait another minute and try again.
  • The FQDNs are case sensitive.



Update History

07/26/2012 - Added note about FQDNs

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 6 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 6 Ratings