Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

Troubleshooting VMware vCenter Server Heartbeat synchronization failures

Symptoms

VMware vCenter Server Heartbeat synchronization fails
Cannot synchronize VMware vCenter Server Heartbeat
You receive an Out of synch or Synchronized and busy processing message
Cannot initiate a handshake
Cannot establish a VMware Channel connection
Replication stops and presents the following error:

Failed to write information for the file: {filename} to the disk. Either the disk is full or the quota (for the SYSTEM account) has been exceeded.

Purpose

This article provides information about resolving VMware vCenter Server Heartbeat synchronization failures including the symptoms, causes, and resolutions.

Resolution

Please validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

When VMware vCenter Server Heartbeat is started, a Full System Check occurs. This ensures that:

All protected File/Folder structure from the active server is present on the passive server
All protected Registry Keys and values from the active server are present on the passive server

After the Full System Check finishes, the File System Status and the Registry Status are shown as Synchronized. However, there may be cases when the File System Status or the Registry Status are shown as Out of synch or Synchronized and busy processing.

Ensure a service running on the passive server is not opening protected files for exclusive access. For more information, see Services running on the passive server (1008573).
Ensure the VMware Channel is configured correctly. For information about common incorrect configurations and resolutions, see Troubleshooting when VMware Channel is incorrectly configured (1008574).
Ensure there is not an incorrect or mismatched disk configuration. For more information, see Troubleshooting an incorrect or mismatched disk configuration (1008511).
Ensure the passive server does not have less space than the active server. For more information, see The passive has less space than the active server (1008575).
Ensure there are no unprotected file system features.
Ensure that registry keys are not out of sync. For more information, see:
- Troubleshooting resources issues in VMware vCenter Server (1008579).
- Troubleshooting registry security issues (1008582).

Note: If your problem still exists after trying the steps in this article, f ile a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request .

Additional Information

vCSHB-Ref-991

vCSGB-Ref-1433

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.

Feedback

1 2 3 4 5

1 2 3 4 5

Actions

Bookmark Document

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)