MySQL Bugs: #67212: Installer crashes when you try to start the service mysql on windows server 2008

Bug #67212	Installer crashes when you try to start the service mysql on windows server 2008
Submitted:	12 Oct 2012 18:48	Modified:	22 Jun 2013 22:15
Reporter:	Rodolfo Andrade	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	5.5.28	OS:	Microsoft Windows (Server 2008)
Assigned to:		CPU Architecture:	Any
Tags:	crash, installer, not start, service

Description:
When installing MySQL Server 5.5.28 on Windows Server 2008. The installer crashes when trying to start the service. The following content appears in the log file:

121007 11:04:42 [Note] Plugin 'FEDERATED' is disabled.
121007 11:04:42 InnoDB: The InnoDB memory heap is disabled
121007 11:04:42 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121007 11:04:42 InnoDB: Compressed tables use zlib 1.2.3
121007 11:04:42 InnoDB: Initializing buffer pool, size = 686.0M
121007 11:04:43 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file. \ Ib_logfile0 is of different size 0 196083712 bytes
InnoDB: than specified in the. Cnf file 0 359661568 bytes!
121007 11:04:43 [ERROR] Plugin 'InnoDB' init function returned error.
121007 11:04:43 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
121007 11:04:43 [ERROR] Unknown / unsupported storage engine: INNODB
121007 11:04:43 [ERROR] Aborting

121007 11:04:43 [Note] mysqld: Shutdown complete

How to repeat:
Try to install MySQL Server 5.5 in a Windows Server 2008 or try to run MySQLInstanceConfig.exe

Suggested fix:
To fix the problem, edit the my.ini file and place the same value of the ib_logfile0 file reported in log. The variable is innodb_log_buffer_size.
Restart the service.

But as the installer crashes before performing the security settings of the root user. Then you must also create the root user manually generating capabilities.

I believe this problem is related to this other bug to Microsoft, because I have other problems sizes of log files on my computer:
http://support.microsoft.com/kb/2470478.

The problems started appearing after I changed my hardware for SATA3, so I think this link has to do with these problems.

Is this the first time you install MySQL on this machine or you had some older version before? Also, is this 32-bit or 64-bit Windows and MySQL binaries?

It is the first installation. MySQL and Windows Server 2008 both 64bits. To repeat the problem I believe you must use a motherboard and a hard drive with SATA3, because I think that the OS has a problem with the hardware according to the Microsoft link I posted.

This isn't a hardware problem:

InnoDB: Error: log file. \ Ib_logfile0 is of different size 0 196083712 bytes
InnoDB: than specified in the. Cnf file 0 359661568 bytes!

It means existing ib_logfile* of 187M was there, but the current my.ini specified 343M.

Please check what Shane commented before. Thanks.

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