Forum Discussion

pkn7's avatar
pkn7
Frequent Visitor
1 year ago

Schedule refresh failed having azure databricks as source

Hi,

One of our dataset scheduled for refresh every half n hour, fails randomly due to one or the other issues. But gets successfully refreshed in the next refresh cycle. Now it got failed with the below error message. Kindly help me understand what is the root cause of the refresh failure.

 

DataSource.Error: ODBC: ERROR [HY000] [Microsoft][ThriftExtension] (14) Unexpected response from server during a HTTP connection: Bad Status: Unrecognized response with no error message header. Status code: 500.. DataSourceKind = Databricks. DataSourcePath={***************************************************************************};OdbcErrors = #table({"SQLState", "NativeError", "Message"}, {}). . The exception was raised by the IDbCommand interface</span></td>

 

 

Thanks,

Priyanga

2 Replies

  • vanessafvg's avatar
    vanessafvg
    Community Champion

    that is quite a generalish error, could be a timeout, has it run successfully since then?   what time of day do you usually get these issues?

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi pkn7 ,

     

    Thank you for reaching out. I understand that your dataset refresh is failing intermittently.

    This error typically indicates an issue with the HTTP connection to the Databricks server, resulting in a status code 500 (Internal Server Error). Ensure that the Databricks server is running and accessible. Sometimes, server-side issues can cause intermittent connectivity problems.

    And I agree with vanessafvg. Sometimes increasing the timeout settings for the ODBC connection can help mitigate intermittent issues.

     

    Best Regards,

    Stephen Tao

     

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