1-800-691-1991 | 9am - 8pm ET

Failed to open VM attachment

KB ID: 2429
Product: Veeam ONE
Version: All
Published: 2018-01-12
Last Modified: 2020-08-13


Veeam ONE generates “Failed to open VM attachment” alarm.


Veeam ONE triggers “Failed to open VM attachment” alarm when the following Windows events are registered on the Hyper-V host:
12290 Microsoft-Windows-Hyper-V-Worker
12290 Microsoft-Windows-Hyper-V-SynthStor
12290 Microsoft-Windows-Hyper-V-VMMS
12140 Microsoft-Windows-Hyper-V-VMMS
12140 Microsoft-Windows-Hyper-V-Worker
12240 Microsoft-Windows-Hyper-V-SynthStor
These events are logged when the Hyper-V host or the Cluster node cannot access some of the VM virtual disks, configuration files, virtual memory, saving state or snapshot files. 

NOTE: In most cases, this happens when the files are located on the shared storages (for example CSV or SMB shares).


Make sure that the mentioned in the alarm details VM file is accessible from the Hyper-V host or the Hyper-V Cluster where VM is residing.

If the file is accessible, but the events continue to be triggered in the Windows Event log, you need to contact Microsoft support for further investigation.

NOTE: For SMB shares you need to additionally configure SMB delegation on the Hyper-V side. 

To enable SMB delegation, refer to the Microsoft documentation:

More information

Should you have any question, please contact Veeam Support
KB ID: 2429
Product: Veeam ONE
Version: All
Published: 2018-01-12
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.