# Can't open s certain dicom file

**URL:** <https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541>\
**Category:** Support\
**Created:** [May 19, 2023, 5:24pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541 "2023-05-19T17:24:36Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohammed\_alshakhas](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mohammed_alshakhas/32/10025_2.png) [@mohammed\_alshakhas](https://discourse.slicer.org/u/mohammed_alshakhas)\
**Post date:** [May 19, 2023, 5:24pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/1 "2023-05-19T17:24:36Z")

</div>

this is the second time it occurred , a dicom file get uploaded yet couldn’t open it . tried reload it again and again and just cant open

notice this error this time whenever opening slicer as well

b’E: cannot create network: 0006:031c TCP Initialization Error: Address already in use\n’

anyway to help with this ?

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 19, 2023, 5:45pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/2 "2023-05-19T17:45:55Z")

</div>

That indicates another program is using a network port. If you can’t find the program and kill it by hand probably just rebooting your computer is the easiest.

---

<div class="post-metadata">

**Author:** ![mohammed\_alshakhas](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mohammed_alshakhas/32/10025_2.png) [@mohammed\_alshakhas](https://discourse.slicer.org/u/mohammed_alshakhas)\
**Post date:** [May 19, 2023, 5:53pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/3 "2023-05-19T17:53:45Z")

</div>

i did reset to default and changed the database location and it worked.

another annoying thing was that that file I couldn’t open and couldn’t delete it.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 19, 2023, 5:56pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/4 "2023-05-19T17:56:15Z")

</div>

Hard to say. If you can replicate the issue with specific steps using public data then maybe someone can help you out.

---

<div class="post-metadata">

**Author:** ![mohammed\_alshakhas](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mohammed_alshakhas/32/10025_2.png) [@mohammed\_alshakhas](https://discourse.slicer.org/u/mohammed_alshakhas)\
**Post date:** [May 19, 2023, 6:47pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/5 "2023-05-19T18:47:03Z")

</div>

it is not a big deal , just wanted to know if there is obvious solution without having to reset the setting

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 21, 2023, 3:48am UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/6 "2023-05-21T03:48:57Z")

</div>

It seems that you run multiple Slicer executables at the same time, which use the same resources (network ports, database files, etc). This leads to inability to delete the database (the file is open in anther instance) inability to start another listening server on the same port (you can probably ignore this error, as the other instance receives any sent DICOM data), etc. The easiest way to resolve any potential problems is to run only one Slicer instance at a time.

---

<div class="post-metadata">

**Author:** ![mohammed\_alshakhas](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mohammed_alshakhas/32/10025_2.png) [@mohammed\_alshakhas](https://discourse.slicer.org/u/mohammed_alshakhas)\
**Post date:** [May 21, 2023, 3:26pm UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/7 "2023-05-21T15:26:58Z")

</div>

im not sure what do you mean by single slicer instance !

i tried to select my previous folder for Dicom data and the issue came back again.

two patient appeared and I couldn’t open or delete the data

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 22, 2023, 12:25am UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/8 "2023-05-22T00:25:59Z")

</div>

Do you get any error messages on screen?  
Do you see any error messages in the application log?  
In DICOM module / DICOM database settings, does “Remove unavailable data sets” remove the non-loadable patients?

---

<div class="post-metadata">

**Author:** ![mohammed\_alshakhas](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mohammed_alshakhas/32/10025_2.png) [@mohammed\_alshakhas](https://discourse.slicer.org/u/mohammed_alshakhas)\
**Post date:** [May 22, 2023, 10:31am UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/9 "2023-05-22T10:31:04Z")

</div>

i didn’t get any error on the screen, it only opens the empty file, and nothing loaded. no patient name or study name.

remove unavailable data set doesn’t change anything

 ![Screenshot 2023-05-22 at 13.39.42](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/b/db7aa2a255c9b3c6e40afa287a2559e297601e62.jpeg)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 23, 2023, 11:10am UTC](https://discourse.slicer.org/t/cant-open-s-certain-dicom-file/29541/10 "2023-05-23T11:10:40Z")

</div>

You get errors for farming to load jpeg images. Do you also have DICOM filter in that folder?

Also, the folder looks like some virtual network drive and its path is very long - both can be problematic.