Skip to main content

When RoboServer is installed as a Windows Service, robots may fail on steps configured to use mapped network drives

Article # 301573 - Page views: 824



The issue is likely related to how network drive letters are handled by a process running as a Windows Service.

Please refer to the following Microsoft MSDN support forum topic: us/library/windows/desktop/ms685143(v=vs.85).aspx

Services and Redirected Drives:

  • A service (or any process running in a different security context) that must access a remote resource should use the Universal Naming Convention (UNC) name to access the resource.
  • The service must have appropriate privileges to access the resource. If a server-side service uses an RPC connection, delegation must be enabled on the remote server.
  • Drive letters are not global to the system.
  • Each logon session receives its own set of drive letters from A to Z. Therefore, redirected drives cannot be shared between processes running under different user accounts.
  • Moreover, a service (or any process running within its own logon session) cannot access the drive letters that were established within a different logon session.
  • A service should not directly access local or network resources through mapped drive letters, nor should it call the NET USE command to map drive letters at run time.

Keywords: Kapow, Robotic Process Automation, Kapow 8.0, 8.1, 8.2, Kapow 8.3.x, Kapow 9.0.x, Kapow 9.1.x, Kapow 9.2.x, Kapow Enterprise 9.3.x, Windows service, mapped drive,