Migrate classic storage accounts to Azure Resource Manager : Unexpected error encountered while preparing migration for

Question

Migrate your classic storage accounts to Azure Resource Manager by 31 August 2024While migrating classic storage accounts to Azure Resource Manager we are facing error in prepare step;

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: {"uri""https://management.azure.com/subscriptions/XXXXXXXXXXXXXX/resourceGroups/Default-Storage-WestUS/providers/Microsoft.ClassicStorage/storageAccounts/cloudassertdownloads/operationStatuses/XXXXXXXXXXXXXXXXX?api-version=2016-11-01&return- path=","type":"GET","pathAndQuery":"","requestld":"d748f659-1af5-4225-9df4-b802d8fc900e","failureCause":"","sessionld":"62f788ec0c4e46ddb52733af4efaf0a7","commandName":"Microsoft_Azure_Storage.classicVNet_prepareMigration","status":409,"statusText":"error","duration":723.7999999970198} errorLevel: 2 errorThrown: extension: Microsoft_Azure_Storage innerErrors: [ qXHR: {"readyState":4,"responseText":"{"error":"code":"OperationFailed","message"A"The operation 'XXXXXXXXXXX failed: 'The server encountered an internal error. Please retry the request.""]","responseJSON":{"error":{"code":"OperationFailed","message":"The operation xXXXXXXXXXXX" failed: 'The server encountered an intemnal error. Please retry the request."."]},"status":409,"statusText":"error"} message: ajaxExtended call failed name: AjaxError stack: AjaxError: ajaxExtended call failed at n.t (https://portal.azure.com/Content/Dynamic/Xh2GpdhKLcYO.js:57:857)"https://portal.azure.com/content/dynamic/xh2gpdhklcyo.js:57:857)") at new n (https://portal.azure.com/Content/Dynamic/v6KMjxxrSFVy.js:1:47295)"https://portal.azure.com/content/dynamic/v6kmjxxrsfvy.js:1:47295)") at k.reject (https://portal.azure.com/Content/Dynamic/v6KMjxxrSFVy.js:1:144335)"https://portal.azure.com/content/dynamic/v6kmjxxrsfvy.js:1:144335)") at Object .< anonymous> (https://portal.azure.com/Content/Dynamic/v6KMjxxrSFVy.js:1:144132)"https://portal.azure.com/content/dynamic/v6kmjxxrsfvy.js:1:144132)") at u (https://portal.azure.com/Content/Dynamic/Xh2GpdhKLcYO.js:42:22828)"https://portal.azure.com/content/dynamic/xh2gpdhklcyo.js:42:22828)") at c (https://portal.azure.com/Content/Dynamic/Xh2GpdhKLcYO.js:42:23130)"https://portal.azure.com/content/dynamic/xh2gpdhklcyo.js:42:23130)") textStatus: error timestamp: 6028757.700000003 type: MsPortalFx.Errors.AjaxError

Answer 1

Hi Dhivya S - Thanks for reaching out over Q&A Forum.Looking at the exception, there are 2 possibilities in here:

1. Some Portal Contention and should ideally work over retry. (Less likely)
2. Some backend Issue and you might need to check with support team further for detailed troubleshooting and further assistance.

Hope that helps!

Answer 2

Hello Dhivya S,

Greetings! Welcome to Microsoft Q&A Platform.

I understand that you are encountering issues when migrating your classic storage accounts to Azure Resource Manager Storage account with error status":409,"{"error":"code":"OperationFailed","message"A"The operation 'XXXXXXXXXXX failed: 'The server encountered an internal error." while preparing migration.

If you are facing issues with the Azure backend, you can try the following steps to migrate your Classic Storage account to ARM:

1. Use the Azure Storage Explorer tool to copy the data from the Classic Storage account to a new ARM Storage account. You can download the Azure Storage Explorer tool from the following link: https://azure.microsoft.com/en-us/features/storage-explorer/
2. Once you have copied the data to the new ARM Storage account, you can update your application to use the new ARM Storage account.
3. Classic storage accounts may contain classic (unmanaged) disks, virtual machine images, and operating system (OS) images. To migrate the account, you will need to delete these artifacts first. If you do not delete classic disk artifacts first, the migration may fail. After deleting the disk artifacts, you can proceed with the migration. Please check to see if this is the case and delete them then retry the migration. The commands to find these resources are in the section here. After the migration, ensure your applications are updated to use the Azure Resource Manager APIs.

This article catalogs the most common errors and mitigations during the migration of Classic to Azure Resource Manager migration.

Identify classic storage accounts in your subscription: You can do this via the Azure portal or PowerShell.

Step-by-Step process: https://learn.microsoft.com/en-us/azure/storage/common/classic-account-migrate?tabs=azure-powershell

Addition information: How to migrate your classic storage accounts to Azure Resource Manager, https://stackoverflow.com/questions/73057732/error-migrating-azure-classic-storage-to-arm,https://learn.microsoft.com/en-us/answers/questions/1489959/how-to-backup-or-recovery-classic-storage-account

In some cases, this is a transient error that goes away with a retry. If it continues to persist, contact Azure support as it needs investigation of platform logs.

Please let us know if you have any further queries. I’m happy to assist you further.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.