Orchestrator Job Faults for Document Understanding Digitisation - Could not find file path, access denied etc

Help Action Center
,
1

I am working on a solution for invoice DU extraction, classification, validation – eventually using the information to submit Invoice records into Dynamics. It works well and I’m coming to the end of the development, however I have one major sticking point.

Info:

  • The automation has 3 parts:
    • 1 - Email extraction, loading of queue items and document paths
    • 2 - Document Understanding extraction, classification and validation
    • 3 - Input into Dynamics

Issue:

  • Part 1 and 3 work fine from both studio and orchestrator job runs
  • However part 2 only works fine from studio runs – despite the publishing being smooth, it comes up with errors when run from orchestrator
  • The issue I receive is it cannot find document paths, either when the document is saved on the c drive Virtual Machine itself or the s drive. It can when run from my machine or the Virtual Machine on studio – but not through orchestrator
    • My testing and tweaks left me with a combination of these types of job fault errors at the digitise stage: Could not find a part of the path… / Input document not found… / Access to the path denied…
  • My suspicion is that the host identity type NT AUTHORITY\LOCAL SERVICE has some sort of issue with the permissions or access of files on the VM when run from orch

So far I’ve played around with dependencies, locations of the files, background run project settings – to no avail.

I am looking at the possibility of using storage buckets to upload and download to get around this, but perhaps you have knowledge on why I get this issue which will prevent some development and testing pain.

Do you have any insight as to why jobs ran from orch for DU processes with this server host identity would cause issues accessing shared file path and local file path documents locations in a Virtual machine. If so, do you have any advice that might mitigate this either from a development perspective or a VM permissions, server permissions perspective

Thanks

2

Hi @luke.deeney1 ,

  • Check and adjust permissions for the execution user context.
  • Consider using UiPath storage buckets to manage file paths.
  • Change the Robot’s execution context to a service account with appropriate permissions.
  • Use dynamic paths to adapt to different environments (Studio vs. Orchestrator).

By addressing these areas, you should be able to mitigate the access and permissions issues you’re encountering when running Document Understanding processes from Orchestrator.

Regards
Sandy

1 Like