Bug #61356 Re-install fails with security settings
Submitted: 30 May 2011 15:07 Modified: 10 Jan 2013 12:13
Reporter: Arve Knudsen Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Installing Severity:S1 (Critical)
Version:5.5.12, 5.5.17, 5.5.25a OS:Windows (Server 2008 R2 x64)
Assigned to: CPU Architecture:Any
Tags: install

[30 May 2011 15:07] Arve Knudsen
Description:
I first installed MySQL Community Edition 5.5.12 successfully on this Windows Server 2008 R2 x64 box, then decided to uninstall it. Then I decided to give it another go, but am now unable to successfully re-install it. The launching of the MySQL Windows service, during configuration of the installation, fails consistently with this error in the event log: 

Faulting application name: mysqld.exe, version: 5.5.12.0, time stamp: 0x4da2f5f9 
Faulting module name: mysqld.exe, version: 5.5.12.0, time stamp: 0x4da2f5f9 
Exception code: 0xc0000005 
Fault offset: 0x00000000002b696c 
Faulting process id: 0x1384 
Faulting application start time: 0x01cc1eccd07f8e75 
Faulting application path: C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe 
Faulting module path: C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe 
Report Id: 0fb3d43e-8ac0-11e0-92a5-0050568c0038 

How to repeat:
1. Install MySQL Community Edition
2. Uninstall MySQL Community Edition
3. Install MySQL Community Edition
4. Watch post-installation MySQL configuration wizard fail to start Windows service
[30 May 2011 15:11] MySQL Verification Team
Thank you for the bug report. Which is the error message showed in the *.err file in data directory?. Thanks in advance.
[30 May 2011 19:01] Peter Laursen
"but am now unable to successfully re-install it" - could be becuase it was never fully uninstalled.  Refer http://bugs.mysql.com/bug.php?id=45050 for such issue

Peter
(not a MySQL person)
[30 May 2011 20:32] MySQL Verification Team
Open a command prompt as administrator and try to run the service:

net start service_name

change the service_name for the actual one.

Print here the error message. Thanks.
[31 May 2011 7:22] Arve Knudsen
Here follows the part of the log related to the last mysqld failure.

110530 15:23:50 [Note] Plugin 'FEDERATED' is disabled.
110530 15:23:50 InnoDB: The InnoDB memory heap is disabled
110530 15:23:50 InnoDB: Mutexes and rw_locks use Windows interlocked functions
110530 15:23:50 InnoDB: Compressed tables use zlib 1.2.3
110530 15:23:50 InnoDB: Initializing buffer pool, size = 2.0G
110530 15:23:51 InnoDB: Completed initialization of buffer pool
110530 15:23:51 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110530 15:23:51  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
110530 15:23:51  InnoDB: Assertion failure in thread 5020 in file fsp0fsp.c line 2101
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110530 15:23:51 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=30408704
read_buffer_size=65536
max_used_connections=0
max_threads=800
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 293889 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
000000014010696C    mysqld.exe!my_osmaperr()
0000000140106C57    mysqld.exe!my_osmaperr()
00000001400C9B1E    mysqld.exe!my_osmaperr()
00000001401251BC    mysqld.exe!my_osmaperr()
00000001400A368A    mysqld.exe!my_osmaperr()
000000014009A140    mysqld.exe!my_osmaperr()
000000013FE72736    mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
000000013FE6C0D2    mysqld.exe!?plugin_lock_by_name@@YAPEAUst_plugin_int@@PEAVTHD@@PEBUst_mysql_lex_string@@H@Z()
000000013FE71349    mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
000000013FE5BD17    mysqld.exe!handle_shutdown()
000000013FE5C88A    mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
000000013FE5CCE2    mysqld.exe!?mysql_service@@YAHPEAX@Z()
00000001401F96A7    mysqld.exe!my_mb_ctype_mb()
00000001401F9751    mysqld.exe!my_mb_ctype_mb()
0000000076AC652D    kernel32.dll!BaseThreadInitThunk()
0000000076CFC521    ntdll.dll!RtlUserThreadStart()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
[31 May 2011 7:25] Arve Knudsen
net start MySQL
The MySQL service is starting.
The MySQL service could not be started.

A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.
[31 May 2011 7:26] Arve Knudsen
Regarding bug #45050, I would wager that it explains what is happening to me; i.e., that MySQL isn't fully uninstalled.
[31 May 2011 7:43] Arve Knudsen
I found that I could work around the problem by deleting the old installation's data files (C:\ProgramData\MySQL) and database directory, after uninstalling it. The re-installation then works.
[22 Jun 2011 13:50] MySQL Verification Team
Could you please try version 5.2.13. Thanks.
[8 Jul 2011 7:38] Andrea Palmate'
I can confirm this bug also with mysql 5.5.14 and my windows7 64 bit.
I've just uninstalled MySQL and i've tried to reinstall it with same error
[20 Jul 2011 13:32] Arve Knudsen
I've tried 5.5.14 now and it solves the problem of the service being unable to start after reinstalling, but the service configuration step fails due to the previous installation being password protected. I configure the new installation with the same password however, so I don't see why it should be a problem...

See error screenshot here: http://imgur.com/X77A4.
[14 Nov 2011 14:24] MySQL Verification Team
Verified with 5.5.17 on Windows 2008. Changed synopsis.
[14 Nov 2011 14:25] MySQL Verification Team
Security settings failed

Attachment: reinstall_failed.png (image/png, text), 381.45 KiB.

[28 Nov 2011 22:42] Jacek Blaszczynski
Simple workaround for that issue: delete all files under %PROGRAMDATA%\MySQL including MySQL diectory before reinstallation. If you have data directory holding any system tables in another location left after uninstall remove them as well or point to a new location in configuration wizard.
[16 Jul 2012 14:37] Valeriy Kravchuk
Bug #65907 was marked as a duplicate of this one.
[16 Jul 2012 15:17] JASE IT Staff
* Coming over from Bug #65907*

None of these solutions worked. The MySQL service will still not start. What do we do? We have clients killing us this morning because their blogs are offline.
[16 Jul 2012 16:28] JASE IT Staff
If it helps, this is the error in the Application Log:

- System 
  - Provider 
   [ Name]  Application Error 

  - EventID 1000 

   [ Qualifiers]  0 
 
   Level 2 
 
   Task 100 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2012-07-16T10:17:31.000000000Z 
 
   EventRecordID 9059 
 
   Channel Application 
 
   Computer
 
   Security 
 

- EventData 

   mysqld.exe 
   5.5.25.0 
   4ff2008d 
   mysqld.exe 
   5.5.25.0 
   4ff2008d 
   c0000005 
   00000000002bd88c 
   13f0 
   01cd633c353ec76b 
   C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe 
   C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe 
   7332bb93-cf2f-11e1-afac-842b2b63c93e
[16 Jul 2012 20:12] JASE IT Staff
Hello? Anyone around?
[26 Nov 2012 9:42] roihfo ijfowe
I had the same bug and it seems the problem is an unclean uninstallation. The
Uninstallation leaves the installation directory with configuration items - remove them. Also go to C:\ProgramData and remove the MySQL directory.
If you want to be on the safe side, you can always run regedit and find "mysql" and remove all references to the MySQL you installed.
[10 Jan 2013 12:13] Erlend Dahl
We are unable to repeat this internally.