You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An Azure Storage Mover agent uses string status codes for statuses that are conveyed to the end user. All XDM status codes have the prefix *AZSM* followed by 4 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:
28
28
29
-
1. Status that applies to the entire agent.<br />These use the scope digit '0' and hence have the prefix "AZSM0".
30
-
1. Status that applies to a specific job that is being run by the agent.<br />These use the scope digit '1' and hence have the prefix "AZSM1".
31
-
1. Status that applies to a specific file/dir being transferred by a job that is being run by the agent.<br />These use the scope digit '2' and hence have the prefix "AZSM2".
29
+
- Status that applies to the entire agent.<br />These use the scope digit '0' and hence have the prefix "AZSM0".
30
+
- Status that applies to a specific job that is being run by the agent.<br />These use the scope digit '1' and hence have the prefix "AZSM1".
31
+
- Status that applies to a specific file/dir being transferred by a job that is being run by the agent.<br />These use the scope digit '2' and hence have the prefix "AZSM2".
32
32
33
33
Each of these scopes can then further divide the statuses into categories and sub-categories and typically reserve 20 status codes for each sub-category to accommodate future expansion.
34
34
35
-
> [!IMPORTANT]
35
+
> [!TIP]
36
36
> *AZSM0000* is the special scope-agnostic status code indicating successful operation. This should be used to signify successful operation at any scope/level.
| <aname="AZSM1001">AZSM1001</a> |Failed to mount source path | Verify the provided server information, name or IP-address, is valid, or the source location is correct. |
43
-
| <aname="AZSM1002">AZSM1002</a> |Encountered an error while scanning the source | Retry or create a support ticket. |
44
-
| <aname="AZSM1003">AZSM1003</a> |Failed to access source folder due to permission issues | Check if the agent has been granted permissions correctly to the source file share. |
45
-
| <aname="AZSM1004">AZSM1004</a> |Source path provided is invalid | Create a new endpoint with a valid source share path and update the job definition and retry. |
46
-
| <aname="AZSM1020">AZSM1020</a> |Miscellaneous error while accessing source | Retry or create a support ticket. |
47
-
| <aname="AZSM1021">AZSM1021</a> |Failed to access target folder due to permission issues | Retry or create a support ticket. |
48
-
| <aname="AZSM1022">AZSM1022</a> |Target path provided is invalid | Create a new endpoint with a valid target container and path and update the job definition and retry. |
49
-
| <aname="AZSM1023">AZSM1023</a> |Lease expired for this agent on the target container | Retry or create a support ticket. |
50
-
| <aname="AZSM1024">AZSM1024</a> |Authorization failure on claiming the target container | The agent does not have the permission to access the target container. The role assignment is performed automatically while running jobs from the portal. If you are using the APIs/Powershell cmdlets/SDKs, then manually create a 'Storage Blob Data Contributor' role assignment for the agent to access the target storage account blob container. The [Assign an Azure role for access to blob data](/azure/storage/blobs/assign-azure-role-data-access) article may help resolve this issue. |
51
-
| <aname="AZSM1025">AZSM1025</a> |Authentication failure on claiming the target container | Retry or create a support ticket. |
52
-
| <aname="AZSM1026">AZSM1026</a> |Blob type in the target container not supported by the agent | This blob type is unsupported by the current Storage Mover agent. |
53
-
| <aname="AZSM1040">AZSM1040</a> |Miscellaneous error while accessing target | Retry or create a support ticket. |
54
-
| <aname="AZSM1041">AZSM1041</a> |Failed to send job progress | Retry or create a support ticket. |
55
-
| <aname="AZSM1042">AZSM1042</a> |Failed to create job | Retry or create a support ticket. |
56
-
| <aname="AZSM1043">AZSM1043</a> |Failed to resume job | Retry or create a support ticket. |
57
-
| <aname="AZSM1044">AZSM1044</a> |Failed to finalize the job | Retry or create a support ticket. |
58
-
| <aname="AZSM1045">AZSM1045</a> |Job was aborted while it was still running | Retry or create a support ticket. |
59
-
| <aname="AZSM1060">AZSM1060</a> |Miscellaneous error during job execution | Retry or create a support ticket. |
60
-
61
-
## I'd like to retain any content below this section for future work
62
-
63
-
I'd like to retain any content below this section for future work.
64
-
65
-
## Upgrade-related status codes (range AZSM0001-AZSM0020)
|"AZSM0001" | Image download during agent upgrade failed. |
70
-
|"AZSM0002" | Pre-upgrade checks for agent upgrade failed. |
71
-
|"AZSM0003" | Actual upgrade process failed. |
72
-
|"AZSM0004" | Post-upgrade checks for agent upgrade failed. |
73
-
|"AZSM0005" | Rollback for agent upgrade failed. |
74
-
75
-
## Job run-related status codes
76
-
77
-
Status codes for various job run failures. These should cover *all* possible cases of job runs failures. These will be conveyed to the user as part of "jobrunlog" telling what happened to the job.
78
-
79
-
Based on the reason for job run failure these are grouped under the following categories:
80
-
81
-
### Source-related status codes (range AZSM1001-AZSM1020)
|"AZSM1021" | Cannot access target folder due to permission issues. |
96
-
|"AZSM1022" | Invalid target path provided. |
97
-
|"AZSM1023" | Lease expired for the target container for agent. |
98
-
|"AZSM1024" | Authorization failure on claiming the target container. |
99
-
|"AZSM1025" | Authentication failure on claiming the target container. |
100
-
|"AZSM1026" | Blob type in the target container not supported by the agent. |
101
-
|"AZSM1027" | Target container is being used by some other job. |
102
-
|"AZSM1040" | Cannot access target folder due to other issues. |
103
-
104
-
### Status codes unrelated to source or target access (range AZSM1041-AZSM1060)
105
-
106
-
|Status code| Description |
107
-
|-----------|------------------------------|
108
-
|"AZSM1041" | Unable to send job progress. |
109
-
|"AZSM1042" | Failed to create job. |
110
-
|"AZSM1043" | Failed to resume the job. |
111
-
|"AZSM1044" | Failed to finalize the job. |
112
-
|"AZSM1045" | Job canceled. |
113
-
|"AZSM1060" | Job failed. |
114
-
115
-
## Copy failure-specific status codes
116
-
117
-
Status codes for various copy failures are provided below. These should cover all possible scenarios in which a source file is prevented from being copied to target. These codes will be conveyed to the user as part of the copy log.
118
-
119
-
### Excluded (status code range AZSM2001 - AZSM2020)
120
-
121
-
The file was excluded by at least one user specified filter. This is not actually an error but neverthless we make a note of it to let user know that these files were skipped due to some exclusion filter.
|"AZSM2001" | File was excluded by at least one user specified filter. |
126
-
127
-
### Unsupported (status code range AZSM2021 - AZSM2040)
128
-
129
-
One or more of the source file's characteristics makes it unfit for storing in the target, e.g., the source file may have deeper directory depths than what the target supports, or it may have path/component lengths longer than that supported by the target, or it may be a filetype not supported by the target, etc.
|"AZSM2021" | Filetype in source cannot be stored in the target. |
134
-
|"AZSM2022" | Source file path has one or more characters that are not supported by the target. |
135
-
|"AZSM2023" | Source file path has one or more components that have length larger than max component length supported by target namespace. |
136
-
|"AZSM2024" | Source file path has total length larger than max path length supported by target namespace. |
137
-
|"AZSM2025" | Source file path has directory depth larger than what target namespace supports. |
138
-
|"AZSM2026" | Source file size is larger than what target supports. |
139
-
140
-
### NoCopyNecessary (status code range AZSM2041 - AZSM2060)
141
-
142
-
The sync engine concluded that the file does not need to be copied as it has not changed since last sync. File was inferred by sync engine as "unchanged since last sync hence not needing copy".
143
-
144
-
|Status code| Description |
145
-
|-----------|------------------------------|
146
-
|"AZSM2041" | By file time |
147
-
|"AZSM2042" | By target compare |
148
-
149
-
### Failed (status code range == AZSM2061 - AZSM2080)
150
-
151
-
The copy failed due to some transient reason, either while reading from the source or writing to the target.
152
-
153
-
|Status code| Description |
154
-
|-----------|------------------------------|
155
-
|"AZSM2061" | Error encountered when scanning the source. |
156
-
|"AZSM2062" | Could not read source file due to permission issues. |
157
-
|"AZSM2063" | Encountered I/O error while reading source file. |
158
-
|"AZSM2064" | Timed out while reading source file. |
159
-
|"AZSM2065" | Transport error when sending file to target. |
160
-
|"AZSM2066" | Status returned by target. |
161
-
|"AZSM2067" | Timed out while writing file to target. |
162
-
|"AZSM2068" | Error encountered when scanning the target. |
163
-
|"AZSM2069" | Could not read/write target file due to permission issues. |
164
-
|"AZSM2070" | Could not write target file because a lease is active. |
165
-
166
-
<!--
167
-
AgentStatusMap holds a small description string corresponding to agent statuses.
XDM_CLSTATUS_EXCLUDED: "File excluded by a user specified filter",
200
-
XDM_CLSTATUS_UNSUPP_FILETYPE: "File type not supported by target",
201
-
XDM_CLSTATUS_UNSUPP_CHAR: "One or more characters in source filename not supported by target",
202
-
XDM_CLSTATUS_UNSUPP_COMPONENT_LENGTH: "One or more source path components longer than max supported by target",
203
-
XDM_CLSTATUS_UNSUPP_TOTAL_LENGTH: "Source path length longer than max supported by target",
204
-
XDM_CLSTATUS_UNSUPP_DIR_DEPTH: "Source path has directory depth larger than max supported by target",
205
-
XDM_CLSTATUS_UNSUPP_FILE_SIZE: "Source file has size larger than max supported by target",
206
-
XDM_CLSTATUS_NCN_BY_FILETIME: "File has not changed since last sync as per filetime check",
207
-
XDM_CLSTATUS_NCN_BY_TARGETCOMPARE: "File has not changed since last sync as per target compare check",
208
-
XDM_CLSTATUS_FAILED_TARGET_SCANFAILED: "Encountered an error while scanning the target",
209
-
XDM_CLSTATUS_FAILED_TARGET_PERM: "Failed to read target file due to permission issues",
210
-
XDM_CLSTATUS_FAILED_SOURCE_PERM: "Failed to read source file due to permission issues",
211
-
XDM_CLSTATUS_FAILED_SOURCE_IO: "Encountered I/O error while reading source file",
212
-
XDM_CLSTATUS_FAILED_SOURCE_TIMEDOUT: "Timed out while reading source file",
213
-
XDM_CLSTATUS_FAILED_SOURCE_SCANFAILED: "Encountered an error while scanning the source",
214
-
XDM_CLSTATUS_FAILED_TARGET_TRANSPORT: "Transport error when sending file to target",
215
-
XDM_CLSTATUS_FAILED_TARGET_IO: "Target failed file copy with an error",
216
-
XDM_CLSTATUS_FAILED_TARGET_TIMEDOUT: "Timed out while writing file to target",
217
-
XDM_CLSTATUS_FAILED_TARGET_PERM_LEASED: "Cannot write blob because it has an active lease",
218
-
-->
42
+
| <aname="AZSM1001"></a>AZSM1001 |Failed to mount source path | Verify the provided server information, name or IP-address, is valid, or the source location is correct. |
43
+
| <aname="AZSM1002"></a>AZSM1002 |Encountered an error while scanning the source | Retry or create a support ticket. |
44
+
| <aname="AZSM1003"></a>AZSM1003 |Failed to access source folder due to permission issues | Check if the agent has been granted permissions correctly to the source file share. |
45
+
| <aname="AZSM1004"></a>AZSM1004 |Source path provided is invalid | Create a new endpoint with a valid source share path and update the job definition and retry. |
46
+
| <aname="AZSM1020"></a>AZSM1020 |Miscellaneous error while accessing source | Retry or create a support ticket. |
47
+
| <aname="AZSM1021"></a>AZSM1021 |Failed to access target folder due to permission issues | Retry or create a support ticket. |
48
+
| <aname="AZSM1022"></a>AZSM1022 |Target path provided is invalid | Create a new endpoint with a valid target container and path and update the job definition and retry. |
49
+
| <aname="AZSM1023"></a>AZSM1023 |Lease expired for this agent on the target container | Retry or create a support ticket. |
50
+
| <aname="AZSM1024"></a>AZSM1024 |Authorization failure on claiming the target container | The agent does not have the permission to access the target container. The role assignment is performed automatically while running jobs from the portal. If you are using the APIs/Powershell cmdlets/SDKs, then manually create a 'Storage Blob Data Contributor' role assignment for the agent to access the target storage account blob container. The [Assign an Azure role for access to blob data](/azure/storage/blobs/assign-azure-role-data-access) article may help resolve this issue. |
51
+
| <aname="AZSM1025"></a>AZSM1025 |Authentication failure on claiming the target container | Retry or create a support ticket. |
52
+
| <aname="AZSM1026"></a>AZSM1026 |Blob type in the target container not supported by the agent | This blob type is unsupported by the current Storage Mover agent. |
53
+
| <aname="AZSM1040"></a>AZSM1040 |Miscellaneous error while accessing target | Retry or create a support ticket. |
54
+
| <aname="AZSM1041"></a>AZSM1041 |Failed to send job progress | Retry or create a support ticket. |
55
+
| <aname="AZSM1042"></a>AZSM1042 |Failed to create job | Retry or create a support ticket. |
56
+
| <aname="AZSM1043"></a>AZSM1043 |Failed to resume job | Retry or create a support ticket. |
57
+
| <aname="AZSM1044"></a>AZSM1044 |Failed to finalize the job | Retry or create a support ticket. |
58
+
| <aname="AZSM1045"></a>AZSM1045 |Job was aborted while it was still running | Retry or create a support ticket. |
59
+
| <aname="AZSM1060"></a>AZSM1060 |Miscellaneous error during job execution | Retry or create a support ticket. |
0 commit comments