MySQL Stopped Working

[dabomb4eve]

Hello. I just started using XAMPP on Windows Vista, and so far I am enjoying how easy everything is to access.
Today, I was able to get Apache to work after some issues (with IIS), and then started using MySQL without any problems. I was doing some successful PHP connects, insert, and selects to my database, when all of a sudden, my php page stopped working. As it turns out, the connect started to fail. I was not able to stop MySQL, or restart it, or even access it using phpMyAdmin. I forced stopped it, but since then I wasn't able to start it again. I've restarted my system, done multiple uninstalls and installs, and I even deleted my data from MySQL. Whenever I try to access it, it says I can't access the database from localhost. I don't know what happened, but would like to get this up and running again with anyone's help.

From phpMyAdmin, this is what is said:

#2003 - Can't connect to MySQL server on 'localhost' (10061)
Connection for controluser as defined in your configuration failed.

Thank you in advance!

[Izzy]

Code: Select all

/* User for advanced features */
$cfg['Servers'][$i]['controluser'] = 'pma';
$cfg['Servers'][$i]['controlpass'] = '';

Look for the above section, which is from a default 1.7.2 XAMPP installation, in \xampp\phpMyAdmin\config.inc.php file and if there is a password in controlpass then remove it, save the file and restart MySQL and test again - if a password is set for controluser pma it may give you this issue.

[dabomb4eve]

My version of the file is exactly as you typed it. There is no password declared in those lines.
Thanks for the quick response, by the way!

[Izzy]

See also these forum search results

[dabomb4eve]

Hi! It works again! I ran the resetroot.bat, and that seemed to fix the problem. Although, I think there may have been a user-related error (DOH!). I kept pressing the Admin button from XAMPP, but that loaded a CACHED phpMyAdmin page. I thought this was fishy, as I got a page when my Apache WASN'T running. So I started Apache once again, and reloaded the page. Voila!

Unfortunately, I don't know which of these two was the fix. Nevertheless, it is fixed.

Thank you very much!