Forum Discussion
Gateway Pipeline Error [GatewayPipelineErrorCode]=DM_GWPipeline_Gateway_CanceledError
- 5 years ago
Hi collinq,
In any case, much appreciated that you spent time looking into the issue!!
I have learned that the problem usually occur when the dataflow needs to reload a full transactional dataset (e.g. added a column or other) or if a new large transactional dataset is added to the dataflow.
Leads me to think that it puts an extra initial load to the server, mashup-wise, which it fails early, looking through documentation and community i concluded the following.
I did two things at the same time;
- Upgraded server running gateway from 2 CPU to 8 temporary for the first succesful load
- Changed setting of MashupDSRTestConnectionTimeout from 50sec to 2min30sec in Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
Following night the scheduled refresh went through with success, 4 hours for the largest one.
The night after the largest took 20 minutes, and been stable at that since - incremental refresh kicked in.
If the solution was 1 or 2, or if I was just "luck" that night, I don't know, and can't reproduce the error now.
In any case, next time, I'll take your lead on enabling advanced log, maybe it will provide better insight.
Thanks anyways.
Hi LasseMr ,
I spetn a good chunk of time trying to see if I could find anything helpful. I really couldn't find anything identical and I circled back to one of the early documents I found - Troubleshoot gateways - Power BI | Microsoft Docs
This talks about looking at the logs, using trace and such but it does suggest opening a ticket. As does this document Troubleshoot the on-premises data gateway | Microsoft Docs
Please let us know the resolution you discover because I am fully intrigued but don't have a great solution other than those two "generic" articles.
- LasseMr5 years agoAdvocate II
Hi collinq,
In any case, much appreciated that you spent time looking into the issue!!
I have learned that the problem usually occur when the dataflow needs to reload a full transactional dataset (e.g. added a column or other) or if a new large transactional dataset is added to the dataflow.
Leads me to think that it puts an extra initial load to the server, mashup-wise, which it fails early, looking through documentation and community i concluded the following.
I did two things at the same time;
- Upgraded server running gateway from 2 CPU to 8 temporary for the first succesful load
- Changed setting of MashupDSRTestConnectionTimeout from 50sec to 2min30sec in Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
Following night the scheduled refresh went through with success, 4 hours for the largest one.
The night after the largest took 20 minutes, and been stable at that since - incremental refresh kicked in.
If the solution was 1 or 2, or if I was just "luck" that night, I don't know, and can't reproduce the error now.
In any case, next time, I'll take your lead on enabling advanced log, maybe it will provide better insight.
Thanks anyways.