Azure migrate error

LE MOAL Lénaïc 0 Reputation points
2024-11-26T08:03:59.3+00:00

Hi,

I have a problem to migrate VM to azure stack hci. My appliance it's correctly registered but i have this error when i try to migrate VM :

Error ID

HyperVToAzStackHCIRcmServiceReplicationCycleFailed

Error message

ErrorCode: '1002' VM: ''. Appliance: 'Not applicable'. Error: Machine of type SnapshotReplicationEngine in state ['Gateway.Service.StateMachine.SnapshotReplication.SnapshotReplicationEngineV1+WaitingForApplyCompletion' ('HandlingUnexpectedEvent)] doesn't have handling for event of type Gateway.Service.StateMachine.SnapshotReplication.UploadChangesTimeout.

Possible causes

The version of the Gateway sending the message () is not compatible with current version of the Gateway (2.31).

Recommendation

Retry the operation. If the issue persists, contact support.

Could you help me please?

Lénaïc Le Moal

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
839 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sina Salam 14,161 Reputation points
    2024-11-26T15:23:35.38+00:00

    Hello LE MOAL Lénaïc,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you are having challenges to migrate VM to Azure Stack HCI.

    Regarding your explanations, it is a version compatibility issue between the Gateway sending the message and the current version of the Gateway (2.31). The below are some steps to help you resolve this:

    1. Make sure that all components involved in the migration are running compatible versions. The error indicates a version mismatch. Verify that the Gateway version on your appliance matches the required version (2.31) for Azure Stack HCI.
    2. If you find a version mismatch, update the Gateway on your appliance to the latest version. This often resolves compatibility issues.
    3. Sometimes, simply retrying the operation can fix transient issues. Ensure all services are running correctly before attempting the migration again.
    4. Ensure there are no network issues between your Hyper-V host and Azure Stack HCI. Network interruptions can sometimes cause replication errors.
    5. Look at the logs for more detailed error messages. This can provide additional insights into what might be going wrong.
    6. If the issue persists after trying the above steps, it might be best to contact Microsoft Support from your Azure Portal. They can provide more detailed troubleshooting based on your specific environment.

    I hope this is helpful! Do not hesitate to let me know if you have any other questions.


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.