Data driver error

Once I had done this, it was possible to select an On-premises gateway. Message 13 of In response to v-yuezhe-msft. Thank you! Message 12 of Thanks for that, I suppose Power BI only accepts bit drivers for data sources? Message 3 of In response to davidSIT. Message 4 of Message 5 of Message 6 of Message 7 of Message 8 of Hi Lydia, I removed the personal gateway installation and reinstalled the on-premesis gateway and recovered the gateway.

It will always be helpful to read articles from other writers and use something from other web sites. Thanks for the article! It was a great read. The driver device error code 16 usually occurs when a device has not been configured properly. There are several ways to solve this error. It can be solved by allocating more PC resources to the device or using a utility tool to assist in this process. Hello everybody. Every time it boots up I have to disable PCI driver for a few seconds to get rid of the driver error code 12 then re-enable PCI driver.

Then I have to do it again. What should I do? I would not like to go back to bit. Any help would be apprciated. Analytical cookies are used to understand how visitors interact with the website.

These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc. Advertisement Advertisement. Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns.

These cookies track visitors across websites and collect information to provide customized ads. Others Others. Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet. Did you know? ETL by more than 30x.

Online course weekend offer! Lifetime access , live demonstrations, downloadable resources and more. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". Or you specify all in the connection string, and you start with the driver. For instance:. Then again, any particular reason you are using ODBC? Else you would use SqlClient and not OdbcClient. The issue could be that you have not told us what connection string you use on the web server, to which instance you are trying to connect.

Or maybe the issue is that or crystal balls are dusty and full of scratches, so we cannot clearly see what you are doing. If I am going to make a guess out of the blue, you set up a user DSN so then it works when you run from your own user, but not when you run from the web server that runs as a service. A system DSN may work. Or a DSN-less connection string with server etc specified.