MySQL Bugs: #65907: MySQL Service will not start on Windows Server 2008 R2 Standard

Bug #65907	MySQL Service will not start on Windows Server 2008 R2 Standard
Submitted:	16 Jul 2012 7:15	Modified:	16 Jul 2012 20:13
Reporter:	JASE IT Staff	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Windows	Severity:	S1 (Critical)
Version:	mysql-5.5.25a-winx64	OS:	Windows (Windows Server 2008 R2 Standard)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Service will not start manually or through the automatic startup process. We have uninstalled MYSQL and reinstalled with no better result.

How to repeat:
Run the install process with mysql-5.5.25a-winx64

FYI: No antivirus is running.

Did you install it as Administrator?

Do you see anything in the error log (<hostname>.err file in the datadir)?

Yes, installed as administrator on the console.

ERROR LOG:

120716  5:44:01 [Note] Plugin 'FEDERATED' is disabled.
120716  5:44:01 InnoDB: The InnoDB memory heap is disabled
120716  5:44:01 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120716  5:44:01 InnoDB: Compressed tables use zlib 1.2.3
120716  5:44:01 InnoDB: Initializing buffer pool, size = 128.0M
120716  5:44:01 InnoDB: Completed initialization of buffer pool
120716  5:44:01 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!
120716  5:44:01  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...
120716  5:44:02  InnoDB: Assertion failure in thread 3880 in file fsp0fsp.c line 2102
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.

Check bug #55529 for possible workarounds.

These tips did not resolve our issues. Please assist. Thank you.

Then this is a duplicate of another known verified bug, Bug #61356.

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.

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

Hello? Anyone around?