0

I have an excel Power Query report with a surprising bug. All of the mashup engine processes have no processor footprint, but exist. The only fix I have right now is to end these processes. The new mashup containers are created and the report continues to load. Why might these dead processes occur? I am not comfortable sharing the code of the problem query here.

Below is the task manager. Per the highlight, those four standing processes are at 0% before I ended them and new instances began.

Task Manager

Isaacnfairplay
  • 217
  • 2
  • 18
  • 1
    Try enabling Power Query tracing (Data -> Get Data -> Query Options -> Diagnostics -> Enable Tracing) and then inspecting the trace folder. Alternately, take your queries to Power BI and see if the same problems occur there (as PBI is the souped-up version of PQ and has more options for tuning query processing). – Jeroen Mostert Aug 11 '22 at 12:51
  • Using PQ in Power BI to inspect the trace, 80% of the time went to. RemoteDocumentEvaluator/Service/OnBeginGetResult , SimpleDocumentEvaluator/GetResult, RemotePreviewValueSource/RunStub, – Isaacnfairplay Aug 11 '22 at 16:53
  • Well, that unfortunately tells you nothing, but it was worth a try. I'm afraid that's as far as it goes without an MS dev hooking up a debugger to the thing and seeing what exactly it's waiting on. The other alternative, as I've said, is seeing what happens if PBI runs the same queries; if that does go through, comparing the traces might give some insight. Without the actual query I think this is as far as random people on the Internet can go. – Jeroen Mostert Aug 12 '22 at 05:53
  • I ran a version of the query in Power BI and it loads in 5 min, as opposed to the standard 30 in excel even with the dead process deleted in Task Manager. I used Power BI to refactor my query and ran it in Power Query in Excel and got the same result as before. The issue is specific to Excel. – Isaacnfairplay Aug 16 '22 at 18:19