Forum Discussion
Re: Issues with Vertica Scheduled refresh
I've already set it up in the ODBC System DSN and in my gateway connections. Yet, when I try to sign in in the database through the dataset options in the web it says the same thing:
I dont undertand why if PBI has a native connector for Vertica is asking me for this drivers?
Thank you in advance!
No, it's much worse. When you select the "native" Vertica connector in the gateway what you get behind the scenes is the Simba 8.0 ODBC driver that doesn't work for you.
What you _should_ do instead is to use ODBC as the connector, and install the official Vertica 9.01 ODBC driver (from Vertica, not from Microsoft or Simba).
To get rid of the Simba driver issue you probably have to uninstall and reinstall the gateway, or even mess around in the registry.
19 Replies
v-yingjlCommunity Support
Hi Anonymous ,
Maybe your gateway cannot read this driver.
Please check:
- Whether your service account has permission to the driver folder
- Try to change the gateway account type to domain account in your test environment
You can also refer this article: Vertica Integration with Microsoft Power BI: Connection Guide
Best Regards,
Yingjie LiIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Thank you v-yingjl for replying!
Yes, It seems like it does not recognized / found the driver.
I've already set my gateway account type and it did not work, yet im still trying to see if my gateway account has access to where the driver is stored. For now when I look into the gateway it appears this message in the connectors tab:
Could you help me out with this?
Thank you in advance!- v-yingjl
Hi Anonymous ,
Try to change the gateway account as a domain account and restart gateway:
Please refer this document and issue:
- Change the on-premises data gateway service account
- Password of Default service account (NT SERVICE\PBIEgwService)
Best Regards,
Yingjie LiIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
- lbendlin
Super User
It's complaining about Simba because you chose to use ODBC as the connection type. You need to change your connection type on the desktop and the gateway to the native Vertica driver (unless you have a really good reason for needing ODBC, like custom query etc)
An ODBC (DSN flavor) connection string looks like this:
{"connectionString":"DSN=DATA_DSN"}
A Vertica connection string looks like this:
{"extensionDataSourceKind":"Vertica","extensionDataSourcePath":"server.domain.net;database"}
Hey lbendlin ! Thank you for replying,
I am using the native vertica connector in the desktop application and in my gateway.
Any suggestions?- lbendlin
That's different from what you state in the original post. Have you switched the connection type around? Note that it needs to be absolutely consistent between desktop and gateway. The connection strings have to be EXACTLY the same.