- Knowledge Base Listing Page
- Failed to open VM attachment
Failed to open VM attachment
| KB ID: | 2429 |
| Product: | Veeam ONE |
| Version: | All |
| Published: | 2018-01-12 |
| Last Modified: | 2020-08-13 |
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
Veeam ONE generates “Failed to open VM attachment” alarm.
Cause
Veeam ONE triggers “Failed to open VM attachment” alarm when the following Windows events are registered on the Hyper-V host:
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).
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
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).
Solution
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:
https://docs.microsoft.com/en-us/powershell/module/smbshare/enable-smbdelegation?view=win10-ps
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:
https://docs.microsoft.com/en-us/powershell/module/smbshare/enable-smbdelegation?view=win10-ps
More information
Should you have any question, please contact Veeam Support
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.