MySQL Bugs: #33633: Crash ODBC manager when tryn to add datasource

Bug #33633	Crash ODBC manager when tryn to add datasource
Submitted:	2 Jan 2008 19:48	Modified:	29 May 2013 11:55
Reporter:	Jose Maldonado	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	5.1.1	OS:	Windows (Crash ODBC manager)
Assigned to:		CPU Architecture:	Any
Tags:	crash, Datasource, ODBC, windows

Description:
When I try to add a datasource using Windows ODBC datasource manager, I call to add a new odbc datasource could be system o user dns, I put the data on form as conection name, description, server, username, password and When to try search databases it hangs odbc manager. Username & passwords are correct when I try to use by mysql clients such as sqlyog, mysql administrator, mysql query, and othes. No way to do it work.

How to repeat:
Try to add a datasource dns from odbc manager from control panel.

Hi Jose and thanks for your report. I'm using c/ODBC 5.1 for some time now and must admit I have never seen this happening...

For a start, please uninstall all c/ODBC files from your system and then remove any files that might remain in System32 folder. Then do the fresh install and test again. Please be careful not to install wrong version!

Latest driver can be found on http://downloads.mysql.com/snapshots
(http://downloads.mysql.com/snapshots/mysql-connector-odbc-5.1/mysql-connector-odbc-noinsta...)

Still the same. Where can I send some screenshots?

Jose, you can attach files directly to this report (see "Files" tab).
As for other things, did you do like I suggested? Cleaned all "MyODBC ... " files and checked the registry (HKEY_LOCAL_MACHINE\SOFTWARE\ODBC etc)? What is the exact OS version you're using? What does DrWatson (or any other post-mortem debugger) has to say? Is the minidump of crash created? If so, please attach it to this report.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.