5.5

Table Of Contents
Troubleshooting SRM Installation and
Configuration 12
Known troubleshooting information can help you diagnose and correct problems during the installation and
configuration of SRM.
Solution
n
Cannot Restore SQL Database to a 32-Bit Target Virtual Machine During SRM Upgrade on page 96
You might encounter problems restoring a SQL database on a 32-bit target virtual machine when you
upgrade or migrate SRM.
n
SRM Server Does Not Start on page 97
SRM depends on other services. If one of those services is not running, the SRM Server does not start.
n
vSphere Client Cannot Connect to SRM on page 98
Connecting to the SRM interface in the vSphere Client fails.
n
Site Pairing Fails Because of Different Certificate Trust Methods on page 99
If you use custom certificates that a certificate authority signs, connecting the SRM sites fails if the root
certificate from the certificate authority is not present on SRM Server.
n
Error at vService Bindings When Deploying the vSphere Replication Appliance on page 99
When you deploy the vSphere Replication appliance, you get an error at vService bindings in the
Deploy OVF Template wizard.
n
OVF Package is Invalid and Cannot be Deployed on page 100
When you attempt to deploy OVF for the vSphere Replication appliance, an OVF package error might
occur.
n
vSphere Replication Appliance or vSphere Replication Server Does Not Deploy from the SRM
Interface on page 100
If problems occur when you use the SRM interface to deploy a vSphere Replication appliance or a
vSphere Replication server, you can deploy the OVF manually.
n
Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved on page 100
You cannot resolve a connection error between the vSphere Replication appliance and SQL Server.
n
404 Error Message when Attempting to Pair vSphere Replication Appliances on page 101
Pairing vSphere Replication appliances might result in a 404 error message.
n
vSphere Replication Service Fails with Unresolved Host Error on page 102
If the address of vCenter Server is not set to a fully qualified domain name (FQDN) or to a literal
address, the vSphere Replication service can stop unexpectedly or fail to start after a reboot.
VMware, Inc.
95