Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Azure Databricks Connection Issue Via On premise Gateway

issue

You can see the Issue in the image. This is occurring when setting up a connection within the PowerBi Service.All things are updated. This was working previously. Reports connected are refreshing on the Desktop with ease,but are failing to refresh sometimes on the service. If in a day a scheduled refresh is enabled 5 times it errors out on 4. I am also pasting the error here which i receive on most of the reports if the scheduled refresh has failed.
error:

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<ccon>ODBC: ERROR [HY000] [Microsoft][ThriftExtension] (14) Unexpected response from server during a HTTP connection: Could not refill buffer.</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"Databricks"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"<ccon>{\"host\":\"adb-7620231adasd27.7.azuredatabricks.net\",\"httpPath\":\"\\/sql\\/1.0\\/warehouses\\/fb5asdasd14676e7\"}</ccon>"}},{"code":"Microsoft.Data.Mashup.ValueError.OdbcErrors","detail":{"type":1,"value":"#table({\"SQLState\", \"NativeError\", \"Message\"}, {})"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: Sccrp/PqOV Mekig.

5 Replies

  • Aside from the ol' Microsoft "uh yeah, just restart it", does anyone have an actual solution for this issue? 

    I too am running into this problem when refreshing a Power BI semantic model on Power BI Service that uses DataBricks as a data source.  Just like the OP says, our semantic model will fail sort of randomly, maybe 25-30% of the times we refresh the model it fails.  It makes no sense.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous 

     

    Will it work if you refresh the semantic model manually?

     

    Here are some steps for your reference:

    Ensure that your on-premises data gateway is up-to-date and running properly. Sometimes, simply restarting the gateway can resolve the issue.

    Try to re-authenticate the data sources credentials and the Gateway Connection.

    If multiple scheduled refreshes occur at the same time, try to stagger their occurrences, as too many refreshes for the same event may result in timeouts due to resource usage.

     

    Best Regards

    Zhengdong Xu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi, I have tried all above but the issue still persists.

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi Anonymous 

         

        Given I have so little information at this time, I can't tell what's causing your problem.You can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.

        It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

        The link of Power BI Support:  https://powerbi.microsoft.com/en-us/support/

        For how to create a support ticket, please refer to How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

        Thank you for your understanding.

         

        Best Regards

        Zhengdong Xu
        If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Known Issue

    I do not know if this known issue is causing issues. I cannot see on the fixed issues site that the issue has been resolved or whats the proposed solution.