Automatic Background Process running on VM it shouldn't have access to

Help Orchestrator
, , ,
1

I have an unattended background process running on one of our Virtual Machines that is configured to start automatically when the robot agent starts on the machine. This is only intended to run on one specific VM (“RPA2”). The folder containing this process only has access to the machine I want it to run on:
image

I do not have a trigger configured for this process since it is set up to start with the robot service.

I am constantly getting faulted job notifications for this process attempting to run on a different VM it shouldn’t have access to (“RPA1”). There also seems to be no rhyme or reason to when it attempts to start this job on the wrong machine. Sometimes it’s every hour - but as you can see below, sometimes it’s every 5 minutes:

image
image1459×645 88.8 KB

I’ve tinkered with every setting I can think of with no luck so far. I really have no idea how “RPA1” is even aware of this process or why it is continually attempting to run it at random. We have a KPI for successful vs Faulted jobs and, because of it’s behavior, this process is at 4% even though it is running correctly where it should.

EDIT: I forgot to note that this process does not have access to the Robot account (or credentials) for the RPA1 machine.

Thank you in advance for any advice!

Sidenote: This process is working correctly for the machine I want it to run on.

2

Looks like the source is “Assistant”? Could it be someone on the RPA1 trying to start it manually?

3

Unfortunately, that’s not it. I’m the only one with access to that machine. My theory is that it says “Assistant” because the robot service runs alongside assistant and it’s set up to start with that service. It says the same thing for RPA2 where it runs correctly.

4

this is an interesting one. What about audit logs of the Orchestrator, or event logs of the machine? anything there?
I also had some weird issues when cloning VMs, but usually it affects the second machine, not the original one.

5

Nothing at all for this process in the audit logs, except when I was testing it on my development machine.

Not seeing anything of note in the machine’s logs either. I did find the entry below around the time it last tried to run the job, but I’m not sure if it’s relevant. It may be related to this job, but doesn’t appear to clarify why it’s attempting to run it in the first place

UiPath.Service.Host 22.10.5.0
DoSasActionInternal:SASWrapper.cpp@28: SAS SAS::SessionActiveAndLocked ERROR 2
WTSQuerySessionInformation returned connection state : 2
WTSQuerySessionInformation returned connection state : 2
[SASLibEx] The given session ID 169 is not connected.

6

Also, I forgot to note that this process does not have access to the Robot account (or credentials) for the RPA1 machine.

I’ve added this detail to the original post as well.