6.6

[N29]The passive VMware vCenter Server Heartbeat server attempted to access the file: {filename}. This failed because
the file was in use by another application. Please ensure that there are no applications which access protected files running
on the passive.
Note This occurs if the vSphere Client is left running on the passive node.
Services that keep files locked on the passive node are:
■
Protected application services
■
File level anti-malware tool services
Note vCenter Server Heartbeat periodically checks for and stops any services running on the passive node.
Solution
Until the file is closed on the passive node, vCenter Server Heartbeat reports the file status and the File System
Status as Out-of-sync.
1 Set Protected Application services to Manual on both nodes and verify that they are not running on the
passive node.
2 Set Recovery Actions to Take No Action.You can set this from the Service Control Manager (SCM) for
the Protected Application services. Otherwise, the SCM restarts the Protected Application services.
3 Verify that file level anti-malware protection is not part of the protected set as the file level anti-malware
and the corresponding services are running on both machines.
Incorrect VMware Channel Configuration
An incorrectly configured channel connection can prevent proper communication and replication.
Problem
The following problems are experienced:
■
IP conflicts occur on one of the VMware Channel IP addresses
■
The VMware Channel does not connect, or connects and disconnects
Cause
The list below provides the most common misconfigurations:
■
Identical IP addresses at each end of the VMware Channel
■
IP addresses in different subnets without static routing at each end of the VMware Channel
■
VMware Channel NIC configured for DHCP when a DHCP server is not available
During installation, vCenter Server Heartbeat configures the VMware Channel NICs with user-provided
information. Incorrect information or incorrectly modifying the VMware Channel NIC configuration after installation
causes the VMware Channel to fail communicating.
On rare occasions, if the Primary and Secondary nodes have NICs of the same type in a different order, both
the name and IP address of a VMware Channel NIC on the Primary node can transfer to the Public NIC on
the Secondary node or the name and IP address of the Public NIC can transfer to a VMware Channel NIC.
Similarly, the names of the VMware Channel NICs can reverse on the Secondary node.You must reconcile
the names of the NICs with their physical identities and assign the correct IP address to each NIC on the
Secondary node.
VMware, Inc. 83
Chapter 5 vCenter Server Heartbeat Diagnostics