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/healthcare-apis/dicom/deploy-dicom-services-in-azure-data-lake.md
+22-4Lines changed: 22 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -206,12 +206,30 @@ Use the Azure portal to **Deploy a custom template** and then use the sample ARM
206
206
207
207
1. When prompted, select the values for the workspace name, DICOM service name, region, storage account name, storage account SKU, and container name.
208
208
209
-
1. Select **Review + create** to deploy the DICOM service.
209
+
1. Select **Review + create** to deploy the DICOM service.
210
+
211
+
## Troubleshooting
212
+
213
+
### Connectivity
214
+
215
+
To be alerted to store health and connectivity failures, please sign up for [Resource Health alerts](/azure/service-health/resource-health-alert-monitor-guide).
216
+
217
+
### 424 Failed Dependency
218
+
219
+
When the response status code is `424 Failed Dependency`, the issue lies with a dependency configured with DICOM and it may be the data lake store.
220
+
The response body indicates which dependency failed and provides more context on the failure. For data lake storage account failures, an error code is provided which was received when attempting to interact with the store. For more information, see [Azure Blob Storage error codes](/rest/api/storageservices/blob-service-error-codes).
221
+
Note that a code of `ConditionNotMet` typically indicates the blob file has been moved, deleted or modified without using DICOM APIs. The best way to mitigate such a situation is to use the DICOM API to DELETE the instance to remove the index and then reupload the modified file. This will enable you to continue to reference and interact with the file through DICOM APIs.
210
222
211
223
## Next steps
224
+
[Receive resource health alerts](/azure/service-health/resource-health-alert-monitor-guide)
225
+
226
+
[Assign roles for the DICOM service](../configure-azure-rbac.md#assign-roles-for-the-dicom-service)
227
+
228
+
[Review DICOM service conformance statement](/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2)
229
+
230
+
[Use DICOMweb Standard APIs with DICOM services](dicomweb-standard-apis-with-dicom-services.md)
212
231
213
-
*[Assign roles for the DICOM service](../configure-azure-rbac.md#assign-roles-for-the-dicom-service)
214
-
*[Use DICOMweb Standard APIs with DICOM services](dicomweb-standard-apis-with-dicom-services.md)
215
232
*[Enable audit and diagnostic logging in the DICOM service](enable-diagnostic-logging.md)
0 commit comments