There was an error when processing the data in the dataset. The command has been canceled.

[byeo]

We have a dashboard that was working fine with scheduled data refreshes for few weeks but it now started failing when refreshing from PowerBI service. There is no issue refreshing from PowerBI desktop and the error is only when trying to refresh from PowerBI service. 

The data source is excel online in a Sharepoint. There is no calculated column involved and it is a very straightforward pointing to excel online to create some visualization in PowerBI.

The size of excel file is ~45 KB and pbix file is ~480 KB.

Any suggestions what might be the root cause for this error?

Thanks

[Anonymous]

As a simple test. Download the project out of the service, rename it and upload it again.  This will give you a newly published clone of your report.  Set up any gateways for this clone and attempt a refresh.

I had a report recently that had a similar issue and it seemed to be a corruption in the version on the Service.  Publishing over the top did not resolve the problem and I had to resort to removing it and republishing it.

[byeo]

 @Anonymous - Thanks for the suggestion. I tried but it is still throwing the same error

[Anonymous]

What happens if you refresh using the Power BI Desktop?  Do you get more information on the error?  With Excel, sometimes changes made to the file can be just enough to break your import logic.

[byeo]

When refresh from PowerBI Desktop, there is no error at all! I am able to see new data coming in from Excel and I am also able to publish to web successfully. Do you know where I can check out "log file"  in PowerBI Desktop? Maybe I can get some hint from there...

[boardstat_beta]

I more or less have the same issue with PowerBI service. 

PowerBI desktop and Excel can download the data with credentials, but PowerBI service times out because it can't refresh the credentials.

[Anonymous]

I would probably suggest raising a ticket for this problem specifically.  I have encountered strange things from time to time and its possible the problem is quick technical on the Power BI Service side.  Generally when I have encountered these, raising this through the "issues" section has helped resolve the problem.  Sometimes the problems are on Microsofts side of the fence, and its worth getting them to look at it directly.