MySQL Bugs: #26315: Using the EXE installer on a previous MSI installation fails

Bug #26315	Using the EXE installer on a previous MSI installation fails
Submitted:	13 Feb 2007 11:52	Modified:	26 Jul 2007 14:39
Reporter:	MC Brown	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.12	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
Setup: Windows XP, C/ODBC 3.51.12 already installed (although I didn't realize that at the time)

I downloaded the latest EXE installer for C/ODBC, when running the installer, you get an error message about not finding the MSI file required to complete the procedure. The file it is looking for is 'mysql-connector-odbc-3.51.12-win32[1].msi'. 

I then downloaded the MSI installer, but got exactly the same error, even though it was the MSI (including matching version number) that I was attempting to install from. 

In either of these two cases, clicking OK forces Windows to look again for the file and you get a more detail error saying that the network resource resource that contained the MSI could not be located, even though in both cases the Setup.EXE and MSI were both my My Documents on the local hard drive. 

Using the MSI again, with the first error, I was able to 'Browse' to the MSI and complete the installation. 

There are (possibly) two issues here:

1) Installers look in the wrong place for the components needed to complete the installation. 
2) It seems, that you cannot manage an existing installation that was handled by the MSI installer using the EXE installer, and vice versa.

How to repeat:
1) Install C/ODBC with MSI
2) Run the EXE installer to try and manage/remote installation.

Thank you for a problem report. Please, try to repeat with a newer version, 3.51.14, and inform about the results.

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've just checked the lates (3.51.17) driver and I don't get the same issue, even when updating over an old version. 

I will mark this one as closed, but keep checking the situation with future releases to make sure the same situation doesn't happen again.