Anybody else get this message?

[Highboy]

We have had this error (Picture below) since version 2.15 (Now running 2.17)

We see this error every day on random scripts and random servers. (Running unattended)
I have a video (can't post due to gdpr) that captures what happens

The process does start and run for some time, and then just disappears with no trace in the logfiles, put it does produce the error below.
Funny enough the error tells us that it did not start, but it did (we watched it on the server).

We are working with Microsoft and have been doing so for more than a month, but so far no solution.

[Henrik_M]

Yep 😐

[yoko2020]

@Highboy 

Now i know what you mean.

I had this error before, maybe once in a month.

Running om PAD 2.14 Attended mode.

Check screenshot below for your reference.

[naridnevahgar]

We observed this error recently. While trying to do real time monitoring of a desktop flow (attended), until the flow completed execution, this error kept popping up. Once the flow completed, we were able to see the breakdown of the actions. 

[Kresimir_RPA]

Hi there,

I had this kind of error. We found out that the flow that was scheduled for running everyday didn't start because that desktop flow was created by external associate that had the newest PAD version at that time but the virtual machine that was trying to run that flow was on some older PAD version. When we updated to new PAD versions on machines the flow started working, and the logs showed up after it was finished.

So my conclusion is that if you updated to new PAD version, also make sure that you update PAD on your running virtual machines, because new flows created won't run on older versions unattended.

Regards, 

Kresimir

[yoko2020]

@Kresimir_RPA 

Flow will still start, but with different error message.

I don't think the error raised by @Highboy is related with this.

[Highboy]

We always run the same version on our developer and production machines.