Mercurial > hg > orthanc-book

changeset 903:25bbeb754420

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
note about shared network drives
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 20 Dec 2022 08:22:35 +0100
parents 7f30e05a3319
children a4a02709b188
files Sphinx/source/faq/troubleshooting.rst
diffstat 1 files changed, 19 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- 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
+  <webviewer>`) 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
+  <https://groups.google.com/g/orthanc-users/c/axrJfgA-Enk/m/Zeg3iUPOAwAJ>`__
+  on the Orthanc Users forum (cf. `additional reference
+  <https://docs.microfocus.com/SM/9.61/Hybrid/Content/serversetup/tasks/configure_the_service_manager_service_to_run_as_a_windows_user.htm>`__
+  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
   <https://groups.google.com/g/orthanc-users/c/axrJfgA-Enk/m/Zeg3iUPOAwAJ>`__
-  on the Orthanc Users forum.
+  on the Orthanc Users forum (cf. `additional reference
+  <https://docs.microfocus.com/SM/9.61/Hybrid/Content/serversetup/tasks/configure_the_service_manager_service_to_run_as_a_windows_user.htm>`__
+  elsewhere on Internet).