Forum Discussion
Sporadic Gateway Error (Mashup error) Dataflow
I'm looking further into your suggestions and I keep investigating the issue, in the meantime, I noticed that I can set up a Power Automate flow to rerun the dataflow in case of failure, so I set this up, and it's working great.
I noticed that I can set up a Power Automate flow to rerun the dataflow in case of failure,That's not what you want to do. First understand the reason for the failure then decide if you need to fix that or if a retry is appropriate.
You just got lucky until now or didn't have the data volumes for the issue to manifest itself. We've been through that phase.
I see, I'm trying but I'm not able to understand the root cause.
I checked the gateway's logs but I can't understand a thing
Customer's system engineer told me we can't have a separate dedicated VM
I checked the windows log in the event viewer and I didn't find any warning about disk space. I found an error on the mashup engine, this is the message:
Application: Microsoft.Mashup.Container.NetFX45.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Could not find a part of the path 'C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Temp\Microsoft\MashupProvider\Cache\28edb145-f663-4146-82de-bd70a008e155\90ed647b-8a5f-4658-82d4-489a614c7aed.dat'.
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Microsoft.Mashup.Container.EvaluationContainerMain+ExceptionHandler.TryHandleException(System.Exception)
at Microsoft.Mashup.Evaluator.SafeThread2.HandleException(System.Exception)
at Microsoft.Mashup.Evaluator.SafeThread2+<>c__DisplayClass9_0.<CreateAction>b__0(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
ata System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)
Same, can't understand what this error is.I didn't find any log about network issue, I don't know how to track it.
So I don't know what else to do right nowCustomer's system engineer told me we can't have a separate dedicated VMDid they give a reason?
They said they have already implemented a large machine 100% dedicated to us (which is true), and there’s no need to modify it. The atmosphere may not be ideal, as it could seem like we are trying to shift the issue onto their side instead of resolving it.
In the previous weeks I've already asked to increase the disk size, also to grant us working days to optimize the infrastructure. Which I have done, but it is still not enough to avoid having dataflows fail occasionally. Anyway, this is more on the relational side of things. I wish I could understand what this bug is on the technical side.
AS you suggested a new machine could help probably, but I usually build this type of set up and I've never had any issue, never encountered this type of error, even with bigger flows.