Forum Discussion
Power BI Report cannot open after Databricks cluster cloned
Today I learned that the cluster in Databricks that I was connecting my Power BI report to was stuck. A new cluster was cloned from the old one, and the old cluster was removed. Now I am seeing an error when I try to open the Power BI report:
Error Message:
<pi>OLE DB or ODBC error: [DataSource.Error] ODBC: ERROR [HY000] [Microsoft][ThriftExtension] (14) Unexpected response from server during a HTTP connection: HTTP Response code: 404 , RESOURCE_DOES_NOT_EXIST: No cluster found matching: 0805-064708-99aa0w90..
</pi>
I am able to connect to the cloned cluster just fine, but only on a new Desktop file. PBI Desktop will not even open for this old cluster. I need to access the old report so that I do not have to recreate the entire report and data model again. Is there a way I can edit the cluster connection on the old report?
- Anonymous3 years ago
Update: I upgraded to the November 2022 version of Power BI Desktop. This allowed me to open the report in Power BI Desktop. From there, I went to Transform Data -> Source and edited the HTTP Path of the Databricks connection to the new cluster. This resolved the issue.
3 Replies
- amitchandakSuper User
Anonymous , I think you need to update the datasource. Home Tab -> Transform Data -> Transform Data- > Data Source setting-> Change any connection details, clear permission, and provide credentials again
- AnonymousNot applicable
amitchandak I cannot open the report in Power BI Desktop, so I cannot get to the Data Source setting to change connection details. When I try to open the pbix file on Desktop, I see the error message above.
I wonder if it is because I am using an older version of Power BI Desktop. My version is December 2021.
- AnonymousNot applicable
Update: I upgraded to the November 2022 version of Power BI Desktop. This allowed me to open the report in Power BI Desktop. From there, I went to Transform Data -> Source and edited the HTTP Path of the Databricks connection to the new cluster. This resolved the issue.