Protecting VMware vCenter Server Environments › vCenter Server Replication and High Availability › The Data Recovery Process › Troubleshooting vCenter Server Scenarios

Troubleshooting vCenter Server Scenarios

The following information is provided to help you resolve any errors and warnings.

EM00589 License Servers configured on vCenter are not consistent

Reason:

License Server deployment on the Master and Replica is not the same. One is locally installed and the other is remotely installed. These should be the same on Master and Replica.

Action:

Reconfigure the settings for the License Server on the Replica.

EM00590 Databases configured on vCenter are not consistent

Reason:

Either the deployment or the database type of the database server on the Master differs from the Replica and must be the same.

Action:

Reconfigure database settings on the Replica.

EM00591 vCenter versions configured are not consistent

Reason:

The vCenter version on the Master differs from that on the Replica and must be identical.

Action:

Re-install vCenter on the Replica.

EM00592 Distributed databases configured on vCenter are not consistent

Reason:

The Database Server hostname or instance name on the Master differs from that on the Replica and must be the same.

Action:

Reconfigure the database settings on the Replica.

EM00594 Database usernames configured for vCenter are not identical

Reason:

The account for vCenter used to access the Database Server on the Master differs from that on the Replica and should be identical.

Action:

Reconfigure the ODBC settings on the Replica.

EM00596 Oracle server name configured on replica for vCenter is not localhost

Reason:

This is a configuration error.

Action:

Change the ODBC setting using "localhost" as the hostname on the Replica.

EM00597 SQL server name configured on replica for vCenter is not localhost

Reason:

This is a configuration error.

Action:

Change the ODBC setting using "localhost" as the hostname on the Replica.

EM00598 The vCenter database names configured are not consistent

Reason:

This is a configuration problem.

Action:

Reconfigure the database settings on the Replica to match those on the Master.

EM00599 The vCenter database on master <IP Address> is distributed deployed and AR isn't supported

Reason:

If the vCenter Server database is on a remote machine, AR is not supported.

Action:

Restart Arcserve RHA. AR options should be dimmed when Arcserve RHA detects remote database deployment.

ER00603 Unknown parameter. vCenter configurations can't be compared

Reason:

This is due to an internal program error.

Action:

Retry.

ER00604 vCenter HA information is not initialized

Reason:

The Engine on the Master or Replica is having problems.

Action:

Verify the Engine is working and retry.

EM00590 Databases configured on vCenter are not consistent

Reason:

The Database server type on the Master differs from that on the Replica and must be the same.

Action:

Reconfigure the database server on the Replica.

ER00605 Failed to configure DB Server

Reason:

Something is wrong with the registry setting on the Replica: HKEY_LOCAL_MACHINE_SOFTWARE\VMware, Inc.\VMware vCenter\DB

Action:

Confirm ODBC settings for vCenter are correct and check the registry key. If it does not exist, re-install vCenter on the Replica.

ER00606 Failed to configure License Server

Reason:

Something is wrong with the registry setting on the Replica: HKEY_LOCAL_MACHINE_SOFTWARE\VMware, Inc.\VMware vCenter\vCenter

Action:

Check the registry key. If it does not exist, re-install vCenter on the Replica.

ER00607 Failed to configure Managed IP

Reason:

Something is wrong with the registry setting on the Replica: HKEY_LOCAL_MACHINE_SOFTWARE\VMware, Inc.\VMware vCenter\vCenter

Action:

Check the registry key. If it does not exist, re-install vCenter on the Replica.

ER00608 Failed to configure DB password

Reason:

Something is wrong with the registry value "3" on the Replica: HKEY_LOCAL_MACHINE_SOFTWARE\VMware, Inc.\VMware vCenter\DB

Action:

Check the registry key. If it does not exist, re-install vCenter on the Replica.

ER00609 Failed to configure Web Access Port

Reason:

Something is wrong with the registry value "WebCenterPort" on the Replica: HKEY_LOCAL_MACHINE\SOFTWARE\VMWare, Inc.\VMware vCenter

Action:

Check the registry key. If it does not exist, reinstall vCenter on the Replica.

WM00529 Distributed License Servers configured on vCenter are not consistent

Reason:

The registry value "License Path" of key HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware vCenter on Replica should be the same as on Master.

Action:

Reconfigure the license server setting on the Replica.

WM00531 License Servers configured on vCenter are not consistent

Reason:

License Server deployment on the Master and Replica is not the same. One is locally installed and the other is remotely installed. These should be the same on Master and Replica.

Action:

Reconfigure the settings of the License Server on the Replica.

WM00532 Databases configured on vCenter are not consistent

Reason:

Either the deployment or the database type of the database server on the Master differs from the Replica and must be the same.

Action:

Reconfigure database settings on the Replica.

WM00533 vCenter versions configured are not consistent

Reason:

The vCenter version on the Master differs from that on the Replica and must be identical.

Action:

Re-install vCenter on the Replica.

WM00534 Distributed databases configured on vCenter are not identical.

Reason:

The Database Server hostname or instance name on the Master differs from that on the Replica and must be the same.

Action:

Reconfigure the database settings on the Replica.

WM00535 Unable to receive vCenter information from <IP Address>

Reason:

This is an internal program error, engine disconnect or timeout.

Action:

Wait and retry the request later.

WM00536 Database usernames configured for vCenter are not identical

Reason:

The account for vCenter used to access the Database Server on the Master differs from that on the Replica and should be identical.

Action:

Reconfigure the ODBC settings on the Replica.

WM00537 WebCenter ports configured on vCenter are not identical

Reason:

The WebCenter ports on the Master differ from those set on the Replica and should be identical.

Action:

Re-install vCenter on the Replica and ensure the WebCenter ports are the same as those on the Master.

WM00538 The vCenter Managed IP <IP Address> isn't set in Move IP list

Reason:

You have set a vCenter Managed IP but not added it to the Move IP properties located in the Switchover properties list.

Action:

Add the managed IP address to the Move IP list when setting switchover properties.

WM00540 SQL server name configured on replica for vCenter is not localhost

Reason:

This is a configuration error.

Action:

Change the ODBC setting using "localhost" as the hostname on the Replica.

WM00541 License server name configured on replica for vCenter is not localhost

Reason:

This is a configuration error.

Action:

Change the value "License Path" to "xxxx@localhost" style on Replica.

WM00542 License server ports configured for vCenter are not consistent

Reason:

This is a configuration error.

Action:

Re-install vCenter to reconfigure the license server on the Replica.

WM00543 License files folders configured are not consistent

Reason:

This is a configuration problem.

Action:

Reinstall vCenter to specify the correct folder for License files.

WM00544 The vCenter database names configured are not consistent

Reason:

This is a configuration problem.

Action:

Reconfigure the database settings on the Replica to match those on the Master.

WM00588 Distributed License Servers configured on vCenter are not consistent

The registry value "License Path" of key HKEY_LOCAL_MACHINE\SOFTWARE\\VMware, Inc.\\VMware vCenter on Replica should be the same as on Master.

Action:

Reconfigure the license server setting on the Replica.

Troubleshooting Oracle Databases

Oracle database fails to start after switchover

Symptom:

My vCenter Server HA scenario uses an Oracle database. After switchover, the Oracle database does not restart and I get the following errors:

• ER00319, 83, Error, <HOSTNAME><DATE/TIME>, Switchover Aborted
• ER00303, 82, Error, <HOSTNAME><DATE/TIME>, Unable to start vCenter Services
• ER00360, 81, Error, <HOSTNAME><DATE/TIME>, Unable to start vCenter after switchover. Service 'vpxd' not started

Solution:

These errors occur when the Oracle database does not successfully mount the following switchover. Use the command line to solve the problem:

1. Shut down

   [ORACLE_HOME]\bin\oradim.exe -shutdown -sid orcl -usrpwd * -shutmode immediate
   

2. Start again

   [ORACLE_HOME]\bin\oradim.exe -startup -sid orcl -usrpwd * -nocheck 0