Normally you see this error when the VM has just been turned on and is still starting or when it is shutting down. Or during a vMotion operation. So I would check the task list first. And sometimes a backup software can lead to this error message if the VM is being backed up at this moment.
If you can't find a running task and there is no backup running, you can first try moving the VM to another host using vMotion or try restarting the VM.
If that doesn't help, I would either restart the vCenter Server or deregister (but don't delete!) the VM and then re-register it. Depending on the impact for you and your infrastructure.
I appreciate the response. I just rebooted the entire hyper-visor to no avail. Had properly shut down and powered up VMs. Any ideas?
Is it possible to do a vMotion to another host? Have you tried restarting the vCenter? And as last resort: Shutdown the VM, unregister it ("Remove from inventory") and re-register the VM again.
Just a single server so no way to vMotion and using vSphere, not vCenter. Small place. Going to re-register it now. Will let you know. Thanks!
De-registered and registered the VM. Powered on and attempted a snapshot. Unfortunately am still receiving the same error:
Create a new snapshot of this virtual machine
Failed - The operation is not allowed in the current state.
Oh, okay. I assumed that it was a vCenter environment.
So you already restarted the VM and rebooted the ESXi host. Furthermore, you removed the VM from the inventory and added it again. And the error still occurs.
Does it have enough free space on the datastore to take the snapshot? How do you create the snapshot? Which options have you activated (Snapshot the virtual machine's memory, Quiesce guest file system)? Have you configured anything special in the VM (PCI or USB pass-through, SCSI bus sharing or something like that)?
Which options have you activated (Snapshot the virtual machine's memory, Quiesce guest file system)?
Using the webclient I've attempted the snapshot with all the different options, with and without snapshotting mem and quiesceing the guest file system.. same error.
My datastore's used capacity is at 68%, with 712GB free.
Have you configured anything special in the VM (PCI or USB pass-through, SCSI bus sharing or something like that)?
-Going into the VM there's a warning: "The portgroup for Network adapter 2, VM Network, could not be found. It has been assigned to Server Network."
-I've deleted the 2nd network adapter since both were connected to the same virtual switch. After this change i still could not snapshot (with and without snapshotting mem)
-I don't see any other oddities or specific settings such as described in the question
By the way, for clarification: there's another active VM on this host that i CAN snapshot with no issue.
Did you ever get your snapshot failing issue resolved? I am having what appears to be the exact same problem and I have tried all the suggestions from restarting the VM and ESXi host to unregistering the VM and re-registering it. I dont know what else to try. Any advice would be greatly appreciated.
I too am having the same issue. I was testing Veeam backup and replication and yesterday all worked fine. Late lastnight I did add a pci(video card) to my vm so that plex would work better and now the backups wont run. Clearly Veeam is using vmware snapshots. Will snapshots not work if you are passing through hardware?
Yes, if you're passing through PCI devices then you can't snapshot a VM.
Well thank you for this clarification. I am currently testing by removing the video card. If this is the case this is BS. I understand they can't copy the pci devices, but com'on man they should still be able to back them up.
Sorry, not how it works!
You have resolved my issue or a least shown me the problem in my case. But how do vm's with pass-through devices get backed up? Does Veeam or other tools not have a way? Is this an unsupported setup?