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
Copy file name to clipboardExpand all lines: articles/planetary-computer/error-codes-ingestion.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ ms.date: 06/16/2025
12
12
13
13
# Error codes: Microsoft Planetary Computer Pro ingestion
14
14
15
-
This article lists the error codes that can occur when ingesting geospatial data into a Microsoft Planetary Computer Pro GeoCatalog. Use this reference to identify the cause of ingestion failures and find resolution steps for each error type.
15
+
This article lists the error codes that can occur when ingesting or deleting geospatial data from a Microsoft Planetary Computer Pro GeoCatalog. Use this reference to identify the cause of ingestion failures and find resolution steps for each error type.
16
16
17
-
Ingestion errors can occur during various stages of the data ingestion process, including authentication, validation, transformation, and storage operations. The following table provides detailed information about each error code, its meaning, and steps to resolve the issue.
17
+
Ingestion errors can occur during various stages of the data ingestion process, including authentication, validation, transformation, and storage operations (adding and deleting). The following table provides detailed information about each error code, its meaning, and steps to resolve the issue.
Copy file name to clipboardExpand all lines: articles/planetary-computer/troubleshooting-ingestion.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,11 +33,13 @@ Data ingestion workflows fail with specific [error codes](./error-codes-ingestio
33
33
34
34
For [Single Item Ingestion](./ingestion-overview.md#single-item-ingestion), if an ingestion error occurs, the API response or user interface returns the error code.
35
35
36
+
[](media/single-item-ingestion-error.png#lightbox)
37
+
36
38
For [Bulk Ingestion](./ingestion-overview.md#bulk-ingestion), the errors can be different for each of the individual STAC Items. To see the individual errors, navigate to the Azure portal and locate the **Diagnostic Settings** for your GeoCatalog resource. Here, you can enable **Ingestion Logs.**
37
39
38
40
[](media/ingestion-diagnostic-settings.png#lightbox)
39
41
40
-
Once logging is enabled, attempt your ingestion again. If the ingestion fails, go to the diagnostic endpoint you specified to review the errors.
42
+
Once logging is enabled, attempt your ingestion again. If the ingestion fails, go to the location you specified in diagnostic settings to review the errors.
41
43
42
44
## Cause 1: GeoCatalog can't access source data
43
45
@@ -52,12 +54,12 @@ The GeoCatalog service lacks the necessary permissions to read your STAC metadat
52
54
53
55
2.**Validate credentials**
54
56
55
-
For managed identity:
57
+
For [managed identity](./set-up-ingestion-credentials-managed-identity.md):
56
58
- Ensure the managed identity has the **Storage Blob Data Reader** role
57
59
- Verify the role assignment is at the correct scope (storage account or container level)
58
60
- Check that the managed identity is associated with your GeoCatalog
59
61
60
-
For SAS tokens:
62
+
For [SAS tokens](./set-up-ingestion-credentials-managed-identity.md):
61
63
- Verify the token isn't expired
62
64
- Ensure the token has `read` and `list` permissions
63
65
- Confirm the token is scoped to the correct container
0 commit comments