Salta al contenuto principale

File does not exist

Thread needs solution

Hey,

I have a problem with some vm's in vmProtect 9.
I got an error message to a file that does not exist in the folder:
Nachricht: Download der Datei 'https://192.168.1.60:443/folder/vmname.de/%23vmname.de_DX11-000001.vmdk…' fehlgeschlagen.
--------------------

Can you help me?

The whole error:

Die Aktion 'Sichernd' ist fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 26
Module: 100
Zeileninfo: 48afbd3608a410ca
Felder:
Nachricht: Die Aktion 'Sichernd' ist fehlgeschlagen.
--------------------
Fehlercode: 1080
Module: 1
Zeileninfo: b43e776571144dee
Felder:
Nachricht: Endgültiges Ausführen des Aktionsergebnisses ist fehlgeschlagen.
--------------------
Fehlercode: 104
Module: 1
Zeileninfo: bb03ce40e9a37f69
Felder:
Nachricht: Backup der zusätzlichen Datei '#vmname.de-000001.vmdk' fehlgeschlagen.
--------------------
Fehlercode: 404
Module: 0
Zeileninfo: 3a807318633ed6fe
Felder:
Nachricht: Download der Datei 'https://192.168.1.60:443/folder/vmname.de/%23vmname.de_DX11-000001.vmdk…' fehlgeschlagen.
--------------------

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Jonas,

The file referred in the error message is the vmdk descriptor which contains the metadata of the snapshot virtual disk. This file can be seen through web browser if you open https://192.168.1.60:443/folder/vmname.de/ URL (this file doesn't show up in vSphere Datastore Browser) when the snapshot of the VM is created. You should try downloading some file from the VM folder using the above URL, for example small .vmx file. This download backed by vSphere web server should work in order for VM backup to work. If the download doesn't work then it makes sense to reboot the vCenter and check whether some other files can be downloaded: the download may be sensitive to VM names and "#" symbol in the beginning of the name of the file may be a problem.

See also the following KB article describing the issue: https://kb.acronis.com/content/32037

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager