APIM platform migration for internal vnet injected not working

Amoghavarsh Patil 60 Reputation points
2024-07-22T04:58:23.3633333+00:00

Hello Team,

I was able to do APIM platform migration from stv1 to stv2 for 2 of instance,

But i followed same step for other 2 APIM in last 2 days and not able to do it.

Reverting back to stv1 without throwing any error

Followed same microsoft document worked previously now not working

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
2,161 questions
{count} votes

Accepted answer
  1. JananiRamesh-MSFT 27,826 Reputation points
    2024-07-25T07:18:40.3+00:00

    @Amoghavarsh Patil Thanks for the update. From the logs i see that your APIM instance got successfully migrated to stv2.
    User's image

    When I further investigated, I see the below error Stv 2 Migration for region East US started at 7/24/2024 4:13:52 PM. Failed at 7/24/2024 4:13:53 PM. - 82ca600f-ab85-4fb3-a341-38a3ce863ae9

    Exceptions:

    StatusCode : Conflict\r\nStatusMessage : {\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "InternalServerError",\r\n "message": "An error occurred.

    System.NullReferenceException: Object reference not set to an instance of an object.

    sometimes a failure can be caused by a transient platform issue. we suggest retrying the operation. going forward if you experience 2 consecutive failures, please open a support ticket with Azure Api Management support.

    do let me know incase of further queries, I would be happy to assist you.

    0 comments No comments

0 additional answers

Sort by: Most helpful

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.