Share via

Cloud Service Migration to ARM error

Schifter, Gabriela 160 Reputation points
2024-07-08T21:04:12.6+00:00

We receive this error when going through the preparation stage of a cloud service classic migration to ARM

Unexpected error encountered while preparing migration. Click here to create a new support request. The error was: baseTypes: ["MsPortalFx. Errors AjaxError", "MsPortalFx.Errors.Error']

data: ["url":"https://management.azure.com/subscriptions/38142e77-4c5c-40a6-9fc7-

Ба694683c19/resourceGroups/SCCM_Resources/providers/Microsoft.Classic Compute/domainNames/SCCMCMGARM/slots/production/operationStatuses/6401dbf124a90eefa86b131dea1009647api-version-2017-11-15&return

path="/"type":"GET"/"pathAndQuery"" "requestid" "291f80d1-9716-4795-9464- 1905 130-3017" "failureCause", "sessionid":"31643007e1ca46f289e7cf599844d4af", "commandName":"Microsoft Azure CloudServices.classicVNet prepareMigration" "status":409"statusText": "error", "duration":1408 1000000014901)

errorLevel: 2 errorThrown

extension: Microsoft Azure Cloud Services

InnerErrors:

jqXHR : ['readyState":4,"responseText":"{"error":{"code":"OperationFailed","message":"The operation 6401dbf124a90eefa86b131dea1c0964' failed: "Migration could not be completed on deployment

80115cf3bf20462abb81b06f974bc3d0 in hosted service SCCMCMGARM because the deployment's metadata is stale. Please abort the migration and upgrade the deployment before retrying migration. Validation Message: The service name SCCMProxy in the service defintion file does not match the name 'sccmcmgarm' in the service configuration file "II" "response/SON":["error":{"code":"Operation Failed", "message":"The operation 6401dbf124a90eefa86b131deal:0964' failed: 'Migration could not be completed on deployment 80115cf3bf20462abb51b06f974bc3d0 in hosted service SCCMCMGARM because the deployment's metadata is stale. Please abort the migration and upgrade the deployment before retrying migration. Validation Message: The service name 'SCCMProxy in the service defintion file does not match the name 'scomcmgarm in the service configuration

file", "status" 409,"status Text": "error")

message: ajaxExtended call failed

name: AjaxError

stack: AjaxError: ajaxExtended call failed

at nit (https://portal.azure.com/Content/Dynamic/qUqF8XzAdiSx.js:57:857)

at new n (https://portal.azure.com/Content/Dynamic/P6EcjwX46u5n.js:1:47295)

at kreject (https://portal.azure.com/Content/Dynamic/P6EojwX46u5n.js1:144336)

at Object. <anonymous> (https://portal.azure.com/Content/Dynamic/P6EojwX46u5n.js:1:1441331

at u (https://portal.azure.com/Content/Dynamic/qUqF8XzAdlSx.js:42:22828) at c (https://portal.azure.com/Content/Dynamic/qUqF8XzAdlSx.js:42:23130)

textStatus: error

timestamp: 254044

type: MsPortalFx Errors.AjaxError

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
754 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. hossein jalilian 5,400 Reputation points
    2024-07-08T23:51:01.87+00:00

    Thanks for posting your question in the Microsoft Q&A forum.

    Before retrying the migration, you need to upgrade the deployment. This should refresh the metadata and resolve the stale data issue. review your service definition (.csdef) and service configuration (.cscfg) files. Ensure that the service name is consistent between these files. Update them if necessary to use the same service name.

    After updating the files, redeploy your cloud service to ensure all changes are applied and the metadata is fresh. once you've completed these steps, attempt the migration process again.

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