Forum Discussion

Msta's avatar
Msta
Helper I
5 years ago

Refresh failed: has failed to refresh NO error message

I have problem with my scheduling powerbi report. It's worked two days ago but now I get only this message( without error code):   My gateway version: 3000.54.8 (latest) Szczegóły Typ Uruchom Koni...
v-deddai1-msft's avatar
v-deddai1-msft
Community Support
5 years ago

Hi Msta ，

 

Would you please try to update your gateway to latest version? And you can also follow the document to troubleshoot your issue:

https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot

 

You can collect logs from the on-premises data gateway app to find detailed error message. In the on-premises data gateway app, select Diagnostics and then select the Export logs link, as shown in the following image:

 

 

And you can also  find the event logs for the on-premises data gateway service, or use Fiddler to troubleshoot your issue.

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards,

Dedmon Dai

 

  • Msta's avatar
    Msta
    Helper I
    5 years ago

    I have upgrade my gateway to latest version and problem still occurred. detailed error message didn't appeared in logs (on-premises data gateway app, Diagnostics)

    We find that the problems showup only with some of our reports (mix sql /SSAS + files), were  we use "Append Queries".  Our problems started 30th August, earlier everything was fine. We have problem also with "Merge Queries". The queries looks like:
    1step - import csv file
    2step - merge queries (SSAS source)
    3step - expand
    4step - merge queries (Another SSAS source)
    5step - expand

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      I'm having the same issues.  A dataset that utilizes the powerbi service for Dataflows has been failing since the November updates to the service.  The failure has no data and I have to looked into the server logs each time.  The error there is that the OATH authentication token failed to refresh.  This is a big problem.  Updating and rolling back the gateway did nothing to help this.