WAMP MySQL server won't start

Check the windows service manager. It shouldn't be disabled from there.
To check that go to Start > Run > services.msc

But there is no .cnf file :-)

I searched my entire system and the only .cnf file I could find is openssl.cnf.  The error script just says "in the .cnf" file and doesn't specify which file (kind of silly if you ask me)

Why would the log file report a size difference between the actual file and the value from my.cnf if my.cnf doesn't exist?

Perhaps more imprtantly, how would I repair the discrepancy to make sure the values match?

Also, the service is started from the wamp taskbar icon which is just connected to the actual service - I double checked and the service is indeed enabled in the service manager.  When I try to start it from there, it fails for the same reason.

ok, please check for "my.ini" file.

OK, managed to manually edit my.ini to match the log size to the existing log.  Here's my new error, and this one looks far worse as it seems to point to nothing:

090928 17:14:54 [Note] Plugin 'FEDERATED' is disabled.
090928 17:14:54  InnoDB: Started; log sequence number 2 1172840417
090928 17:14:54 [ERROR] Aborting
 
090928 17:14:54  InnoDB: Starting shutdown...
090928 17:14:55  InnoDB: Shutdown completed; log sequence number 2 1172840417
090928 17:14:55 [Warning] Forcing shutdown of 1 plugins
090928 17:14:55 [Note] 

                                              

1:
2:
3:
4:
5:
6:
7:
8:

> Here's my new error, and this one looks far worse as it seems to point to nothing:
I agree, worse, and I feared you would run into something like this.

in short: your InnoDb tablespace seems corrupt.
hence, "only" a clean restore can fix the issue...

oh boy - this seems like very bad news - how can I do a "clean restore" - I thought that's what I was doing ;-)

>I have an existing ibdata file and log files in my d:\data directory
where did those files come from?

d:\data was the mysql data directory on my old windows installation
I had mysql.ini point to it.  ibdata contains all my development databases
I reinstalled windows and wamp on c, leaving d untouched

the log files and ibdata are from my previous installation

btw thanks for the speed of your replies - I'm incredibly nervous about losing the data - ibdata was working just fine on my previous installation and I did nothing to it but leave it there - this scare makes me want to go back to MyISAM just so I can feel comfortable backing up data - I thought ibdata was the only file that really mattered - now it's ibdata + the 2 log files + the form files + configuration directives, all interdependent on one another where if one file is changed, you could lose everything? blah - what a MESS!

I don't like those "bad surprises" neither.
ps: I am about to leave for bed, midnight approaching here...

the old server and my.ini were on c: which was reformatted for the new installation of windows - both my previous and new installations of WAMP were to c:\wamp - my data folder is where I keep all my data so I can reinstall if needed - i.e. I don't have the old my.ini

Would it makes to attempt to install mysql server by itself (no wamp) to see if I can isolate the issue?  

I'm not 100% sure if the wamp I just installed is the exact same version as was on my old installation (same dir though for sure).

Also, I distinctly remember running into this issue before and somehow getting around it.

Thanks again

>the old server and my.ini were on c: which was reformatted for the new installation of windows
outch ...

ok - found something that CLEARLY indicates that the data is not corrupt.  WHEW!  You scared me.
Installed an older version of WAMP  version 2.0a - and everything is working FINE!

Here's the differences in the 2 versions:

WAMP 2.0a (working):
Apache 2.2.6
PHP 5.2.5
MySql 5.0.45

WAMP 2.0i (busted):
Apache 2.2.11
PHP 5.3.0
MySQL 5.1.36

There's a big format change in the my.ini file from the 2 versions - I'm comfortable with the 2.0a version while the newer 2.0i version just scares me (probably because I can't get it working)

So again, I'll I have done is installed a different (older) version of WAMP.  I pointed my.ini to my existing data folder (datadir=d:/data) and it works without a hitch.

I'd still like to get to the bottom of why the newer version of WAMP or MySQL thinks my data is corrupt.  

I've attached copies of my old (working) my.ini and the new one(broken).

I'm guessing I can just SQL dump all the data from the old version, install the new version and re-import everything to recreate it on the new config - just wondering if there was any input as to why my ibdata file appears corrupt to a newer version of mysql.