Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Error Message : "DM_GWPipeline_Gateway_MashupDataAccessError"

As the title says, I'm getting an error message on my published report. The server for the database is running fine, and I even rebooted, but still having this issue. Below is a breakdown of the full error I get when trying to refresh my data. This report has been working fine for a few months, and suddenly just stopped refreshing. I've also updated the gateway to the latest version.

 

Data source error:{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: incilog.

 

I'm able to refresh the report just fine on the Desktop application, but when attempting to do so through the workspace/dataset, I get the above error message. 

Any ideas as to what could be going on?

8 Replies

  • Hi there

    Have you updated the Gateway server to the latest version?

    The reason is Power BI Desktop gets updates to the Mashup Engine and the Gateway Server also needs to get the same version of the Mashup Engine?
    • Anonymous's avatar
      Anonymous
      Not applicable

      Yes, the gateway has been updated to the latest version.

  • Watsky's avatar
    Watsky
    Solution Sage

    Anonymous  is it just this report that's having this issue or all reports?

    • Anonymous's avatar
      Anonymous
      Not applicable

      All the reports on the Sharepoint Workspace have been affected.

  • jasonGBDS28's avatar
    jasonGBDS28
    Frequent Visitor

    Hi,
    Did you verify that the credentials are correct?
    What kind of connection ODBC, SQL Server, Excel?

    • Anonymous's avatar
      Anonymous
      Not applicable

      I did verify that the credentials are correct. The dataset is connected to a SQL Server.

    • Anonymous's avatar
      Anonymous
      Not applicable

      We don't currently have an Enterprise Gateway setup to my knowledge, so I don't believe this is the issue either. Thank you for the input though!