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
We are running docker.io/dcm4che/dcm4chee-arc-psql:5.31.0-secure with podman on redhat8. The DICOMs are correct in storage and can be downloaded separately but when download the series I got error of:
WARN [org.dcm4chee.arc.wado.WadoRS] (default task-67) Response Internal Server Error caused by java.util.zip.ZipException: duplicate entry: DICOM/EA6C7868/1431DE4C/4A3715EB.dcm
What I tried:
I backed up the 2 DICOMs in storage which were EA6C7868/1431DE4C/4A3715EB and EA6C7868/1431DE4C/CF6557BA They were sent from MRI scanners at beginning.
I deleted the series from GUI and wait until the files in storage are also been deleted.
Resent CF6557BA and got file as 4A3715EB in storage. Then resent 4A3715EB and got a random name.
Download the series from GUI and got the above error.
The storage path format is: {now,date,yyyy/MM/dd}/{0020000D,hash}/{0020000E,hash}/{00080018,hash}
The 2 DICOM has different sop_iuid.
Already Exists on Storage Path is configured as RANDOM_PATH
I also checked the database the filenames are correct there:
storage_path
We are running docker.io/dcm4che/dcm4chee-arc-psql:5.31.0-secure with podman on redhat8. The DICOMs are correct in storage and can be downloaded separately but when download the series I got error of:
WARN [org.dcm4chee.arc.wado.WadoRS] (default task-67) Response Internal Server Error caused by java.util.zip.ZipException: duplicate entry: DICOM/EA6C7868/1431DE4C/4A3715EB.dcm
What I tried:
The storage path format is: {now,date,yyyy/MM/dd}/{0020000D,hash}/{0020000E,hash}/{00080018,hash}
The 2 DICOM has different sop_iuid.
Already Exists on Storage Path is configured as RANDOM_PATH
I also checked the database the filenames are correct there:
storage_path
2024/07/26/EA6C7868/1431DE4C/4A3715EB
2024/07/26/EA6C7868/1431DE4C/C67B5BF6
Do you know what might be the problem? This happened with a few of our series.
Thanks
Yuqian
The text was updated successfully, but these errors were encountered: