# "other DICOM listeners running" on startup

**URL:** <https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980>\
**Category:** Support\
**Tags:** dicombrowser\
**Created:** [December 5, 2018, 9:27pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980 "2018-12-05T21:27:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [December 5, 2018, 9:27pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/1 "2018-12-05T21:27:47Z")

</div>

I recently started seeing the message below every time on startup. I don’t start any listeners knowingly. Is this message expected?

![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/6/8/68ebd8a9f4458c3f70b1c3b195a0f574066dcb47.png)

---

<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:** [December 5, 2018, 9:45pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/2 "2018-12-05T21:45:25Z")

</div>

The error message means that the DICOM module detects running processes that have `storescp` in their name. Do you actually have such processes running?

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [December 5, 2018, 9:48pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/3 "2018-12-05T21:48:01Z")

</div>

No, not to my knowledge. I do not think I knowingly started any storescp processes. I guess I should investigate whether this is caused by any of the extensions first … Let me disable all extensions and see if I still get this popup.

---

<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:** [December 5, 2018, 10:03pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/4 "2018-12-05T22:03:42Z")

</div>

Storescp may be run by other applications with DICOM networking features, not just by Slicer. When Slicer reports that this process is found, run `ps -A` to confirm.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [December 5, 2018, 10:07pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/5 "2018-12-05T22:07:57Z")

</div>

Ah, good point! Indeed, I see it running with `ps`. But it is running from the Slicer application folder. And it is not stopped when I close Slicer. If I uninstall all extensions, it is still started when I start Slicer.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/f/bfe60f46a35d4a8c456ad361e8f5a489badcd343.png)

---

<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:** [December 5, 2018, 10:12pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/6 "2018-12-05T22:12:26Z")

</div>

I think this is a Slicer core feature. Check if “Start listener when Slicer starts” checkbox is enabled in the DICOM module (in the module panel).

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [December 5, 2018, 10:28pm UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/7 "2018-12-05T22:28:43Z")

</div>

Yes, indeed - it was checked. I don’t recall checking it though, and when it is checked, I would expect Slicer to shut it down on application exit. But in any case, the issue I had is resolved - no more automatic startup, and the popup is gone. Thank you!

---

<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:** [December 6, 2018, 1:36am UTC](https://discourse.slicer.org/t/other-dicom-listeners-running-on-startup/4980/8 "2018-12-06T01:36:42Z")

</div>

> [@fedorov](#):
>
> I would expect Slicer to shut it down on application exit.

Yes, it is supposed to, at least it used to.