Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to connect using 4.0.34 version #1095

Closed
achettyiitr opened this issue Aug 18, 2022 · 9 comments
Closed

Failed to connect using 4.0.34 version #1095

achettyiitr opened this issue Aug 18, 2022 · 9 comments

Comments

@achettyiitr
Copy link

achettyiitr commented Aug 18, 2022

Issue

Getting this particular error for DSN-less connection string for the recent version 4.0.34. It's working with the 4.0.32 version.

('IM002', '[IM002] [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0) (SQLDriverConnect)')

@achettyiitr achettyiitr changed the title Failed to connect using Failed to connect using 4.0.34 version Aug 18, 2022
@v-chojas
Copy link
Contributor

Check where your odbcinst.ini is. 4.0.34 came with its own version of unixODBC which might not be looking for the odbcinst.ini in the same place as the one you installed.

@achettyiitr
Copy link
Author

Sorry, @v-chojas. I added the description incorrectly. It's working with 4.0.32. Not working with the current released version 4.0.34

@achettyiitr
Copy link
Author

achettyiitr commented Aug 19, 2022

Check where your odbcinst.ini is. 4.0.34 came with its own version of unixODBC which might not be looking for the odbcinst.ini in the same place as the one you installed.

I have both the files obdc.ini and odbcinst.ini empty since I am opting for a DSN-less connection string and specifying the Driver as well in the connection string itself. But with the current released version, it was kind of looking for configuration in these files instead of being specified in the connection string itself.

@Atheuz
Copy link

Atheuz commented Aug 19, 2022

4.0.34 is broken because it includes old libraries. I recommend not using it until it is fixed, and instead use 4.0.32.

@v-chojas
Copy link
Contributor

Indeed, avoid '34. It has already caused these problems reported here:
#1082
#1083
#1081
#1079

@TroyWitthoeft
Copy link

Reporting in with similar issues.

@v-chojas
Copy link
Contributor

We know. 4.0.34 is broken.

@TroyWitthoeft
Copy link

@v-chojas Good luck on the fix! Appreciate the feedback.

@gordthompson
Copy link
Collaborator

pyodbc 4.0.35 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants