Troubleshooting Storage Mover job run error codes

An Azure Storage Mover agent uses string status codes for statuses that are conveyed to the end user. All status codes have the prefix AZSM followed by four decimal digits. The first decimal digit indicates the high-level scope of the status. Each status code should belong to one of the following scopes:

• Status that applies to the entire agent.
  These codes use the scope digit 0, and therefore and have the prefix AZSM0.
• Status that applies to a specific job run by the agent.
  These codes use the scope digit 1 and therefore have the prefix AZSM1.
• Status that may be set by the agent on a specific file or directory that is transferred by a job run by the agent.
  These codes use the scope digit 2 and therefore have the prefix AZSM2.

Each of these scopes further divides statuses into categories and subcategories. Each subcategory typically reserves 20 status codes to accommodate future expansion.

Tip

AZSM0000 is the special scope-agnostic status code indicating successful operation and should be used to signify successful operation at any scope/level.

Error Code	Error Message	Details/Troubleshooting steps/Mitigation
AZSM1001	Failed to mount source path	Verify the provided server name or IP-address is valid, or the source location is correct. If using SMB, verify the provided username and password is correct.
AZSM1002	Encountered an error while scanning the source	Retry or create a support ticket.
AZSM1003	Failed to access source folder due to permission issues	Verify that the agent has been granted permissions to the source file share.
AZSM1004	Source path provided is invalid	Create a new endpoint with a valid source share path and update the job definition and retry.
AZSM1020	Miscellaneous error while accessing source	Retry or create a support ticket.
AZSM1021	Failed to access target folder due to permission issues	Retry or create a support ticket.
AZSM1022	Target path provided is invalid	Create a new endpoint with a valid target container and path and update the job definition and retry.
AZSM1023	Lease expired for this agent on the target container	Retry or create a support ticket.
AZSM1024	Authorization failure accessing the target location	The agent doesn't have sufficient permission to access the target location. RBAC (role-based access control) role assignments are performed automatically when resources are created using the Azure portal. If you're using the APIs, PowerShell cmdlets, or SDKs, manually create a role assignment for the agent's managed identity to access the target location. For NFS, use the Storage Blob Data Contributor role assignment. For SMB, use Storage File Data Privileged Contributor. The Assign an Azure role for access to blob data article may help resolve this issue.
AZSM1025	Authentication failure accessing the source location	Verify that the agent has been granted permissions to the source location.
AZSM1026	Target type is not supported by the agent	This target type is unsupported by the current Storage Mover agent.
AZSM1027	The target location is busy	The agent can't access the target location because an existing lease is active. This error may be caused by another agent writing to the location. Ensure no other job is running against the target. Retry or create support ticket.
AZSM1028	Key Vault access failure	Verify that the agent has been granted permissions to the relevant Key Vault.
AZSM1029	Source endpoint type not supported by this agent version	This source type is unsupported by the current Storage Mover agent.
AZSM1030	Cannot verify storage account type	Verify that the storage account and container exist, and that the agent has been granted permissions to them.
AZSM1031	Failed to resolve target host	Review the network configuration.
AZSM1040	Miscellaneous error while accessing target	It's likely that this error is temporary. Retry the migration job again. If the issue persists, create a support ticket for further assistance.
AZSM1041	Failed to send job progress	It's likely that this error is temporary. Retry the migration job again. If the issue persists, create a support ticket for further assistance.
AZSM1042	Failed to create job	It's likely that this error is temporary. Retry the migration job again. If the issue persists, create a support ticket for further assistance.
AZSM1043	Failed to resume job	Retry or create a support ticket.
AZSM1044	Failed to finalize the job.	Retry or create a support ticket.
AZSM1045	Job was aborted while it was still running.	Retry or create a support ticket.
AZSM1060	Miscellaneous error during job execution.	Retry or create a support ticket.
AZSM2021	File type not supported by target.	This target type does not support files of this type. Reference scalability and performance targets for Azure Files and Azure Blob Storage for additional information.
AZSM2024	Source path length longer than max supported by target.	Refer to guidance within the Naming and referencing shares, directories, files, and metadata article.
AZSM2026	Source file has size larger than max supported by target.	Refer to guidance within the Naming and referencing shares, directories, files, and metadata article.
AZSM2027	Source file security descriptor has unsupported properties	Review the file's or folder's permissions.
AZSM2061	Unknown Error encountered when scanning the source.	This is probably a transient error. Rerun the migration job.
AZSM2062	Failed to read source file due to permission issues.	Verify that the agent has been granted permissions to the source location.
AZSM2063	Encountered I/O error while reading source file.	It's likely that this error is temporary. Retry the migration job again. If the issue persists, create a support ticket for further assistance.
AZSM2069	Failed to read target file due to permission issues.	Verify that the agent has been granted permissions to the target location.
AZSM2070	Cannot write blob because it has an active lease	This error may be caused by another agent writing to the location. Ensure no other job is running against the target. Retry or create support ticket.
AZSM2071	Source file has been modified during transfer	It's likely that this error is temporary. Retry the migration job again. If the issue persists, create a support ticket for further assistance.
AZSM2080	Copy failed due to an unknown error	It's likely that this error is temporary. Retry the migration job again. If the issue persists, create a support ticket for further assistance.

Troubleshooting Storage Mover RBAC issues

During a job run, automatic RBAC assignments happen. If there are failures in assignments, manually add the required role assignment.

1. Navigate to the appropriate resource - Key Vault, File Share or Blob Container.
2. Navigate to Access Control (IAM).
3. Add a new role assignment: Assign Azure roles using the Azure portal - Azure RBAC | Microsoft Learn.
4. In the Add role assignment wizard, search for the appropriate role in the table below for the resource type selected in step 1. In the below example the resource would be Key Vault.

Resource Type	Roles required
Key Vault	Key Vault Secrets User
File Share	Storage File Data Privileged Contributor
Blob Container	Storage Blob Data Privileged Contributor

i. Assign access should be for “Managed Identity”.
ii. On the right pane, select Managed Identity type as Machine – Azure Arc.
iii. Select the machine arc from the list. It is of the same name as the agent.
iv. Complete the assignment.