Error Message

The VmwareDisk_A.log at %VCS_HOME%/logs folder would give the error below, every time a Probe is attempted.

VCS ERROR V-16-10061-22516 VMwareDisks::monitor:Failed to check if the disk '[VMware_Datastore_Name] CorrectDisk_Name.vmdk' is valid on ESX with error 'SOAP 1.1 fault: "":ServerFaultCode [no subcode]
"File [VMware_Datastore_Name] [CorrectDisk_Name]-000001.vmdk was not found"
Detail:'VCS ERROR V-16-10061-22517 VMwareDisks-VMwareDisks:monitor:Disk '[VMware_datastore_Name] [incorrectdisk_name].vmdk' is not valid on ESX

The path of the .vmdk file mentioned in the DiskPath attribute for the resource is not a valid path. 

a) From the Vcenter server, browse to the datastore path mentioned in the error and confirm the actual name for the VMDK file.

NOTE: The VMDK disks will not show up in the Hard drive list for the VM (Cluster Node) until the VMwareDisk agent comes online in VCS.on that node.

b. Modify the path for VMDK in the DiskPath attribute section of the VMwareDisk Resource in VCS with the correct name of the .vmdk files as obtained from the Vcenter. 

The 000001 in the vmdk name of [VMware_Datastore_Name] [CorrectDisk_Name]-000001.vmdk, typically indicates that a snapshot has been done on the parent vmdk file (without the 000001 in the name).  Ensure that the vmdk name in the main.cf file matches the actual vmdk name in the datastore and path.  If the snapshot is present then the 000001 or other number will be in the vmdk name.