Error Running MySQl 4.1 on XP

Rex__

i am having the exact same problem that was posted here...

http://www.phpbuilder.com/board/showthread.php?threadid=65619&highlight=1067

i installed apache2, then php, then mysql 4x. it seemed to run automatically as a service by default (i used the installer). everything was fine until i rebooted and now i keep getting the 1067 error.

i have tried everything. i have a my.ini in my windows folder that contains this info:

[mysqld]
basedir=C:/mysql
datadir=C:/mysql/data

[WinMySQLAdmin]
server=C:/mysql/bin/mysqld-nt.exe
user=admin
password=admin

all paths are fine, and WinMySQL's Start Check confirms this.

when i run mysql using the following command line it works ok:

mysqld-max-nt --standalone --skip-innodb

i can print out a report in WinMySQL, but i don't know if it's needed.

this is the last error in my mysql\data\computer.err file:

InnoDB: No valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to section 3.1 of
InnoDB: http://www.innodb.com/ibman.html
030609 14:04:56 Can't init databases
030609 14:04:56 Aborting

030609 14:04:56 InnoDB: Warning: shutting down a not properly started
InnoDB: or created database!
030609 14:04:56 MySql: Shutdown Complete

Rex__

i got the service to run using this command for the installation:

mysqld install --skip-innodb

and then just starting it with net start. it also managed to start it with WinMySQLadmin. this is a good start, but the problem is, obviously, innodb won't work.

i don't know alot about innodb. I know it enhances the performance of mysql and doesn't seem to be essential to it's operation or security. it appears to add speed and stability and graceful recovery to mysql. at the moment, having a small website and a fairly stable OS, i don't really need all this. nonetheless, i don't like the idea of running this thing half-baked and i am still wondering how to run this properly as a server.

i read the following at http://www.innodb.com/ibman.html#InnoDB_overview and it doesn't make sense. if only the -max binaries use innodb then why do i get this error when i install plain old mysqld?

InnoDB tables are included in the MySQL source distribution starting from 3.23.34a and are activated in the MySQL -Max binary. For Windows the -Max binaries are contained in the standard distribution.

If you have downloaded a binary version of MySQL that includes support for InnoDB, simply follow the instructions of the MySQL manual for installing a binary version of MySQL. If you already have a recent version MySQL-3.23.4x installed, then the simplest way to install MySQL -Max with the same version number 3.23.4x is to replace the server executable mysqld with the corresponding executable in the -Max distribution. MySQL and MySQL -Max differ only in the server executable.

Cuban

hi,
ive got this exact problem but none of these fixes work,
when using this command line to install the sevice:
mysqld install --skip-innodb
it installs a service called --skip-innodb
please help

Rex__

This is surprisingly common, and I hope that MySQL deals with this problem soon.

I decided to give up on MySQL 4.x and I went back to 3.23. It runs fine as a service on XP.

I have noticed that many people with this problem re-install MySQL 4.x on XP and it works fine for them and they think the problem is solved... but then they reboot and discover that the problem is there again.

One idea that I have is to install mysql 4.x, copy the my.ini file, then reboot. Compare the ini files and if different, replace the new one with the original one. Most people seem to be convinced that the problem is with the ini file paths. If this is the case, then it seems logical to record the paths while the program is running well.

I used my old 3.23 database, but I hear that you can usually use a 4.x database in 3.23 with minimal changes. If you don't have subqueries or the link (new with 4.x) then downgrading should be fast and easy.

Rex__

hey cuban, I had the same problem. This was weeks ago. I remember that it was the syntax. stop and uninstall the mysql service and then try it again at the command line is the only thing i can think of. you can also remove the service using the Services list in XP. in fact, i seem to recall that you don't need the command line at all to set up the service with our withoud innodb.

also try net start after you install. you can also try right clicking on the mysqld exe file and then click "run as..." in the menu. remember that you can't seem to add switches if the service is automatic (only if it's manual)

hope this helps.