Power Automate Desktop Crash

(0) Share

Report

Posted on by yoko2020

495

We have a process which process 40000 rows of record and it can run almost 5 hours.

Previously no issue when running in ProcessRobot.

Below is the screenshot of the error.

1. Cloud Flow Log

Cloud Flow Log

3. Window Event Viewer Log

4.Window Event Viewer Log

5.Window Event Viewer Log

6.Window Event Viewer Log

Categories:

Power Automate Desktop

All responses (7)

Answers (0)

Sort by

geavgous Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi yoko2020,

It seems that you have a license. Could you open a ticket in the support site? Please include any correlation id from that issue so that we can have a look.

Thanks,
George
yoko2020 495 on at

Like
a
(0)

Report
Copy link

Link copied!

@geavgous
The error does not give any correlation id. Very strange.
Henrik_M 2,021 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@yoko2020 or @geavgous can you provide the information here, after you find out what's going on? Thanks!
yoko2020 495 on at

Like
a
(1)

Report
Copy link

Link copied!

@Henrik_M
As i remember, there is no clear explanation from power automate support what cause this issue.
For now i just hope with every PAD release update, this problem does not occur again.
geavgous Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi yoko2020,

It seems from the screenshots that the communication channel with the Runtime Robot fails. It could be an issue with named Pipes. Have you ever run this flow successfully in Power Automate? In addition, you don't need to have a correlation id. Once you open a ticket, you will be guided in collecting the logs and provide them to the support.
For a deeper look, creating a ticket is the best way to deal with this issue 🙂

Thanks,
George
yoko2020 495 on at

Like
a
(0)

Report
Copy link

Link copied!

@geavgous
Yes i did create the ticket.
And i remember they collect logs from the machines.
I never test again after that, its long run bot almost 5 hours, processing 40000 rows.
geavgous Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
Hi there,

To test if this has to do with Named Pipes, you could follow the steps below

To identify whether this is indeed the issue, you should follow the steps below:
Download the Sysinternals Suite ( https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite )
Extract the zip to a folder
Run a CMD as administrator
Navigate to the folder Sysinternals has been extracted to
Run the following command: handle net.pipe
Running this command should display a list of processes that use named pipes and the address they listen to, e.g.:
PAD.BrowserNativeMessageHost.exe pid: 21064 type: Section 464: \Sessions\1\BaseNamedObjects\net.pipe:EbmV0LnBpcGU6Ly8rL0JST1dTRVJOQVRJVkVIT1NULzE2NjIwLzEv
Microsoft.Management.Services.IntuneWindowsAgent.exe pid: 26708 type: Section 6AC: \BaseNamedObjects\net.pipe:EbmV0LnBpcGU6Ly8rL0lOVFVORU1BTkFHRU1FTlRFWFRFTlNJT04vU1RBVFVTU0VSVklDRS8=
PipesTest.Server.exe pid: 6540 type: Section 3AC: \BaseNamedObjects\net.pipe:EbmV0LnBpcGU6Ly8rLw==

You need to identify whether there is a process displaying the string highlighted in bold (EbmV0LnBpcGU6Ly8rLw==).

The reason for the error may be another process running a named pipes server in the same machine. This process runs most probably with elevated rights using the localhost endpoint which blocks other applications from using this endpoint as well.