Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi Community,
Would anyone be knowing the reason behind the failure. It worked fine last few months and recently started popping error m
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
HI @schoden,
Can you please share more detail information to help us clarify your scenario? It is hard to troubleshoot from the error message. (e.g. refresh history, error message with activity/request-id, data source type and connection mode, data source credentials type...)
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
@v-shex-msft Please see the message below: (the Dateset refresh icon shows failed error message)
Something went wrong The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support. Please try again later or contact support. If you contact support, please provide these details. Cluster URIWABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net Activity IDfb59f6a2-48f1-4618-8642-ddbb9ddb0c0f Request IDde963595-d9b7-c77b-8e95-f269f51c9592 Time2020-07-15 03:49:52Z Get help Copy
Hi @schoden ,
There is something critical missing in your error message.
Normally it looks like below so you would get a better idea about what went wrong.
If that's actually what you received, please provide more details.
e.g. data source type, gateway type, what's changed recently to your report. I guess the more info the better.
Regards
It would be clear if you can specifiy what source are you trying to refresh the data from!
Check these!!
Hi @Anonymous
Yes the refresh is working on Desktop.
Credentials has not been changed.
There can be more than 1 scenarios for an internal service error. In my case, re-publishing the report after downloading a latest version of the Power BI desktop resolved the issue.
If you have recently made changes to your report and published the report to the service, a chance of this error could be with your cachce. When you publish the report can you clear the cache and try to publish.
If issue persists, you can run a fiddler trace further to see where exactly the issue occurs..
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem-tshoot/#fiddler-trace
More details from your side like, the type of source you are using could help.
Hi @Anonymous
I recently republished the old report with updated version from the desktop.
Like you mentioned, I suspected the cache which I cleared it.
The datasource is SQL and it is connected via gateway.
Hi @schoden ,
Did you check the refresh history on Power BI service? It would reveal more details.
If this helps, please give me a kudo. Thanks a lot.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
34 | |
30 | |
18 | |
12 | |
8 |
User | Count |
---|---|
50 | |
35 | |
30 | |
15 | |
12 |