Cancellation occurred when sending or receiving a request.

Hi hugo6262,

Please try it again. If the error persist, I would suggest you file a support ticket here.

Best Regards,

Dale

Hello PowerBI Team,

We are facing the exact same issue. The production work is getting impacted in a big way. Request for a resolution ASAP. Thanks!

Same issue here.  I will enter a support ticket today. 

Same here and I cannot enter a ticket even though i am a pro trial user :(

Cancellation occurred when sending or receiving a request.
Please try again later or contact support. If you contact support, please provide these details.

Actually I am having the same issue trying to enter a ticket.  I am a pro user, but not an admin on my computer.  

Root issue still persists...

We are having the same issue on one report scheduled refresh... have raised a support ticket.

We were also having the same issue connecting to an Azure AD SQL db. The problem was with an identity column having duplictae values. 

We are also having the same issue. It impacts only one report. The Gateway is working fine for other reports.

I updated the Gateway to the latest version. The refresh won't work on demand or scheduled.

Hi,

I'm also facing the same issue for a specific dataset.

The dataset is refreshing successfully on desktop version.

I have updated the on promise gateway to the latest vrsion (14.16.6584.1) but the error message remains the same.

Looking at the gateway logs (C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log) I see some recurring error messages:

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_SpooledOperationMissing

Thank you all for the support.

Hi all,

I've faced the exact same problem (GatewayPipelineErrorCode=DM_GWPipeline_Gateway_SpooledOperationMissing)

for 2 days now and have only just solved the issue.

I removed all tables and added them back in one by one. The error changed to an OleAut date error in a certain table.

From this reference I found any date on or before 30/12/1899 (e.g. 11/12/1089) would cause an error. Replacing/removing these would cause the whole original report to work. In query editor, order your date field to find the problem dates.

As values can be introduced to your Dataset over time, replacing each one isn't a good solution. I've come up with the following M code which you can add to your query editor (Query Editor, View, Advanced Editor) to remove any dates which will cause this error:

#"Remove inappropriate dates" = Table.TransformColumns(#PREVIOUS_STEP_OR_NO#TABLE_NAME, {"COLUMN_TO_AFFECT", each if _ < #date(1900, 1, 1) then #date(1900, 1, 1) else _}),

real-life-example:

e.g. #"Remove inappropriate dates" = Table.TransformColumns(dbo_tblAccounts, {"DOB", each if _ < #date(1900, 1, 1) then #date(1900, 1, 1) else _}),

Remember to take off any filters/sorting you introduced whilst diagnosing your issue!

Hope this helps someone.

Simon C, UK, 01/Feb/2018