https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMjk2IiwiaGFzaCI6ImJhMmZkYTVlLWI0OTgtNDBiZi05Njc2LTk1ZTc3MGIyNDdkMCJ9
1-800-691-1991 | 9am - 8pm ET
EN

CreateSnapshot failed, the operation is not allowed in the current state

Challenge


Cause

This issue occurs if the vCenter management agents have stopped causing the snapshot attempt to move in to the ON_SHUTTING_DOWN state.

Solution

To resolve this issue restart the VMware agents:

  1. Ensure that the Virtual machine startup / shutdown with host feature is disabled before this step.

  2. Restart the management agents on the host. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490).

  3. On vCenter Server, restart the vCenter and Management Web services. For more information, see Stopping, starting, or restarting vCenter services (1003895).

  4. Attempt the snapshot again. 

  5. The operation succeeds and the corresponding log entry for the snapshot attempt reflects a transition from ON to CREATE SNAPSHOT instead of ON_SHUTTING_DOWN.

 

VMware KB:
 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027707


KB ID:
1296
Product:
Veeam Backup & Replication
Version:
5.x
Published:
2011-10-13
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later