MySQL Bugs: #62553: Can not install 6.4.4. on a system formerly running an earlier version

Bug #62553	Can not install 6.4.4. on a system formerly running an earlier version
Submitted:	27 Sep 2011 16:42	Modified:	9 Mar 2012 21:01
Reporter:	Louis Breda van	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.4.4 and others	OS:	Windows (windows7 64 bit)
Assigned to:	Gabriela Martinez Sanchez	CPU Architecture:	Any
Tags:	install

Description:
Hello,

I was not capable ot installing 6.4.4 on a system running 6.4.3 before.

Please fix this.

Sincerely,

Louis

How to repeat:
- install an earlier version

- run the installer. It will stop as soonas it detects an earlier version

- remove that earlier version via windows config screen programms
(in my case that worked ok)

- run the installer again. It will stop telling you that there is an earlier version installed (not true, however I assume there are "left overs" due to an improper remove script) 

Suggested fix:
I do not know. This is not the first time the .net connector installer does not work. So there were workarrounds with previes version.

Did not put effort in it jet. But I hate this! An update install schould just work!!!!

And this is not the first complain!

Sincerely,

Louis

Older connector .NET installed

Attachment: older-connector-net.png (image/png, text), 31.99 KiB.

Message to remove older connector .NET

Attachment: warning-connector-net.png (image/png, text), 83.69 KiB.

New 6.4.4 .NET connector installed

Attachment: new-connector-net.png (image/png, text), 47.47 KiB.

I couldn't repeat on Windows Server 2008, prior pictures attached showing: a prior connector .NET installed, the message to remove that early version and the successfully 6.4.4 install after the removed early version.

I was able to install 6.4.4 on top of existing 6.3.7 on 32-bit Windows XP without any problems.

Hello,

I tried again. Of course same result. Other version still installed (not true).

So, I checked windows programs/programs86 directorys and the programdata directory's no leftovers visible there.

I logged in with my admin account, did not change any thing.

Surched on the internet finding multiple very old reports about this issue.  

e.g. http://blog.shlomoid.com/2008/10/problems-uninstalling-mysql-connector.html

And of course multiple complains on the bug form from me and many others.

e.g. http://forums.mysql.com/read.php?38,389637,389637

e.g. http://bugs.mysql.com/bug.php?id=32141

etc, etc, etc.

To help you, please provide me with a debug version of the installer, which exactly shows what the problem is. Then I will test for you.

Sincerely,

Louis

Hello,

Perhaps a hint. I realised that the connector was ofcource used in favor for a visual basic.net program.

So, I opened the thatprogramm with visual studio, and removed ther reference towards mysql.net connector

Removed 6.4.3 
Tryed to install 6.4.4 Sorry no way !

reinstalled 6.4.3 no problem

Sincerely,

Louis

Tried to reproduce it but no luck. Could you please provide us the files (.msi) that you used?

Hello,

I just downloaded the msi from oracle and verified the md5. So that is the msi I used.

That is not the problem. The problem is (I estimate) that the deinstaller leaves some left overs which "desturbs" the new install.

I repeat my offer, please probide me with an installer which output in a debug file what it is doing why it is stopping. That will not solve the problem, but solving the problem is proably peanuts if you know the problem !

The actual installer fault message is just far to global !!

Sincerely,

Louis

MSI logging from not working Installation

Attachment: 20111014 InstalllogMySQLconnector644.txt (text/plain), 43.13 KiB.

msi and sysinternals procexp dumps (multiple formats) of not successfull install

Attachment: 20110114 InstallLogs.rar (application/octet-stream, text), 369.62 KiB.

Could you please provide the application and system event viewer logs?
Thanks in advance,

Gabriela,

Because of your request for:

"Could you please provide the application and system event viewer logs?
Thanks in advance,"

I have been looking into the MS-windows logs. Looking into the different logs, 

I noticed that mysql was accessing the mysql data directory, trying to put a testfile there (MAIN.lower-test). That directry was not normally mounted. So repaired that and also started the server first. Like expected that did not fix the problem, but never the less "I fixed" it. However I am almost sure it has any thing to do with the problem (error was reported by mysql not the installer).  

Looking further I found an mysql error installer error message
"Het product is geïnstalleerd. Productnaam: MySQL Connector Net 6.4.4. Productversie: 6.4.4. Producttaal: 1033. Fabrikant: Oracle. Fabrikant: Oracle. Status van geslaagde/mislukte installatie: 1603."

That error code 1603 could perhaps help you! 
Whatever, I suggest that you show the errornumber in the normal error window ! 
 
Sincerely,

Louis

Hello,

Nowing now that the errorcode is 1603 (what ever in means), I find even more error reports. 

It is really time to fix it !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

In fact it is ashame that the problem is still there after many years! And aside of that it is costy and time consuming for every body. Oracle and there customers!

Louis
Louis

Hi Louis, I did try to reproduce again the issue but still I couldn't reproduce it. I think that the problem was that the library was being used by the application that you mentioned. In the other hand there have been several improvements in the installer of the connector in the latest version 6.5.2 which I strongly recommend you to try it. Please let us know if you were able to install it. And last I looked for references to MAIN.lower-test file but there's not any.
 
Hope you can give us some feedback.

Thanks,

Hello,

At the end I managed to get rid of the old installation. Can not remember exactly what I did (I really spend a lot of time on it (perhaps days) ). Among the things I did:
- removing the mysql references from my (not running) .net applications
- removing (nearly) all mysql packages, also leftovers by hand
- deleting a "all" of registry keys I could possible find related to "mysql and oracle" with regedit
- installing applications again
- making the references to mysql in .net again

At the end it worked again. I am using 6.4.4 now. 

Sincerely,

Louis