Bot error in unattended mode

Help Orchestrator
,
1

Hi team

Need your expertise. I have developed a process which is downloading the file from Network Shared drive. Process is running fine in Development environment and attended mode. I have deployed the bot to orchestrator and getting access error to shared drive while executing in unattended mode. However, bot user is having access to Shared drive.

As far as, I could understand, unattended bot is running in service mode.

Attached, the error screen for your reference. Please help me to resolve this issue.

The image displays a detailed log entry showing an error message related to a system exception where access to a specific file path is denied. (Captioned by AI)
The image displays a detailed log entry showing an error message related to a system exception where access to a specific file path is denied. (Captioned by AI)949×802 76.6 KB

2

Did you set the process as a background process? If so it won’t log into the session and then won’t have access to the Network drive.

3

Are you trying to access a mapped network path??

If yes - please try full path and let me know if that resolved your problem

4

@Naresh_Upadhyay

  1. Try opening the file manually from that machine. If fails to open then give access to machine user to read and write access
5

@Naresh_Upadhyay

also I can see WindowsIdentity is NT AUTHORITY\LOCAL SERVICE. Ensure the machine template or unattended robot is configured with a domain account(e.g., domain\robotuser)

6

@Darshan_Sable

Thanks for replying on this thread. I am able to open the network path manually and robot is configured with domain account.

I tried to map the network path as Z drive and run the process which is running fine in Dev environment/Attended mode.
Tried to execute the process in Robot machine in unattended mode, Package is not being installed in robot machine and got the following error.

[Process ‘EDI 846 Summary Notification’ is not installed. Use the UiPath Diagnostic Tool to collect usage data so our support team can troubleshoot the issue]

Regards
Naresh

7

You should not use mapped drives. You can’t be sure they’ll always be there. Always use full UNC.

If you can log into the server as the robot account and access the file, but it fails when running unattended, then something is wrong with how you have Robot installed/configured.

8

Hi @postwick

Process checks if drive is mapped or not. it maps the drive before downloading the file.

Kindly suggest what troubleshooting I should do at robot side.

Thanks
Naresh

9

You shouldn’t be doing that stuff with mapping etc. Asking for problems. Just use the UNC (full path).

I would reinstall robot and make sure it’s set as service mode.

10

Hi @Naresh_Upadhyay

I would agree to what @postwick said about not mapping drives, its a good practice to use fully qualified names.

mapped drive identifier also can be different in different machines. if in your laptop, it is mapped under Z: but if that is not available on another machine, it wont get mapped to Z:

I understand that you are checking for if drive is mapped or not and then map it.

In my view, better approach would be to leave the mapping part out and simply navigate to the full path.

Hope that helps.

11

Thanks everyone for helping me on this. This has been resolved after disabling the background process in UiPath Studio for process.

“Unattended robots handle* background *processes in Session 0, under NT AUTHORITY\LOCAL SERVICE, which has no UI and cannot interact with a user session”.

  1. Open the project in UiPath Studio and follow the instructions in the attached documentation to confirm and disable background execution: [Background Vs Foreground Processes]
  2. Publish a new version of the project to Orchestrator to ensure the changes take effect. Then, run the job in unattended mode.
12

Yup,

I was saying that in my first reply at the start of this thread. Glad you got this resolved but you can still make background processes able to access network resources, you can change some environment variables on the machine to change the behaviour so that it still doesnt need to log on (so its faster) but can access the network resources as it still works with the robot account instead of a session 0 system account.

2 Likes
Forum Engagement Daily Reports
13

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.