Forum Discussion

opschain's avatar
opschain
Frequent Visitor
6 years ago

Mysql Database : Fatal Command Error for a few tables in the DB

I am trying to load data into Powerbi desktop that is present on a AWS VM . 
I am able to connect to the database and see a list of tables in the 'navigator' window that opens after the connection is made.

 When i check on certain tables , the table preview  load and the data load into the powerbi desktop is also successful. 

But in certain other tables (most of the tables) , the data does not load and it throws a fatal error. I have attached screenshot for both the cases . 

When I query the same table in the mysql workbench in the same VM, i get the required data without any errors.

Can someone help me with this.

 

3 Replies

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

    That's certainly odd, haven't seen it where it partially works. Anything particular about those tables that do not work? Are they all using some kind of data element that perhaps PBI doesn't like. What version of MySQL?

     

    You could check the Issues forum here:

    https://community.powerbi.com/t5/Issues/idb-p/Issues

    And if it is not there, then you could post it.

    If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

    • opschain's avatar
      opschain
      Frequent Visitor

       Greg_Deckler The same queries work perfectly when i try them on another VM thats hosted on azure , so its certianly not something specific to Powerbi, do you think it can be a case of access/security compliance issues that may vary in the way the two VMs have been setup ?

      I am not sure , because the same queries run perfectly when i run them on mysql workbench. the verison is 8.0

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

        Could be or maybe an old driver? That's really hard to troubleshoot virtually. It's almost a go through and check every setting, OS version, Power BI version, MySQL drivers, etc.