Running PAD flow unattended fails to start Desktop flow.

[Slavnyy_Avtomat]

We have an Onboarding flow that's currently saved in 2.21.262.22194 that fails to start when ran on one of our unattended servers that had been upgraded to test 2.23.114.22217.  It gives the following error both when ran and when rerunning:

Encountered an unexpected error during Robot initialization: 'Microsoft.Flow.RPA.Desktop.Robin.Runtime.Agent.Exceptions.RobotInitializationException: Host process terminated with unknown exit code -532462766
   at Microsoft.Flow.RPA.Desktop.Robin.Runtime.Agent.Agent.CheckHostProcessExitCode()
   at Microsoft.Flow.RPA.Desktop.Robin.Runtime.Agent.Agent.LoadRobotImpl(RobotOptions options)
   at Microsoft.Flow.RPA.Desktop.Robin.Runtime.Agent.Agent.<>c__DisplayClass91_0.<LoadRobotAsync>b__0()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.Flow.RPA.Agent.Server.Components.ScriptEngines.RobinEngine.RobinEngine.<Execute>d__20.MoveNext()'.

Are there any known issues with 2.23 as yet?

[Bruiser]

@NikosMoutzou, @John_Mavridis , FYI.

[Slavnyy_Avtomat]

Now the same flow is failing to run on locally installed 2.23 -- I understand that things may break, but having more information than this for troubleshooting would be immensely helpful.  We're rapidly approaching v2.14 levels of irritation.  E: Flow designer and all PAD services have been restarted.

Correlation Id: 3190d78d-7684-4044-8bad-fd6a9b4f4882

[Waylold]

We are seeing the same thing. 

@NikosMoutzou, @John_Mavridis , is there any feedback on this?

[KaranSomnathe]

Points to check if unattended flows getting into error.

1. Make sure you have PA unattended license

2. Make sure machine configuration is done correctly. (Machine Settings)

3. Make sure the machine is logged off while running the flow.

4. Make sure that machine is set active by admin to be able to log in unattended.

5. Make sure to have the latest version of PA desktop installed in the system.

6. Best practice is to run the flow attended in same machine before running unattended.

[Slavnyy_Avtomat]

We have a premium license and have ~30 flows that run regularly without issue.  This appears to only be occurring within one flow that can now not even be ran attended.  I'm going to dedicate some time today to rebuilding the flow to see if we can find some sort of trigger.

[Waylold]

Hi @KaranSomnathe,

This is an existing flow that was running successfully on 2.21, along with the dozens of other unattended flows we have. 

The desktop flow receiving the error only started having the error after the VM running the machine runtime was upgraded to 2.23. No other configuration has changed outside of the version change. This is the only flow out of the aforementioned flows having an issue, so it appears to me to be a bug in the 2.23.114 version. 

[Slavnyy_Avtomat]

I wanted to do more in depth troubleshooting, so I rebuilt the flow that failed to run in attended and unattended modes.

I'd created a blank template and pasted the subflows over, testing as I added them.  Rebuilding the flow using the steps pasted from the broken flow has resulted in a success.  It can now run attended and unattended.

If I had to guess as to a root cause, I'd say that it's something in the translation from 2.16 > 2.18 > 2.21 > 2.23

Regardless, issue appears to be resolved.

[Waylold]

@Slavnyy_Avtomat , great stuff. I'm going to try that as well. 

[AGK02_Ganesh]

Thank you @Slavnyy_Avtomat 

Similar issue i am also facing. but your resolution not work for me.

I tried with below step:

1.Copy the all steps from broken RPA.

2.Create a new RPA and pasted the steps from old one.

Can you please help me more specific. 

Thank you