Forum Discussion

jdelhoyo's avatar
jdelhoyo
Frequent Visitor
6 years ago
Solved

Simba Spark on premise gateway connection.

 Hi!

 

My name is Javier. It is my first post in the community. I have a dashboard in which I have changed the data source from MySQL to Hive and Spark 2.4.5 (spark thrift server) succesfully on desktop creating an ODBC connection with Simba Spark ODBC Driver. However, when I try to create the new gateway connection on the server, after creating the same ODBC connection with the same name that the pbix have, the gateway show me this error.

I've tried to figure it out a solution creating new connection, using other drivers but impossible.

 

Thanks for your support.

 

 

 

 

  • Eventually, I've solved the problem writing the connection string instead of choosing the ODBC connection in the data source windows. This is the connection string that I wrote: Driver=Simba Spark ODBC Driver; Host=XXXXXX; Port=10001; AuthMech=3.

     

    I hope it could be helpful.

4 Replies

    • v-yingjl's avatar
      v-yingjl
      Icon for Community Support rankCommunity Support

      Hi jdelhoyo ,

      There seems to be some encryption enabled at your end, that does not allow the other user to access the ODBC driver connection.

      This could be some Windows level configuration or some security parameter.

      You need to change the authentication menthod when configuring gateway instead of anonymous to certify ODBC.

      You can also refer this similar issue:

      https://community.cloudera.com/t5/Support-Questions/Using-Cloudera-Hive-ODBC-Driver-with-SSIS-run-as-account/td-p/281047

       

      Best Regards,
      Yingjie Li

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

      • jdelhoyo's avatar
        jdelhoyo
        Frequent Visitor

        Thanks v-yingjl . I've tried with the info in the link but I'm still unable to set up the connection. I've upload a pbix with only one source and a simple query but I'm still getting the same error. It's really frustating.