Forum Discussion
Error when connecting to Azure HDInsight Spark with Power BI Pro
I've followed the instructions at https://docs.microsoft.com/en-us/power-bi/spark-on-hdinsight-with-direct-connect and always receive the error: "We are unable to establish connection, please check connection information". I'm definitely copying the instance address correctly and I've verified the login credentials multiple times.
My HDInsight cluster type is: Spark 2.0 on Linux (HDI 3.5)
The error doesn't give any other information and I've even tried opening all inbound ports in the azure security group in case it was a firewall issue, but to no avail.
Are there any additional troubleshooting tricks to conencting Power Bi Pro to HDInsight?
Thanks!
Solved this: turns out HDInsight was accepting a >20char password at instance creation (and for instance login) but was rejecting it when passed via Power BI. Somewhere there's probably clipping going on. Reducing my password down to <= 20chars fixed the Power BI connection issue.
In case Power BI Support is reading this: it would be great if the error was more descriptive, as it was unclear if the issue was connecting to the service or authenticating. Had I known it was an authentication issue I would have found the solution much faster, but the "We are unable to establish connection" text implied it was a connectivity issue.
2 Replies
- john3ganNew Member
Solved this: turns out HDInsight was accepting a >20char password at instance creation (and for instance login) but was rejecting it when passed via Power BI. Somewhere there's probably clipping going on. Reducing my password down to <= 20chars fixed the Power BI connection issue.
In case Power BI Support is reading this: it would be great if the error was more descriptive, as it was unclear if the issue was connecting to the service or authenticating. Had I known it was an authentication issue I would have found the solution much faster, but the "We are unable to establish connection" text implied it was a connectivity issue.
- AnonymousNot applicable
john3gan,
Glad to hear the issue is solved, you can accept your reply as answer to close this thread.
Regards,
Lydia