MySQL Bugs: #19139: Installation did not work

Bug #19139	Installation did not work
Submitted:	17 Apr 2006 14:33	Modified:	17 May 2006 17:21
Reporter:	NOT_FOUND NOT_FOUND	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0	OS:	Windows (Win XP Home SP2)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I downloaded 5.0 from a mirror, installed with all defaults.   Went to Programs > MySQL 5.0 > Instance Config Wizard.   I chose what looked to be all the defaults, and on the last screen, hit Execute. 

All it said was "The service could not be started. Error: 0".

I have and AMD Athlon with 1 gig RAM, lots of disk space, 

How to repeat:
Follow the installation instructions, and take all the defaults.  I have no idea what else to try.   I can't believe that my setup is that unique.

Thank you for the bug report. Could you please see if actually the service
is not running then go to \bin install directory and issue:

mysqld-nt --defaults-file=path_your\my.ini --standalone --console

and please gives us the error message printed.

Thanks in advance.

InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number <if stored to page already> 0,
InnoDB: space id <if created with >= MySQL-4.1.1 and stored already> 0
060417 11:23:15 [ERROR] mysqld-nt: Got signal 11.  Aborting!
060417 11:23:15 [ERROR] Aborting
060417 11:23:15 [Note] mysqld-nt: Shutdown complete

Thank you for the feedback.
If you did a fresh install and you don't have data on your InnoDB table space
then you can delete all the log and data InnoDB files (data directory or the
path on your my.ini file) and start the server again how you did before from
the prompt screen. See if at this time these files are created correctly.

Then shutdown the server:

mysqladmin -uroot shutdown

and try to start the service.

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