Forum Discussion

chrisgill's avatar
chrisgill
Frequent Visitor
1 year ago

Data Gateway Recurring Error

We have an on-premises data gateway we have used for several years. We've occasionally experienced refresh errors, but they generally have been transient and intermittent. Recently, we upgraded our servers to Windows 22 and migrated the gateway to new servers (we have two servers in a gateway cluster). Since that migration we have received the following error regularly (almost, but not quite, daily). The semantic model that fails is a large model running in a Power BI Premium workspace.

 

Refresh failed:

Model - Enrollment has failed to refresh.
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

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

 

Any thoughts on how to address the error? Thanks in advance for any help you can provide.

 

Chris Gill

Need Help

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    I would create a support ticket with Microsoft:

    "This is usually a transient issue. If you try again later and still see this message, contact support."

  • SaiTejaTalasila's avatar
    SaiTejaTalasila
    Super User
    1 year ago

    Hi chrisgill ,

     

    You can try to load the data to multiple dataflows complete possible transformations and you can try to bring that data to your reports.Even it helps you reduce some load on your semantic model.

     

    I hope it will be helpful.

     

    Thanks,

    Sai Teja 

  • BIBB's avatar
    BIBB
    Advocate I
    1 year ago

    Hi chrisgill , I wonder if/how were you able to fix this. I am currently experiencing the same issue after moving the GW to new VMs. thanks!

    • chrisgill's avatar
      chrisgill
      Frequent Visitor
      1 year ago

      We are currently working with Microsoft. They suggested two things for us.

      1. Make sure we have at least 15 minutes between refreshes that go through the gateway

      2. Make sure the primary gateway is installed on the database server. This is the item we are still working on. The first did not resolve our issue.

       

      Chris