V-79-57344-38317 - The operation failed because the virtual center or ESX server reported that a specified file or configuration path already exists
Article ID: 100007962
Updated On:
Description
Error Message
1.Backup Job Log shows:
Completed status: Failed
Final error: 0xe00095ad - The operation failed because the virtual center or ESX server reported that a specified file or configuration path already exists.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-38317
2. VShpere Client shows:-
Create virtual machine snapshot : Cannot complete the operation because the file or folder
Cause
As per VMware:
This issue occurs when VMware ESX or ESXi tries to create a new vDiskname-delta.vmdk redolog file, but the generated filename already exists. This can occur if the -delta.vmdk redolog file does not have an associated descriptor file.
Every virtual disk is composed of two files, a "flat" or "delta" file containing the actual data and a descriptor file containing geometry and topology information. For example, vDiskname.vmdk and vDiskname-flat.vmdk or vDiskname-delta.vmdk. For more information, see Understanding virtual machine snapshots in VMware ESX (1015180).
When creating a snapshot, the host uses the lowest file number that is not in use by the chain of snapshots and does not exist on the directory. The host calculates this by checking through the descriptor files.
When the host tries to create the snapshot, it first creates the new descriptor file, then creates the associated -delta.vmdk file. If the host detects that a -delta.vmdk file with that name already exists the snapshot operation fails and the virtual machine reverts to its previous state.
Please refer to VMware KB article below for more information about this error:
Resolution
As per VMware KB article above to resolve this issue, locate and manually remove the -delta.vmdk file that does not have an associated descriptor file.
Connect to the ESX or ESXi host using the vSphere Client.
- Locate the affected virtual machine in the Inventory.
- Determine which datastore(s) the virtual machine is stored on.
- Open the Datastore Browser.
- Navigate to the working directory containing the Virtual Machine configuration files. For more information, see Creating snapshots in a different location than default virtual machine directory (1002929) .
- Confirm that remnant redolog delta.vmdk files from previous snapshots exist. For example:
- VM is currently pointed to vmname-000001.vmdk
- vmname-000001.vmdk 's parent is the VM base disk, vmname.vmdk
- A file named vmname-000002-delta.vmdk exists in the VM directory.
- The .vmx file does not reference the file named vmname-000002-delta.vmdk .
- The .vmsd file does not reference the file named vmname-000002-delta.vmdk .
- Rename or move the remnant file aside. For example, move the file vmname-000002-delta.vmdk into a backup directory.
- Retry the Create Snapshot operation, it should complete successfully.
Note : If the memory state is captured for a snapshot, a .vmsn file is created before the new .vmdk files. If the snapshot operation fails unexpectedly, the process halts and the .vmsn file is left behind. The .vmsn files can be safely removed if the virtual machine has no snapshots. If there are any snapshots, look in the .vmsd file to identify the which .vmsn files are referenced by the VM and remove the rest.
Issue/Introduction
Additional Information
