Forum Discussion

jderekc's avatar
jderekc
Icon for Helper IV rankHelper IV
9 years ago
Solved

Power BI dataset refresh failing

Here we go again... most of my datasets fail on the refresh.  It again points to "WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net" as the details for the error.  I noticed it happening this weeke...
Need Help
  • Anonymous's avatar
    Anonymous
    9 years ago

    Hi jderekc,

     

    Based on your screenshot, I found the timeout error, it may related to your network or data volume.


    You can check your local gateway log or use fiddler to trace the operation logs.

     

    Reference link:

    Troubleshooting Power BI Gateway - Personal

     

    Fiddler Trace

    Fiddler is a free tool from Telerik that monitors HTTP traffic.  You can see the back and forth with the Power BI service from the client machine. This may show errors and other related information.

    Setup Logs

    If the Personal Gateway, fails to install, you will see a link to show the setup log. This could show you details about the failure. These are Windows Install logs, or also knows as MSI logs. They can be fairly complex and hard to read. Typically the resulting error will be at the bottom, but determining the cause of the error is not trivial. It could be a result of errors in a different log, or be a result of an error higher up in the log.

    Alternatively, you can go to your Temp folder (%temp%) and look for files that start with Power_BI_.

    Note:

    Going to %temp% may take you to a subfolder of temp.  The Power_BI_ files will be in the root of the temp directory.  You may need to go up a level or two.

     

     

    Regards,

    Xiaoxin Sheng
     

Anonymous's avatar
Anonymous
Not applicable
9 years ago

Hello,

 

We have end-users who are members with 'Members can edit Power BI content' permissions yet are experiencing this refresh error intermittently when trying to refresh when connected to the primary domain via VPN.

Could someone please advise recommended troubleshooting steps, i.e. Power BI or gateway logs, etc., that would help identify the root cause?  I have looked at the Fiddler and F12 traffic to no avail, but may not be looking for the correct log entry.

 

 

Thank you,

Ben