Bug #63761 Errors Updating Installer from 5.5.17 to .19 on New PC with Same User Data
Submitted: 15 Dec 2011 16:37 Modified: 2 May 2012 12:01
Reporter: Scott Sanders Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL for Windows: Installer Severity:S2 (Serious)
Version:5.5.19 OS:Windows (XP Pro SP3)
Assigned to: CPU Architecture:Any
Tags: 2753

[15 Dec 2011 16:37] Scott Sanders 
Description:
My old PC had Installer 5.5.17, but that PC died, so I am on a new PC, and as it is on a domain, I still have my old user documents and settings.

When I try to do a fresh install of the new Installer 5.5.19, at first it tries to find the Installer 5.5.17, and it fails when it cannot.

So I found and downloaded Installer 5.5.17 to my desktop, but now 5.5.19 fails with error code 2753.

Maybe I must install 5.5.17 first on the new PC?

How to repeat:
Install 5.5.17 on a PC on a domain to a user profile, log onto this user profile on another PC without Installer installed, and try installing 5.5.19.
[15 Dec 2011 16:50] Scott Sanders 
Indeed, I had to install 5.5.17 and then 5.5.19 on the new PC, and now 5.5.19 works.
[19 Dec 2011 15:25] MySQL Verification Team 
Thank you for the bug report. Are you able to provide step by step the failed install process?. Thanks in advance.
[19 Dec 2011 15:25] MySQL Verification Team 
Thank you for the bug report. Are you able to provide step by step the failed install process?. Thanks in advance.
[19 Dec 2011 18:31] Scott Sanders 
On my first try installing 5.5.19, it looked for mysql-installer-5.5.17.0.msi from where I had deleted it and which was installed on my old PC. I found mysql-installer-5.5.19.0.msi on another website, downloaded it to my Desktop, and setup apparently found it but then failed with error code 2753. The setup did not do much more than that.
[2 Apr 2012 12:01] Valeriy Kravchuk 
Please, check if this still happens with a newer version of Installer, 5.5.22.1.
[3 May 2012 1:00] Bugs System 
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".