Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Refresh failed due to gateway configuration issues.

HI ALL
I am failing to refresh a report with the following error:

 

 

 

 

 

 

 

 

 

 

 

 

Refresh failed due to gateway configuration issues.
This dataset requires a properly configured gateway in order to refresh.If you're using personal mode, please make sure your gateway is online.If you're using enterprise mode, please make sure you've added the following data sources in the Gateway Management PortalMySql { server : "localhost" , database : "DB" } 
Please try again later or contact support. 
If you contact support, please provide these details. Activity ID: 67750544-d437-4c6a-9d5a-ed51d0efaede Request ID: 1b0a07e8-af32-3cb8-4b6d-571c7a56621a Correlation ID: 3c2ac6e9-96de-9495-e51a-512a8854e86c Time: Wed Jan 16 2019 14:51:02 GMT+1100 (AUS Eastern Daylight Time) Version: 13.0.7840.233 Cluster URI: https://wabi-australia-southeast-redirect.analysis.windows.net

 

I am using the same gateway and cluster with another report and it works fine.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

What am I missing?
How this should be fixed?

Cheers!

  • Anonymous's avatar
    Anonymous
    7 years ago

    Update

    The bottom line, Power BI is a buggy tool.

    As mentioned in the previous post, removing the JOIN clause from the query solved the original issue.

     

    I found other issues on the way. For example re-publishing a report will not reflect all changes. The workaround will be to delete the dataset from Power BI service and re-publish a fresh copy (not overwrite).

     

    Hope someone will find this post helpful.

     

    Cheers!

    A

     

6 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Update

    The bottom line, Power BI is a buggy tool.

    As mentioned in the previous post, removing the JOIN clause from the query solved the original issue.

     

    I found other issues on the way. For example re-publishing a report will not reflect all changes. The workaround will be to delete the dataset from Power BI service and re-publish a fresh copy (not overwrite).

     

    Hope someone will find this post helpful.

     

    Cheers!

    A

     

  • Anonymous's avatar
    Anonymous
    Not applicable

    HI ALL,

    These are my findings so far.

    I simplified my query in the SQL statement.

    At first, my query contained a JOIN between 3 tables. 

    i.e.

    select * from A INNER JOIN B INNER JOIN C
    ON A.id = B.id and A.id = C.id

     

    Now I have changed it to a simple query.

    select * from A.

     

    After the change the refresh works as expected.

     

    The question is about the JOIN caluse. Isn't it allowed? It is NOT supported?

    The work around will be, I believe, to upload each table in a seperate query and join them in the Power BI relationship module.

    Need to test if this works, though.

     

    Thanks!

    • Alex_Ooi's avatar
      Alex_Ooi
      Icon for Helper IV rankHelper IV

      No way! This is too much of a hassle! I'd rather refresh it manually from my desktop and hit publish every time after that then. Thanks for informing.

  • Anonymous's avatar
    Anonymous
    Not applicable

    OK,
    I got rid of the first error. I added the port number to the connection string.

    Now I have these errors:


     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    Any idea?
    Credentials are fine and I am able to see the data pulled from the DB.
    MySQL DB with localhost connection.

     

    Cheers!

    • v-yulgu-msft's avatar
      v-yulgu-msft
      Icon for Microsoft Employee rankMicrosoft Employee

      Hi Anonymous,

       

      Apart from MySQL Database, is any other type of data source contained in current dataset? If so, you also need to add that data source to Data Gateway.

       

      Regards,

      Yuliana Gu

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi v-yulgu-msft

        No other data source in this specific dataset.

        I do have other data set(s) that use the same gateway and same MySQL DB, and there are no issues there.

        Thanks
        A