Bug #64833 MySQL Workbench is ok, but the server stopped running after a Windows 7 upgrade
Submitted: 1 Apr 2012 21:05 Modified: 23 Apr 2012 15:44
Reporter: David Sparks Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Installing Severity:S1 (Critical)
Version:5.5.22 OS:Windows (Windows 7 64bit)
Assigned to: CPU Architecture:Any

[1 Apr 2012 21:05] David Sparks
Description:
MySQL Workbench is ok, but the server stopped running after a Windows 7 upgrade.
I downloaded version 5.5.22 of the server. The msi install seemed to be ok, but could not start the server. I watched the Running Process list on the Task Manager window and it shows that mysqld.exe does come on when manually started, but stops after 5 seconds. It shows a script identical to what is recomended to insert into a CLI window. The correct paths and codes are an exact match. A program called "Windows Defender" was installed as part of the upgrade, and I cannot delete it. I am the sole superuser, yet it will not delete, saying I do not have the authorization keys.
I ran the MySQLInstanceConfig.exe program and it indicates that it is being blocked from starting the server. This is a dump of it's detail report:

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:	AppHangB1
  Application Name:	MySQLInstanceConfig.exe
  Application Version:	1.0.17.0
  Application Timestamp:	2a425e19
  Hang Signature:	7389
  Hang Type:	0
  OS Version:	6.1.7600.2.0.0.256.48
  Locale ID:	1033
  Additional Hang Signature 1:	73898d898b4748ce5aabd4be25d3e9f7
  Additional Hang Signature 2:	7727
  Additional Hang Signature 3:	77271e528a0fa6467b4df2d611564543
  Additional Hang Signature 4:	7389
  Additional Hang Signature 5:	73898d898b4748ce5aabd4be25d3e9f7
  Additional Hang Signature 6:	7727
  Additional Hang Signature 7:	77271e528a0fa6467b4df2d611564543

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

How to repeat:
I can manually start the server from Workbench, but it only runs for 5 seconds, then stops.
As an addendum note, after the windows upgrade I had to re-install a copy of the php5apache2_2.dll into the System32 folder. At least Apache and PHP are now working again, but PHP has no server link of course.
Also, the original InnoDB data base was corrupted beyond use, so if I can get the server running I will have to use Workbench to re-do all the sql files I lost.

Suggested fix:
Reinstall Windows from the DVD, which did not have these upgrades, or find a .dll (or create one) that can be manually installed into the System32 file to allow MySQL Server to work, much the same way I have to install a dll for Apache and php to work together.
[2 Apr 2012 6:59] Valeriy Kravchuk
Please, upload the error log of you MySQL server. It is usually called <hostname>.err and is located in the datadir.
[2 Apr 2012 16:28] David Sparks
This is the latest (host).err report you asked for, after reviewing an older version and correcting some path and data-type (it is now utf8) mistakes.
The results are almost the same as before. It is progressing closer to a stable startup, but the server still stops after 5 seconds. It would seem that this database still is missing crucial MySQL files due to corruption or a memory leak.
I do plan to install this setup as a LAMP in my Dell 390 running Ubuntu, as it is my only pc with true RAID 5 built in, but it will have to wait until I can purchase more monitors. This pc I am using now is a Dell 690 Workstation with 2 quad cores and 8GB ram. I have 4 of these pc's, but this is the only one with a WAMP installed as a local loop-back (LLB). Here is the dump from the err file:

120402 12:07:29 [Note] Plugin 'FEDERATED' is disabled.
C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Table 'mysql.plugin' doesn't exist
120402 12:07:29 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
120402 12:07:29 InnoDB: The InnoDB memory heap is disabled
120402 12:07:29 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120402 12:07:29 InnoDB: Compressed tables use zlib 1.2.3
120402 12:07:29 InnoDB: Initializing buffer pool, size = 107.0M
120402 12:07:29 InnoDB: Completed initialization of buffer pool
120402 12:07:29  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 54 MB
InnoDB: Database physically writes the file full: wait...
120402 12:07:30  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 54 MB
InnoDB: Database physically writes the file full: wait...
120402 12:07:31 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!
120402 12:07:31  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...
120402 12:07:31  InnoDB: Waiting for the background threads to start
120402 12:07:32 InnoDB: 1.1.8 started; log sequence number 1595916
120402 12:07:33 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
[2 Apr 2012 17:26] Valeriy Kravchuk
This is critical:

120402 12:07:33 [ERROR] Fatal error: Can't open and lock privilege tables: Table
'mysql.host' doesn't exist

Can you, please, check datadir\mysql directory content? If you see nothing there, then these important tables were removed, and you have either to restore them from backup or place like C:\Program Files\MySQL\MySQL Server 5.5\data, or to create new ones with mysql_upgrade.exe.
[8 Apr 2012 15:37] David Sparks
I looked at the InnoDB Database and it is 10MB of space characters. It was never formatted. I mover the database to MySQL\MySQL Server 5.5\data, and ran mysql_upgrade.exe, and the MySQLInstanceCofig.exe, which hangs up when trying to start the server. It also shows 2 instances of the server. Version 5.1 in the (x86) MySQL\MySQL Workbench directory and the 5.5.22 version in the 64 bit directory. It seems that the first time I had these working (about a year ago)I installed MySQL Workbench last. Apache and PHP work just fine-they are also in the Windows\Programs (x86) directory. This is the dump from the path list shown on the PHP Info screen:

C:\Program Files (x86)\PHP\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\Program Files (x86)\IVI Foundation\IVI\bin;C:\Program Files\IVI Foundation\IVI\bin;

I think I will save my .mwb and .sql copies to a isolated file and re-install MySql Worbench after the server has been re-installed. With both programs temporarily deleted I will run a registry cleaner and get rid of loose DLL's that could be causing Windows to block the install or prevent the server from being formatted. This worked a year ago, maybe it will work again.
DS
[19 Apr 2012 19:50] Sveta Smirnova
Thank you for the feedback.

Your problem is you pointed MySQL server to wrong datadir. Most likely this is just some empty dir, because error log shows messages "InnoDB: Log file .\ib_logfile1 did not exist: new to be created" This is misconfiguration and nor dll issue, neither MySQL bug.
[23 Apr 2012 15:44] David Sparks
Thanks for the clues Svetna. I have tried re-installing both the MySQL server and MySQL Workbench, but the installs fail when trying to start-up the programs. Both programs show a Python.exe CLI window and an error message stating that the "startup command lines were rejected by the OS. Installation aborted."
After the last Windows upgrade I have noticed that the few programs I had that used Python have all stopped working.
After 2 weeks of this I am not sure if it is a Python compatibility issue or what.
I have stopped this attempt for the time being and gone on to writing more of the javascript code I need for my pages. Apache and PHP are working just fine, but have no database to query.
I may wait until my Ubuntu server is working (I have to replace the motherboard)and install MySQL server and Workbench in that workstation.