Forum Discussion
Advocate IIScheduled Refresh Error - An Unexpected Exception occured
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
AnonymousJust 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.
8 Replies
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
Anonymousthe 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.
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.
