Forum Discussion

MOVC's avatar
MOVC
Icon for Resolver I rankResolver I
2 years ago

Dataflow Gen2 Failure: Couldn't refresh the entity, transport-level error

This morning one of our Gen2 Dataflows began failing. It takes data from our On Prem SQL Server via the Data Gateway and creates a new table in a Warehouse with the replace method. The error message ...
Dataflows
Need Help
miguel's avatar
miguel
Icon for Community Admin rankCommunity Admin
2 years ago

Hi

Please go ahead and raise a support ticket so an engineer can take a closer look at this situation.

https://support.fabric.microsoft.com/support

 

If you've isolated the issue to a particular workspace, then this would require an investigation by our support ticket.

MOVC's avatar
MOVC
Icon for Resolver I rankResolver I
2 years ago

I have created the ticket.

  • v-cboorla-msft's avatar
    v-cboorla-msft
    Icon for Microsoft Employee rankMicrosoft Employee
    2 years ago

    Hi MOVC 

     

    Apologies for the delay in the response from my end.

    We appreciate your initiative in raising a support ticket. Could you kindly share the ticket number with us for our reference and tracking purposes.

     

    Thanks

    • MOVC's avatar
      MOVC
      Icon for Resolver I rankResolver I
      2 years ago

      It was TrackingID#2402130050003994

       

      Updating the gateway fixed the issue for that workspace but we were unable to figure out what the actual cause was, as the previous version of the gateway was able to perform the same activities in a different workspace. 

       

      As we can continue working this is resolved but frustrating to have these issues keep occurring (and not knowing the cause).

      • JayJay11's avatar
        JayJay11
        Icon for Resolver II rankResolver II
        2 years ago

        Seeing this thread just now, we are also having problems with Gen2 flows using an On-Prem Gateway since last week. Downgrading to the Gateway September 2023 version has resolved the situation for us for the moment. I hope MFST escalates this topic and a hotfix can be delivered asap.