Mysql SERVICE will not start

[d3vlabs]

I installed XAMPP for the third time on the PC and got an error mysql service will not start -1
Here's a screenshot



http://ioj.com/164672/tmp_l4mhC.jpg

[Izzy]

Can you start MySQL clicking on the Start button - but DO NOT click on the Admin... button or you will have all sorts extra issues.

Untick the Svc boxes or run xampp\mysql\mysql_uninstallservice.bat file then try again to start MySQL

Can you start Apache?

BTW what version of Windows?
What version of XAMPP?
Both omitted.

If Vista then you have to be logged in as an Administrator and disable UAC.

[d3vlabs]

clicking on start button, says busy, then says, mysql service will not start...

apache starts fine

running vista sp1 disabled uac, logged in as admin

xampp-win32-1.7.0

thanks for quick reply

[Izzy]

BTW this is the German language forum, the English language forum is in the Apache Friends in English - XAMPP for Windows - this may be moved.

Untick the MySQL Svc box or run xampp\mysql\mysql_uninstallservice.bat file then try again to start MySQL

Did you try this?

[d3vlabs]

Untick the MySQL Svc box or run xampp\mysql\mysql_uninstallservice.bat file then try again to start MySQL

THANK YOU!

[chriswilds]

I attempted that, and it says "Click OK to uninstall mysql service". Then nothing happens. The box stays checked, nothing happens. The service still can't be started.

Thanks!

[chriswilds]

Oh, but I tried running it from the file ...uninstall.bat and it worked! <Never mind....> <blushing>

[Jeggs]

Untick the Svc boxes or run xampp\mysql\mysql_uninstallservice.bat file then try again to start MySQL

Followed these instructions and it worked for me, thanks.
Excuse my ignorance, why exactly is this a problem for mysql??.

[Sharley]

Excuse my ignorance, why exactly is this a problem for mysql??.

This may be a problem with the installer version of XAMPP on XP that has not yet been defined - the EXE (7zip) self extracting version does not have this associated problem.

However I do believe that in the next release 1.7.1 and after exhaustive beta testing that this issue may have been resolved, only time will tell.