# HG changeset patch # User Sebastien Jodogne # Date 1671520955 -3600 # Node ID 25bbeb75442009e83b1076c46b94cba59a214235 # Parent 7f30e05a3319d74a9b717e0745243ef109aab420 note about shared network drives diff -r 7f30e05a3319 -r 25bbeb754420 Sphinx/source/faq/troubleshooting.rst --- a/Sphinx/source/faq/troubleshooting.rst Tue Dec 20 08:12:17 2022 +0100 +++ b/Sphinx/source/faq/troubleshooting.rst Tue Dec 20 08:22:35 2022 +0100 @@ -184,6 +184,20 @@ characters. Please try and run Orthanc in a folder with a simple name such as ``C:\Orthanc``. +* If you run Orthanc as a Windows service, and if you want to store + the Orthanc database (or the :ref:`Orthanc Web Viewer plugin + `) onto a shared network drive, you might encounter an + error ``boost::filesystem::status: The specified server cannot + perform the requested operation``. This probably means that the + ``SYSTEM`` account is not allowed to access the **mapped network + drive**. The easiest approach to this end consists in configuring + the Windows service to **run as user** (instead of the default + ``SYSTEM`` account), `as explained in this thread + `__ + on the Orthanc Users forum (cf. `additional reference + `__ + elsewhere on Internet). + * If **Orthanc crashes when handling one large DICOM file**, this most probably indicates a memory allocation error. Indeed, the `official Windows binaries @@ -199,9 +213,11 @@ * If you run Orthanc as a Windows service, with the Python plugin enabled, you might have to change your ``PATH`` environment variable - for Orthanc to find the Python DLL. The easiest approach to this end - consists in configuring the Windows service to **run as user** + for Orthanc to **find the Python DLL**. The easiest approach to this + end consists in configuring the Windows service to **run as user** (instead of the default ``SYSTEM`` account), `as explained in this thread `__ - on the Orthanc Users forum. + on the Orthanc Users forum (cf. `additional reference + `__ + elsewhere on Internet).