MySQL Bugs: #118883: The ODBC connector definition GUI does not present or use existing values when editing sources

Bug #118883	The ODBC connector definition GUI does not present or use existing values when editing sources
Submitted:	22 Aug 10:31	Modified:	6 Oct 17:52
Reporter:	Horst Wieland	Email Updates:
Status:	Verified	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	8.4x, 9	OS:	Windows (10, 11)
Assigned to:		CPU Architecture:	Any
Tags:	GUI

Description:
Starting with V.8, in some environments the ODBC Connector GUI to define a data source always appears to forget it's parameters for System DSNs, despite these are written into HKLM\Software\ODBC correctly.

The server name and the password are written into the data source key after having defined them.
The data source works fine then!

With certain installations re-editing the data source by ODBCAD32 does not present some values with the GUI, which had been defined previously, despite the key still holds these. Namely a subset of User name, password and even the sever name.
When trying to test the connection by the GUI right after opening the data source it fails, unless server name and password and sometimes user name got re-entered inside the GUI.

This only happens with certain environments.
What might be wrong with these?

I recently also was confused, the data source cannot be configured to "enable auto reconnect" or use a distinct charset any more. That was clearly announced in release informations though.

Nevertheless it's still confusing, the GUI still offers those options even with the newest connectors, but does not use them any more and removes those registry values accordingy when saving.

How to repeat:
Unknown. It does not happen with my own system. I noticed this frequently with several other systems, which stubbornly refuse to work identical then.

Suggested fix:
Fix the ODBC GUI to respect connector-version specific options and always present existing values from the registry key(s), if applicable.

Hi,

I am having issues reproducing this. Can you try to upgrade to latest connector i the env. where you can reproduce the problem? Does it solve it?

As mentioned I also have issues reproducing the disappearing entries of password, server and sometimes user name with my system. It's O.K there and it ever was with all connectors. Current and previous ones.

Only the options, which don't work any more are present inside the GUI still. 
Unfortunately I didn't note where this happened recently. There are some environments. It would be interesting which system details might be needed to find in order find a reason why this happens there. Legacy libraries?
It happend with new Windows 11 systems as well as with Windows 10 before and also wit 8.0.x drivers as I remember.

additional comment. 

A colleague of mine yesterday used the newest connector 9.4, where this also happened. 

Anything to look for in such environments? I now know a case where to check.

I'm discussing this with connector team. So far we have no solution.

today i checked a system where this happened yesterday. Today the values didn't disappear when editing the data source.

Might this happen right after installing or updating the connector anew before a reboot occured? (The customer proposed this)

Nevertheless, the additional Options in "Details" which are depreciated are present still and are misleading.

Hi,

I tried today, win11 24h2, latest driver, I could not reproduce the problem on fresh install of everything (virgin windows installed few days ago no dev tools yet there).

No idea how to reproduce the problem. But most of these tools require windows restart to properly finish installing so if the problem does appear only pre first reboot, I'd call it a non problem as it is Windows we are talking about. I believe it is some Windows problem and nothing we can do about except maybe "force reboot" after installation.

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

Hello,

I attached some video captures, taken with Teamviewer, which also can replay this. (I tried to convert the videos to a more common video format, but they tend to grow enormously when doing this with teamviewer itself.)

The videos are from different machines, which ignore the password and the last one even the server name. The first machine was rebooted after having installed and configured the data source. The effect kept present.

The last machine even "forgets" the server name, which the first one doesn't.

best regards,
Horst Wieland

Hi,
I'v seen the video but I can't reproduce this. BTW We can't use free TV for "business" and we do not have a licence so please upload next time as avi/mp4...

Sorry for the tvs format. I didn't manage to install additional video codecs which show up in the teamviewer application to be used. Still struggling to achieve this for the future. 

With the default codec to create an independent format the first video would have used about 1.6 GB as AVI, which cannot be uploaded here. Glad, you was able to see this anyways.

I wonder which information we would need to identify the reason for this. I also can't reproduce this with my system. But many customer systems show this behaviour. I catched two systems with 3 individual workstations.