This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Recently, we have upgraded the simba ODBC driver for Google BigQuery to 2.5.0.1001, and re-created the sytem DSN and Linked Server. We are getting the following error then connecting to the BigQuery.
[Simba][DriverSupport] (1030) Failed to decrypt data: Key not valid for use in specified state.
That means re-creating the DSN won't solving the issue mentioned in the document. Do we have to downgrade the driver version in order to fix this issue?
Caution: If you are upgrading to BigQuery ODBC 2.5 on the Windows platform, you may see a "Failed to decrypt" data error after the upgrade. To resolve the issue, recreate your data source names (DSNs).
Hey @cassiemkt I've seen this error come up on Windows machines. Sometimes it can be resolves by looking at users permissions on the machines and ensuring that this driver is available to all users... the other solution I've seen floated is downgrading to a previous version of the driver.
Let us know if you're still experiencing this issue... and if not, how did you fix it?!
Hey @cassiemkt I've seen this error come up on Windows machines. Sometimes it can be resolves by looking at users permissions on the machines and ensuring that this driver is available to all users... the other solution I've seen floated is downgrading to a previous version of the driver.
Let us know if you're still experiencing this issue... and if not, how did you fix it?!
Hi Roderick, thanks for your suggestions. I have downgraded to the previous version and now it works. I am not sure when can I apply latest patch without this issue...
I am able to fix the issue by executing the client (Studio) as an Administrator - as ODBC driver installed and given access to only Administrator. Thanks.
Tried different versions of Simba Odbc Driver for Big Query Failed to decrypt data: The parameter is incorrect." There is no permission issue. Tried to configure the driver for all user using this machine still same issue. Tried different user profile
LinkedIn
Twitter
