Unable to run unattended robot with the option Starts in background

Help Orchestrator
,
1

Hi,

I am unable to run unattended robot with the option Starts in background.

My scenario is - I am using “wait For Document Validation Action and resume” in my process. So I have to select the option “Starts in background” and working well from Studio…

When I publish the same, its giving error while starting process (using Bat file) saying Access is Denied.

I think I can not run without starts in background as using wait and resume task, but unable to run from orchestrator as unattended.

Can someone suggest the workaround please.

Thanks.

2

@krishbcd

I believe somewhere you are using environment.username for something and when run in background it would run as localntuser and not the actual user…so the access to some files or to run few thinga might be denied…and why is it that you need to only run in backgroundnmode?

If you still need then you need to give necessary permissions…from studio as already a user is there even background task runs as that user

Cheers

1 Like
3

@Anil_G

Here I am running the bot in VM as Background process (Running as Background process as I am using wait and resume activity for the action center approvals and proceed further). Its getting different resolution from the resolution i have setup in robot account.

image

image

Is it something I need to do with Local session manager as I am using a VM machine and as a Background process with user interaction (Here my background process access the bat files from shared (Network drive) and access the applications.)

image
image749×285 6.07 KB

4

@krishbcd

What do youmean by background process with ui access?

We call a process as background when there is no ui interaction at all

Cheers

5

@krishbcd,

Check this thread if it’s relatable.

Thanks,
Ashok :slight_smile:

6

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