Forum Discussion

Pratshin's avatar
Pratshin
Regular Visitor
4 years ago

Dataset Refresh Error "DM_GWPipeline_Gateway_PipelineJsonDeserializationError"

Hi Team,

We are continously getting below error for Dataset refresh after start using power bi vnet data gateway. 
PS: this error is only for 2 dataset which has ~2GB datset size. please suggest for this issue.


Data source error: {"error":{"code":"DM_GWPipeline_Gateway_PipelineJsonDeserializationError","pbi.error":{"code":"DM_GWPipeline_Gateway_PipelineJsonDeserializationError","parameters":{},"details":[]}}} Table: Customers Risky Sessions Query.
Cluster URI: WABI-US-NORTH-CENTRAL-G-PRIMARY-redirect.analysis.windows.net
Activity ID: 95f7351c-be7d-4ab7-af0e-f51d6787ac62
Request ID: 29979b6f-b954-41d3-ae39-56cb0e4445bd
Time: 2022-02-25 06:56:43Z

5 Replies

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

    Hi  ,

    It would be great if you could provide more details about this issue.

    For example:

    1. I would like to know which data source are you connecting to? Is it Azure SQL?
    2. Based on the information you mentioned that the problem only occurs in 2Gb dataset, we would like to know if the refresh works when the dataset is >2GB or <2GB. Do you have enough memory for refreshing?
    3. Has your dataset been refreshed properly before? Or does this situation occur suddenly?
    4. Have you tried to create a new workspace to see if it refreshes properly?
    5. Can you provide a screenshot of the complete error message, as shown below.

     

    Best Regards,
    Jinwei Li
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Pratshin's avatar
    Pratshin
    Regular Visitor
    1. Yes It's Azure SQL
    2. Have error in 2 Dataset which have ~2GB size all other dataset are quit smaller than these 2 and also refreshing fine.We are at P1 Capacity and not sure if it's sufficient but before Vnet Data Gateway all dataset refresh was good.
    3. Yes Before we had public connection from PowerBI to SQL Database and refreshed successfull.
    4. No I would consider this option at last as this will change dataset ID which leads to break integration with application & some downtime.
    5. Refresh Error
    • Pratshin's avatar
      Pratshin
      Regular Visitor

      This issue resolved after increasing SQL timeout to 120m from reports settings. Thanks!

      • Zap5619's avatar
        Zap5619
        Regular Visitor

        Hi Pratshin 

        Where did you change this setting? Can you give a path of how to get to it?

         

        Thank you!