# HG changeset patch # User amazy # Date 1500528877 -7200 # Node ID e3be44c1d0418bf84889c5ab5698fbbda07bd696 # Parent 7063afe5748ce8bc3f214c49fc3fb51ad39e48a8 added startup troubleshooting diff -r 7063afe5748c -r e3be44c1d041 Sphinx/source/faq/troubleshooting.rst --- a/Sphinx/source/faq/troubleshooting.rst Wed Jul 19 12:49:56 2017 +0200 +++ b/Sphinx/source/faq/troubleshooting.rst Thu Jul 20 07:34:37 2017 +0200 @@ -13,6 +13,24 @@ of this page). Your issue might indeed have already been discussed in the past or in the FAQ. +Startup +------- +* If **Orthanc fails to start** with the error "**The TCP port of the DICOM + server is privileged or already in use**", this means another software is + already using the port Orthanc is trying to use. Usually, this means + that an other instance of Orthanc is running. However, note that, by default, + Orthanc uses port 4242 which might also be used by other software like + a `Juniper VPN client `__. + To determine which other process is using the port: + + On Windows, you may use the `Resource Monitor `__. + In the `Network` tab, check the `Listening Ports`. + + On Linux, you may use this command line: ``sudo ss --tcp --listen --numeric --processes``. + + Starting with version 1.3.0, the check at Orthanc startup is more robust + (it also checks for UDP socket using the same port) and Orthanc 1.3.0 might + display error messages that where not displayed by previous versions. Orthanc Explorer ---------------- @@ -103,4 +121,4 @@ less than 4GB of RAM. If this is an important limitation for you, precompiled command-line versions of Orthanc for Windows 64bit are available courtesy of `Osimis - `__. + `__. \ No newline at end of file