Skip to content

Commit 399729c

Browse files
committed
2 parents 128ab51 + 6893f4c commit 399729c

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure-data-lake.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -217,14 +217,19 @@ To be alerted to store health and connectivity failures, please sign up for [Res
217217
### 424 Failed Dependency
218218

219219
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 will indicate which dependency failed and provide more context on the failure. For data lake storage account failures, an error code will be provided which was received when attempting to interact with the store. For further information on what these errors may mean, please refer to [Azure Blob Storage error codes](https://learn.microsoft.com/en-us/rest/api/storageservices/blob-service-error-codes).
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](https://learn.microsoft.com/rest/api/storageservices/blob-service-error-codes).
221221
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.
222222

223223
## Next steps
224-
* [Receive Resource Health alerts](https://learn.microsoft.com/en-us/azure/service-health/resource-health-alert-monitor-guide)
225-
* [Assign roles for the DICOM service](../configure-azure-rbac.md#assign-roles-for-the-dicom-service)
226-
* [Review DICOM service conformance statement](https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2)
227-
* [Use DICOMweb Standard APIs with DICOM services](dicomweb-standard-apis-with-dicom-services.md)
224+
[Receive resource health alerts](https://learn.microsoft.com/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](https://learn.microsoft.com/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)
231+
228232
* [Enable audit and diagnostic logging in the DICOM service](enable-diagnostic-logging.md)
229233

234+
230235
[!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]

0 commit comments

Comments
 (0)