cancel
Showing results for 
Search instead for 
Did you mean: 

Published Power BI report/dataset failing to refresh

Despite having no trouble refreshing a report when in Power BI Desktop, I am getting the following error with scheduled refreshes once the report is published:

ast refresh failed: Fri Nov 16 2018 09:08:55 GMT-0800 (Pacific Standard Time) 
The last refresh attempt failed because of an internal service error.
Hide details

Cluster URI:DF-MSIT-SCUS-redirect.analysis.windows.net
Activity ID:9d901569-5d35-417b-a53e-7d9ced7c7752
Request ID:63d9aa5a-39b0-48e5-b69a-f414c1388df7
Time:2018-11-16 17:08:55Z

 

The dataset is pulling from both AzureBlob & Web (Excel on a SharePoint using the Web connector). Different reports/datasets with the same sources and credentials are not having this issue.

 

Help?

Status: New
Comments
Moderator

Hi @WTarrasque,

 

Please download the pbix from Power BI service, open it in Power BI desktop, click on Refresh button, check if any error displays in report view or Query Editor. 

 

Best Regards,
Qiuyun Yu 

Visitor

Hi Qiuyun,

 

Power BI desktop has no issue refreshing the report. It is only in the Power BI service the refresh is failing.

 

I downloaded the PBIX and it could refresh in Power BI Desktop.

 

How can we diagnose the problem in the service?

Moderator

Hi @WTarrasque,

 

Please create a support ticket to get dedicated support. 

 

Support Ticket.gif

 

Best Regards,
Qiuyun Yu 

Visitor

Will do.

 

Separate problem that is very annoying. Every time I sign in on a page it redirects me somewhere else. I can't sign in on the page I'm on.

 

Is that an issue or a feature request?

Moderator

Hi @WTarrasque,

 

Do you mean the Sign in button on support ticket page? 

q5.PNG

 

As I tested, we needn't to click Sign In button. We just need to fill all required fields then click Submit Ticket. 

 

Best Regards,
Qiuyun Yu 

 

 

Visitor

Unfortunately I have exactly the same issue. Do we have a solution for this?

Visitor

Hi Maverick. The solution that worked for me was a workaround to republish the dataset & report with a different name, and then see if that refreshes.

 

It now works. I'm not sure why the first dataset won't refresh, but a different name (and therefore new dataset) does.