Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

Error when refreshing in services

Hi, I found a strange bug when refreshing data in pwbi services.

It's always show the error message in below:

 

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

 

Then, I check my gateway, it shows the message that there is the latest version of apps. After I update to the latest version, I can now refresh normally in the services.

This is the 4th time I met these bugs. And I always just need to update the gateway, then everything will come back to normal.

 

Just wondering, why it happened?

 

 Please help me gain knowledge in this case.

  • Hi , Anonymous 

    As mentioned in the doucument :

    It's a good general practice to make sure you're using a supported version. We release a new update of the on-premises data gateway every month. Currently, Microsoft actively supports only the last six releases of the on-premises data gateway. If you're experiencing issues with the version you're using, try upgrading to the latest one as your issue may have been resolved in the latest version.

    Best Regards,
    Community Support Team _ Eason

2 Replies

  • v-easonf-msft's avatar
    v-easonf-msft
    Community Support

    Hi , Anonymous 

    As mentioned in the doucument :

    It's a good general practice to make sure you're using a supported version. We release a new update of the on-premises data gateway every month. Currently, Microsoft actively supports only the last six releases of the on-premises data gateway. If you're experiencing issues with the version you're using, try upgrading to the latest one as your issue may have been resolved in the latest version.

    Best Regards,
    Community Support Team _ Eason

  • Greg_Deckler's avatar
    Greg_Deckler
    Community Champion

    So, 4 times, in how long? Could be that the changes being made to the Service get to a point where an older gateway simply doesn't work with the Service any longer?