Merge pull request #278069 from stevenmatthew/errcode061224

errcode061224: New status codes

Author: prmerger-automator[bot]

articles/storage-mover/status-code.md

@@ -5,7 +5,7 @@ author: stevenmatthew
 ms.author: shaas
 ms.service: azure-storage-mover
 ms.topic: how-to
-ms.date: 09/25/2023
+ms.date: 06/12/2024
 ms.custom: template-how-to
 ---
 
@@ -53,20 +53,24 @@ Each of these scopes further divides statuses into categories and subcategories.
 | <a name="AZSM1026"></a>**AZSM1026** |Target type is not supported by the agent | This target type is unsupported by the current Storage Mover agent. |
 | <a name="AZSM1027"></a>**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. |
 | <a name="AZSM1028"></a>**AZSM1028** |Key Vault access failure | Verify that the agent has been granted permissions to the relevant Key Vault. |
+| <a name="AZSM1029"></a>**AZSM1029** |Source endpoint type not supported by this agent version | This source type is unsupported by the current Storage Mover agent. |
 | <a name="AZSM1030"></a>**AZSM1030** |Cannot verify storage account type | Verify that the storage account and container exist, and that the agent has been granted permissions to them. |
+| <a name="AZSM1031"></a>**AZSM1031** |Failed to resolve target host | Review the network configuration. |
 | <a name="AZSM1040"></a>**AZSM1040** |Miscellaneous error while accessing target  | It's likely that this error is temporary. Retry the migration job again. If the issue persists, please create a support ticket for further assistance. |
 | <a name="AZSM1041"></a>**AZSM1041** |Failed to send job progress  | It's likely that this error is temporary. Retry the migration job again. If the issue persists, please create a support ticket for further assistance. |
 | <a name="AZSM1042"></a>**AZSM1042** |Failed to create job  | It's likely that this error is temporary. Retry the migration job again. If the issue persists, please create a support ticket for further assistance. |
 | <a name="AZSM1043"></a>**AZSM1043** |Failed to resume job  | Retry or create a support ticket. |
-| <a name="AZSM1044"></a>**AZSM1044** |Failed to finalize the job  | Retry or create a support ticket. |
-| <a name="AZSM1045"></a>**AZSM1045** |Job was aborted while it was still running  | Retry or create a support ticket. |
-| <a name="AZSM1060"></a>**AZSM1060** |Miscellaneous error during job execution  | Retry or create a support ticket. |
+| <a name="AZSM1044"></a>**AZSM1044** |Failed to finalize the job.  | Retry or create a support ticket. |
+| <a name="AZSM1045"></a>**AZSM1045** |Job was aborted while it was still running.  | Retry or create a support ticket. |
+| <a name="AZSM1060"></a>**AZSM1060** |Miscellaneous error during job execution.  | Retry or create a support ticket. |
 | <a name="AZSM2021"></a>**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](/azure/storage/files/storage-files-scale-targets) and [Azure Blob Storage](/azure/storage/blobs/scalability-targets) for additional information. |
 | <a name="AZSM2024"></a>**AZSM2024** |Source path length longer than max supported by target.  | Refer to guidance within the [Naming and referencing shares, directories, files, and metadata](/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata) article. |
 | <a name="AZSM2026"></a>**AZSM2026** |Source file has size larger than max supported by target.  | Refer to guidance within the [Naming and referencing shares, directories, files, and metadata](/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata) article. |
+| <a name="AZSM2027"></a>**AZSM2027** |Source file security descriptor has unsupported properties  | Review the file's or folder's permissions. |
 | <a name="AZSM2061"></a>**AZSM2061** |Unknown Error encountered when scanning the source. |  This is probably a transient error. Rerun the migration job. |
 | <a name="AZSM2062"></a>**AZSM2062** |Failed to read source file due to permission issues. | Verify that the agent has been granted permissions to the source location. |
 | <a name="AZSM2063"></a>**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, please create a support ticket for further assistance. |
 | <a name="AZSM2069"></a>**AZSM2069** |Failed to read target file due to permission issues.  | Verify that the agent has been granted permissions to the target location. |
-| <a name="AZSM2070"></a>**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. |
-| <a name="AZSM2080"></a>**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, please create a support ticket for further assistance. |
+| <a name="AZSM2070"></a>**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. |
+| <a name="AZSM2071"></a>**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, please create a support ticket for further assistance. |
+| <a name="AZSM2080"></a>**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, please create a support ticket for further assistance. |