Forum Discussion

Aker's avatar
Aker
New Member
6 years ago

Error 400 when uploading PBIX report connected to MySQL dataset

Hi,

 

I am enountering a problem when trying to share a PBIX report based on a MySQL dataset. The MySQL server is located on my own server, and I can access it without problem from Power BI Desktop (latest update, June 2020).

 

When trying to publish the report, I am encountering an error 400 without more information.

 

I tried to perform the upload the other way around, logging in to the online Power BI and uploading my local PBIX to my workspace. With the exact same result (error 400).

 

The online Power BI provides me the following reference to identify the issue:

 

We couldn't import data from Power BI Desktop File
Make sure you're entering the information correctly.
Please try again later or contact support. If you contact support, please provide these details.
Activity ID: de21985c-2332-4c9c-af63-7ec7a0d137f2
Request ID: 012b75a1-593b-1b65-e527-f5e291e3b5d8
Correlation ID: df706094-d754-70c8-1c32-11847a72c3cc
Status code: 400
Time: Thu Jun 11 2020 15:56:01 GMT-0400 (Eastern Daylight Time)
Service version: 13.0.13524.230
Client version: 2006.1.01422-train
Cluster URI: https://wabi-us-east2-b-primary-redirect.analysis.windows.net/

 

Since it is (apparently) not possible to create a MySQL dataset directly from the online Power BI tools, we are blocked since it is impossible for us to share new reports based on our MySQL data.

 

Thank you

7 Replies

  • aj1973's avatar
    aj1973
    Icon for Community Champion rankCommunity Champion

    Aker 

     

    You need to install either on premises or a personal Power Bi Gateway.

      • Aker's avatar
        Aker
        New Member

        Thank you aj1973 for your prompt response.

         

        The problem is not to access MySQL from my report. I can already access it and create a report out of it. The issue comes when I try to upload my report to my workspace, this is where I get the error 400 from the Power BI service.

         

        This may actually not even be related to MySQL. But my test report is so basic - it is just a single line chart - that MySQL is the only "exotic" feature being used which may cause the Error 400.

         

        I have a configured gateway, I just enabled it and runnning doesn't fix the issue. Morover, as far as I understand, a gateway is used for periodic refreshes of the data and should not be required for uploading a report.

    • Syndicate_Admin's avatar
      Syndicate_Admin
      Icon for Administrator rankAdministrator

      Someone has been able to fix this problem of connecting from power bi server to MySQL since I have the same problem

      I hope you can help me

      Best regards.

  • v-easonf-msft's avatar
    v-easonf-msft
    Icon for Community Support rankCommunity Support

    Hi , Aker 

    The issue occurs only for one specific report when you republish report from desktop to Power BI service, right?

    Have you tried to  rename  the pbix file  or using "Save as"  option to create  a new file  and publish it as a new dataset ?

    You may check if the follow thread helps.

    Error-400-Bad-Request-when-publishing-a-PBIX-file

    Power-BI-Publishing-not-working

    If the problem is still unsolved  ,on the forum side, it's hard for us to provide any more support about this issue. I would suggest you open a support ticket to get dedicated support from the Microsoft personally.

     

    Best Regards,
    Community Support Team _ Eason

  • v-easonf-msft's avatar
    v-easonf-msft
    Icon for Community Support rankCommunity Support

    Hi , Aker 

    Could you please tell me whether your problem has been solved?
    If it is,  please mark the helpful replies or add your reply as Answered to close this thread.
    More people will learn new things here. If you haven't, please feel free to ask.

    Best Regards,
    Community Support Team _ Eason
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.