Unexpected vSphere Replication Failure Results in a Generic Error

vSphere Replication includes a generic error message in the logs when certain unexpected failures occur.

Problem

Certain unexpected vSphere Replication failures result in the error message VRM Server generic error. Please check the documentation for any troubleshooting information..

In addition to the generic error, the message provides more detailed information about the problem, similar to the following examples.

• VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: 'org.apache.http.conn.HttpHostConnectException: Connection to https://vCenter_Server_address refused'. This error relates to problems connecting to vCenter Server.
• Error - VR synchronization failed for VRM group virtual machine name. Sync monitoring aborted. Please verify replication traffic connectivity between source host and target VR server. Sync will automatically resume when connectivity issues are resolved.. This problem relates to a synchronization operation error.
• Error - Unable to reverse replication for the virtual machine 'virtual machine name'. VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: 'org.hibernate.exception.LockAcquisitionException: Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. This problem relates to a deadlock in Microsoft SQL Server.

Cause

vSphere Replication sends this message when it encounters configuration or infrastructure errors. For example, network issues, database connection issues, or host overload.

Solution

Check the detailed exception message for information about the problem. Depending on the details of the message, you can try to retry the failed operation, restart vSphere Replication, or correct the infrastructure.