Bug #28660 Default storage engine (InnoDB) is not available
Submitted: 24 May 2007 17:37 Modified: 24 May 2007 17:58
Reporter: Mr Wakazula Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.0.41 OS:Any
Assigned to: CPU Architecture:Any

[24 May 2007 17:37] Mr Wakazula
Description:
When installing MySql server 5.0.41, the service will fail to start and the following will be logged in the Windows Event Log:

Event Type:	Error
Event Source:	MySQL
Event Category:	None
Event ID:	100
Date:		24/05/2007
Time:		1:25:53 PM
User:		N/A
Computer:	MYCOMPUTER
Description:
Default storage engine (InnoDB) is not available

For more information, see Help and Support Center at http://www.mysql.com.  

How to repeat:
On a machine that is running an existing MySql instance (for me it was 5.0.21)...

0) Backup the existing MySql.ini file
1) GoTo: "Add/Remove Programs"
2) Unintall MySql server
3) Install MySql 5.0.41 /w the default options
4) Configure the MySql instance... do not change the existing root account
5) Start the MySql service
6) Check the Windows Event Log

To date, I have performed this installation on 4 different machines (2 XP, 2 Win2K3), all have failed with the same error. If I simply replace the MySql.ini file with the old version... all is well.

Suggested fix:
I suspect that the error is related to the MySql.ini file.
[24 May 2007 17:41] Mr Wakazula
CORRECTION
I have performed 4 installs to date.  Each server had an existing version of the MySql service.

RESULTS
- 1 XP server: installed ok
- 3 Win2003 servers: installed failed with the before mentioned error
[24 May 2007 17:48] Mr Wakazula
I understand what is happening now.

My expectation was that the new installation would inherit the properties of the existing one.  It seems that this is not the case.

My Windows Xp server was the only one that did not have custom paths for the InnoDB data file.
[24 May 2007 17:55] MySQL Verification Team
Thank you for the bug report. Could you please provide both my.ini files
(the older and new ones). Thanks in advance.
[24 May 2007 17:58] MySQL Verification Team
Closing again since you provide the answer. Thanks for the feedback.
[23 Oct 2008 22:32] Jared S
Solutions to this problem can be found in this thread http://forums.mysql.com/read.php?22,58270,58270#msg-58270