Bug #46111 Mysql configuration wizard error:
Submitted: 10 Jul 2009 11:30 Modified: 10 Jul 2009 13:38
Reporter: Rahul rahul Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.34 and 5.1.36 OS:Microsoft Windows (2003 server X64)
Assigned to:

[10 Jul 2009 11:30] Rahul rahul
Description:
Hi,

I tried to install MySQL 5.1.34 in a Windows 2003 64 bit system (with innodb). But during installation in the 'MySQL Server Instance Configuration Wizard' final page, 'Start Service' failed with the error 'The service could not be started'. But acutally the MySQL service is started, I can verify that by going to the 'services.msc'.

Note: Prepare configuration and Write Configuration file get success during installation in the wizard.

I have remove instance and uninstalled MySQL, and remove the MySQL directories and data dir .. restart system and try install again freshly.. I have tried these things several times but still not able to work with that.

I have followed several links and those have not help.
for eg:
http://www.swizzling.org/2009/04/01/mysql-51-installer-could-not-start-service/

When I try the msi file via, msiexec.exe /i and redirect the log file no error is there.

Pls check this and update me, is there any thing I need to do to fix these installation issues.

Another issue: I have also faced installation abort issue while installing 5.1.36 in the Windows 2003 64 bit version. (even MySQL folder also not created.)

Thanks in Advance,

Regards,
Rahul.

How to repeat:
You can Repeat it by insall 5.1.34 or 5.1.36 in Windows 64 bit system.
[10 Jul 2009 11:31] Rahul rahul
For your reference, I have also posted this issue in detail in http://forums.mysql.com/read.php?11,271140,271140
[10 Jul 2009 11:54] Peter Laursen
I have already reported the same here 3 months ago:
http://bugs.mysql.com/bug.php?id=44073

I also noticed MySQL supporter Miguel Solorzano mentioned in another discussion he had experienced the same, but still my report is not verified yet.

(But this is not a "S1" bug - read the guidelines for classification).

Peter
(not a MySQL person).
[10 Jul 2009 12:21] Miguel Solorzano
Thank you for the bug report. Actually how it was mentioned by Peter it is duplicate of bug: http://bugs.mysql.com/bug.php?id=44073.
[10 Jul 2009 13:11] Rahul rahul
Thanks for your update.

May I know, is there any reason for this issue. Because, we can install MySQL on a few systems without any issue but faced this kinda issues in a few systems.

Since, most of the people face this issue, is there any workaround on this.

Thanks in advance.

Regards,
Rahul
[10 Jul 2009 13:22] Peter Laursen
Workaround is simply to ignore the error message thrown by the service manager.  Server is running, as also you noticed. Just close that dialogue and Check in Coumputer Management .. Services that service is up and running.

Windows fixes have a hard time!  There are lot of installer/config wizard issues reported that have not been fixed for (I think) almost a year now.  My *strictly personal* guess is that Workbench project taps resources from the Windows team at MySQL (but personally I disagree with this priority)
[10 Jul 2009 13:38] Rahul rahul
hi Peter,

Thanks for your follow ups.

I have changed the Severity to Non critical. I thought that failure, may cause any security issues in my MySQL database.

Regards,
Rahul.
[17 Jul 2009 18:21] everton evaristo
In my case, i update the msi (Windows Installer 4.5 Redistributable) and install the 5.1.34 version. work's fine!