MySQL Bugs: #66760: Erroneous? error messages saving DSN files under Window 7

Bug #66760	Erroneous? error messages saving DSN files under Window 7
Submitted:	10 Sep 2012 23:57	Modified:	30 May 2013 7:06
Reporter:	Wayne Fogg	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	5.1.11	OS:	Windows (7)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	Cannot Save, save, windows 7

Description:
I am running Windows 7 using the 5.1.11 ODBC connector.

Problem 1:
All attempts to create MySQL file DSNs end with displaying “File Data Source was not saved” *if* you fill out enough information so that the connection could be verified. (Attempts to save an empty connection just get a connection could not be verified message.) Similar behavior was observed using v5.1.08 of the connector under Win 7. On the other hand the v5.1.08 would save the file without an error message under Windows XP. (I did not check v5.1.11 under Win XP.)

On the third hand, even though the error message clearly states that the file was not saved, a file is created and the contents appear to be correct.

Problem 2:
If you try to edit a DSN that has any of the boxes on the connection tab checked, you immediately get the error message “General error: Invalid file dsn…”. (Actually I am not sure that I tried all of the boxes. I know for sure the “Enable auto reconnect” and the “Don’t prompt when connecting” will do it. I’ve tried several of the others at random but I did not track which ones.)

Problem 3:
If you try to edit a DSN that has none of those boxes checked and then check any of those boxes, you get the error message “General error: Invalid file dsn…” when you attempt to save it *if* you had previously entered enough data so that the connection could be verified. Editing DSNs that were empty (and could not be verified on the previous saving) could be updated (including checking some of the boxes on the connection tab) and saved without error. However once were saved they would exhibit the behavior noted under Problem 2.

Again, I saw none of these behaviors with the Win XP machines.

These issues did not go away when the program was run as Administrator.

Wayne

How to repeat:
See Description

Suggested fix:
I haven't tried these but think you work around the problems by:
1) Ignoring the error message during the save
2) Creating new file DSN instead of updating existing ones
3) Since the DSNs are simple text files, use notepad and edit them by hand

On the other hand, when I had access to a Windows XP system, I would prepare the DSNs on that machine an copy on the Window 7 machines without an issues.

Unfortunately, the problem with the file data sources exists in Connector/ODBC 5.1, but it should be resolved in the version 5.2.
Can you try the version 5.2 from here?

http://www.mysql.com/downloads/connector/odbc/5.2.html#downloads

Note that version 5.2 has two separate drivers: ANSI and UNICODE.
Both should work with file DSNs.

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".

Duplicate of bug 24581.
The patch is on its way.