Abhilesh Gupta Posted February 14 Share Posted February 14 if we open the dashboards by browser the data are not fetched and Spotfire prompts the error in the picture below (using the analyst there are no issues and the data are fetched correctly) tss-azumw21005.westeurope.azure.st.com-e4a66b68-42a7-4b4f-90b3-7e406833ae86-20240209061129.zip Link to comment Share on other sites More sharing options...
Solution Dave Leigh Posted February 14 Solution Share Posted February 14 Hi Abhilesh We have seen this error with other customers. It is usually caused by the HTTPS request to the Azure Databricks site being refused by a Web Proxy or Firewall. In those cases the request was being redirected to a web page stating that the request was refused, which was an HTTP page for a human to read, hence the ODBC driver did not understand the response. If this is the first time you are deploying to the Web Player, please confirm that the server in question has access to the following URLs as listed in the Installation Guide: https://login.microsoft.com/* https://<databse name>.azuredatabricks.net/* If the Web Player was previously working and is now failing, then you should check with your IT team to see if any changes were made that would prevent the server accessing these URLs. The Connector allows the Web Proxy settings to be specified for just Web Player connections, so this might also be required in your environment. Cheers Dave 1 Link to comment Share on other sites More sharing options...
Abhilesh Gupta Posted March 15 Author Share Posted March 15 Hi Dave we have checked our firewall configuration & it seems to be fine. We have also aligned the drivers on all the servers. But the issue is still persists. Could you please suggest. Link to comment Share on other sites More sharing options...
Fabien GRABHERR Posted March 19 Share Posted March 19 Thank you Dave, I confirm that your idea was the correct one, we realized that some of the databricks URL were not reachable from node managers (and TSS as well by the way), and after fixing with network team problem is now solved. Thanks for your usual efficient support. Fabien 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now