Scheduled Refresh Error - An Unexpected Exception occured

[Gopa]

Hi

I have a dataset which has 4 scheduled refreshes in a day. It has been working fine for many months now. From Yesterday night (Aug 31, 23:30 IST) refresh, it is throwing up en error. The Screen shot of the error from today morning is attached herewith. When the refresh error occured the first time at 23:30, I refreshed the desktop version without any errors and re-published to power BI service. But then the subsequent scheduled refreshes again throws up the same error. I cannot understand the issue, more so, as the manual refresh from Power BI desktop works fine. 

Regards

Gopa Kumar

[Seth_C_Bauer]

@Gopa There should be a more specific error if you look into the settings on the dataset. If not, go check the gateway logs to see a more specific error.

Go to the computer that has the gateway installed and search for the log file in this location:

C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log

The easiest way to find what you are looking for is either by searching for a datasource in the report or the time of failure.

[Gopa]

@Seth_C_Bauerthe dataset does not use the Gateway. It is a connection from OneDrive of Excel files. The issue is that when I refresh the same dataset in Power BI desktop, it refreshes properly, so I am unable to get any further info on the error. And moreover, the schedule refresh in power BI service had been working perfectly for many months now. 

[Seth_C_Bauer]

@Gopa Ok. If there are no additional pointers on the dataset, then I would validate that there was no change to the files, or an invalid value in a column. I would run back through each aspect of the PQ connection / transformation to ensure it still works appropriately. If you search the specific error, there are a myriad of different cases where something like this occurs because something in the underlying data or structure changed.

[Gopa]

@Seth_C_BauerI have refreshed individually all the queries in power query with no issues. The Power BI Desktop refreshes without any issue. The issue comes in the scheduled refresh from power BI service. 

I have another dataset which also throws up error. This also is a direct connection to OneDrive excel file and this also started day before. Till then it was working fine. In this case the message is:

'Message: The command has been canceled. Table: 2 GL Line item table.'

But in desktop again this table does not give any errors when refreshed in PQ. And again, in a subsequent schedule refresh in power BI service, the message will give a different table name. 

I am at a loss as to how to solve this issue.

[Seth_C_Bauer]

@Gopa What I am suggesting is that based on other issues I've read this situation can occur where the Desktop handles processing an "error", while the refresh process (Gateway- whether you have to set it up or not) fails. Hard to find, but there are enough use cases I've read that I wouldn't rule out a data/datatype issue.

[Gopa]

@Seth_C_BauerThank your for your suggestions. I am not able to solve this as I am unable to pinpoint the issue. In both the cases the structure of the excel files had not changed and in fact in the 2nd case, even the data had not changed since the last successful scheduled refresh.

I have raised a support ticket with Microsoft on this issue. They are looking into it. They have asked for some details, which I had provided. Let us see what comes out of it. In any case, I shall update this thread once they finish with their analysis.

[Gopa]

@Seth_C_Bauerjust an update to this issue...had a support call with Microsoft today. It seems the issue is with reports having custom visuals and dataset in OneDrive cloud. The issue might get resolved by Sep 12th Update.

The issue and the workaround as reported at https://powerbi.microsoft.com/en-us/support/

[Gopa · Accepted solution]

@Seth_C_BauerJust to update this issue. Finally, the issue was identified as a bug by the product team. The bug was rectified in the November Dektop update and also in the service. The issue has been resolved. 

Note: The issue was not what was reported earlier regarding the oneDrive cloud. It was a new bug in the internal calculation.