Skip to content

Commit 30654ca

Browse files
committed
Updating error article
1 parent 3df6a00 commit 30654ca

File tree

1 file changed

+66
-16
lines changed

1 file changed

+66
-16
lines changed

articles/storage/common/storage-ref-azcopy-error-codes.md

Lines changed: 66 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -4,25 +4,75 @@ description: A list of error codes that can be returned by the Azure Blob Storag
44
author: normesta
55
ms.service: azure-storage
66
ms.topic: reference
7-
ms.date: 04/17/2024
7+
ms.date: 04/18/2024
88
ms.author: normesta
99
ms.subservice: storage-common-concepts
1010
---
1111

1212
# Error codes: AzCopy V10
1313

14-
The following errors can be returned by the Azure Blob Storage API when working with AzCopy. For a list of all common REST API error codes, see [Common REST API error codes](/rest/api/storageservices/common-rest-api-error-codes). For a list of Azure Blob Service error codes, see [Azure Blob Storage error codes](/rest/api/storageservices/blob-service-error-codes).
15-
16-
| HTTP status code | Error code | Message |
17-
| ---------- | ------- | ----- |
18-
| Bad Request (400) | InvalidOperation | Invalid operation against a blob snapshot. Snapshots are read-only. You can't modify them. If you want to modify a blob, you must use the base blob, not a snapshot.|
19-
| Bad Request (400) | MissingRequiredQueryParameter | A required query parameter was not specified for this request. |
20-
| Bad Request (400) | InvalidHeaderValue | The value provided for one of the HTTP headers was not in the correct format. |
21-
| Unauthorized (401) | InvalidAuthenticationInfo | Server failed to authenticate the request. Please refer to the information in the www-authenticate header. |
22-
| Unauthorized (401) | NoAuthenticationInformation | Server failed to authenticate the request. Please refer to the information in the www-authenticate header. |
23-
| Forbidden (403) | AuthenticationFailed | Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly including the signature.|
24-
| Forbidden (403) | AccountIsDisabled | The specified account is disabled. Your Azure subscription can get disabled because your credit has expired or if you reached your spending limit. It can also get disabled if you have an overdue bill, hit your credit card limit, or because the Account Administrator canceled the subscription. |
25-
| Not Found (404) | ResourceNotFound | The specified resource doesn't exist. |
26-
| Conflict (409) | ResourceTypeMismatch | The specified resource type doesn't match the type of the existing resource. |
27-
| Internal Server Error (500) | CannotVerifyCopySource | This error is returned when you try to copy a blob from a source that is not accessible. More information and possible workarounds can be found [here](/troubleshoot/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction#copy-blobs-between-storage-accounts-in-a-hub-spoke-architecture-using-private-endpoints). |
28-
| Service Unavailable (503) | ServerBusy | Error messages:<li>The server is currently unable to receive requests. Please retry your request.<li>Ingress is over the account limit.<li>Egress is over the account limit.<li>Operations per second is over the account limit.<li>You can use the Storage insights to monitor the account limits. See [Monitoring your storage service with Azure Monitor Storage insights](storage-insights-overview.md). |
14+
The following errors can be returned by the Azure Blob Storage API when working with AzCopy. The error codes are organized by HTTP status code. For a list of all common REST API error codes, see [Common REST API error codes](/rest/api/storageservices/common-rest-api-error-codes). For a list of Azure Blob Service error codes, see [Azure Blob Storage error codes](/rest/api/storageservices/blob-service-error-codes).
15+
16+
## Bad Request (400)
17+
18+
### InvalidOperation
19+
20+
Invalid operation against a blob snapshot. Snapshots are read-only. You can't modify them. If you want to modify a blob, you must use the base blob, not a snapshot.
21+
22+
### MissingRequiredQueryParameter
23+
24+
A required query parameter wasn't specified for this request.
25+
26+
### InvalidHeaderValue
27+
28+
The value provided for one of the HTTP headers wasn't in the correct format.
29+
30+
## Unauthorized (401)
31+
32+
### InvalidAuthenticationInfo
33+
34+
Server failed to authenticate the request. Refer to the information in the www-authenticate header.
35+
36+
### NoAuthenticationInformation
37+
38+
Server failed to authenticate the request. Refer to the information in the www-authenticate header.
39+
40+
## Forbidden (403)
41+
42+
### AuthenticationFailed
43+
44+
Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly including the signature.
45+
46+
### AccountIsDisabled
47+
48+
The specified account is disabled. Your Azure subscription can get disabled because your credit has expired or if you reached your spending limit. It can also get disabled if you have an overdue bill, hit your credit card limit, or because the Account Administrator canceled the subscription.
49+
50+
## Not Found (404)
51+
52+
### ResourceNotFound
53+
54+
The specified resource doesn't exist.
55+
56+
## Conflict (409)
57+
58+
### ResourceTypeMismatch
59+
60+
The specified resource type doesn't match the type of the existing resource.
61+
62+
## Internal Server Error (500)
63+
64+
### CannotVerifyCopySource
65+
66+
This error is returned when you try to copy a blob from a source that isn't accessible. More information and possible workarounds can be found [here](/troubleshoot/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction#copy-blobs-between-storage-accounts-in-a-hub-spoke-architecture-using-private-endpoints).
67+
68+
## Service Unavailable (503)
69+
70+
### ServerBusy
71+
72+
The server is currently unable to receive requests. Retry your request.
73+
74+
- Ingress is over the account limit.
75+
- Egress is over the account limit.
76+
- Operations per second is over the account limit.
77+
78+
You can use the Storage insights to monitor the account limits. See [Monitoring your storage service with Azure Monitor Storage insights](storage-insights-overview.md).

0 commit comments

Comments
 (0)