Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I installed PHP and MySQL on our windows 2003 server about 3 months ago. Everything has been working wonderfully, but for some reason when I came into work this morning, the service had stopped working. I proceeded to start the service up again, shortly there after the service stopped again. In the Event Log for the server I have the following errors:

Application Event: Source: Application Error, Category 100, Event ID: 1000, Description: Faulting application mysqld.exe, version, faulting module mysqld.exe, version, fault address 0x002aafd7.

System Event: Source: Service Control Manager, Description: The MySQL service terminated unexpectedly. It has done this 2 time(s).

I figured something was just buggy, so I rebooted the server, same problem. As far as I know, nothing was changed on the server over the weekend.

When I launched MySQL Administrator that installed with it, And click on the Server logs, their is no information, and most boxes are grayed out.

If somebody could point me in the right direction it would be greatly appreciated.

share|improve this question
maybe add some output from mysql logs? what happens when you try to start mysqld from command line [ not as a service ] ? – pQd Jun 29 '09 at 20:45
Sorry, the error code I copied to: Thanks for your help! – Ryan Jun 29 '09 at 21:13
Was the 2k3 box patched over the weekend? – Izzy Jun 29 '09 at 21:17
Not that I'm aware off. I'm in contact with our outside server vendor and that was the first thing I asked them, and they said nobody from their end accessed the server over the weekend. – Ryan Jun 29 '09 at 21:30
up vote 0 down vote accepted

From the looks of your logs, you're hitting database errors. Ideally this would not cause the service to crash. I would look into the mysqlcheck and the associated table repair utilities to see about repairing any database errors you might have to see if that clears things up.

share|improve this answer
Thanks for the link. I just ran mysqlcheck --all-databases The output was: echo.addtypes echo.boilerplates mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ... ' It appears the the MySQL service crapped out during the middle of the check. Ugh. – Ryan Jun 29 '09 at 21:29

if you have backups - take lazy way and just restore from them. remove all table files [ or even all database dirs except mysql ] from data directory, then restore from backup. possibly you'll have to remove ib_logfileX and ibdataX files as well.

otherwise - i'm afraid you are about to gain experience in recovering innodb databases... [ i assume you use this storage somewhere, at least log suggests crash around it ].

share|improve this answer

Sounds like database corruption to me. Try a fresh install. Then restore databases one at a time till it goes crunch. Then at least you know which one is the problem. Get rid of that one and restore the rest. That just leaves you with the problem of how to repair the troublesome one. It if was mine I'd go back to an earlier backup. Good luck.

share|improve this answer

Open the MySQL administrator UI and untick Data directory in the Startup Variables section.

share|improve this answer
You could look at improving your question by going into a little more detail. – Drew Khoury Sep 7 '13 at 7:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.