Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Export Failed - Paginated Report when using Netgear/ASUS Router

Hello,

 

I am having issues in my org a minority of users exporting paginated reports from our PBI products. The commonality is that they are using non-ISP routers, and are using Netgear/ASUS routers. The reports export fine when they tether with their mobile phones or switch back to ISP-routers. 

 

They have no difficulty accessing our dashboards, this is specifically affecting the export, not the generation of reports where they get the "Export Failed - Export failed, please try to export your report again."

 

Would anyone be able to advise a fix in the paginated reports so this does not happen?

 

Many thanks!

Need Help
  • Anonymous's avatar
    Anonymous
    4 years ago

    Hi Anonymous ,

     

    If the reports export fine with ISP-routers, this should not be an issue with Power BI. You might need to check the settings of the router.

     

    Best Regards,

    Jay

6 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Hi Anonymous ,

     

    If the reports export fine with ISP-routers, this should not be an issue with Power BI. You might need to check the settings of the router.

     

    Best Regards,

    Jay

    • JonathanDtz's avatar
      JonathanDtz
      Frequent Visitor
      3 years ago

      Hi Gazsam,

       

      Could you explain exactly what you had to change on the router? We are experiencing the same issue right now.

      Thanks!

    • segreral's avatar
      segreral
      Icon for Helper I rankHelper I
      3 years ago

      Hi Gazsam,

       

      Same here, could you please elaborate more the scenario, I have some users with same issue.

       

      I really appreciate all help you can provide us.

      • JonathanDtz's avatar
        JonathanDtz
        Frequent Visitor
        3 years ago

        Hi segreral,

         

        For what it's worth, we managed to solve it on our end. It turns out that the file exports trigger a different URL that our DNS was not resolving due to firewall policies. You might want to look into your DNS and Firewall rules. 

        Cheers!

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Following up from quite a long time ago, so apologies for delayed response, it did turn out to be an issue with the Router. There were fundamental issues with a netgear router which were only resolved using 3rd party software.