There must be some file(s) in the XAMPP installation that the MySQL server uses to find the various databases and tables. Simply the message that the table does not exist in the engine.
I did add the user account in the new XAMPP installation that has the same name, password and privileges as used in the old installation, so it is not an issue with access privileges. Running phpMyAdmin shows that the custom databases and the tables are visible, but when I try to access any of them, there is an error that the table does not exist in the engine. I dug out the files from a Time Machine backup, manually added them to the xamppfiles/var/mysql directory and changed permissions to match those of the databases included with the XAMPP package (chmod 770 on the custom database directories in xamppfiles/var/mysql). I have tried to completely remove the remaining xamppfiles folder before a reinstall of XAMPP, and that works, but of course the databases I have created are not available anymore. Running a backup after every single database change is not feasible and should not be required IMHO. The obvious restore method for a MySQL table or database is of course running the restore by importing an earlier SQL backup from phpMyAdmin, but you need to have that backup, and that is impossible to create after the MySQL server dies and refuses to restart. The problem is that the new installation does not automatically pick up the databases that were created in the old installation, even if they are in the same physical location on my disk. In the end, the only working solution was to re-install XAMPP. If it specifies a missing default folder, you should create a new default file.I have experienced many problems with MySQL, where the server simply refuses to restart after something has happened (not sure which events make it crash). Go to the MySQL * bin* and run the following command: mysqld -defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\my.ini" -standalone -console Use the steps in this section to check for this missing default files:
It’s possible that default files are missing. You might need to verify that the Network Service has the proper permissions. Paste them onto the current my.ini to resolve this issue. If you have a backup of the original my.ini file, you can copy the contents of this file and manually
The line specifies that each file must have a unique ID, which then appends the Log in as root and reinstall the MySQL service by running the following commands: mysqld -installĬertain versions of MySQL add invalid hex values at the beginning of the my.ini configuration file.ĭeleting the first three hex values using a hex editor should resolve this issue. You need to log in as root or use sudo -i to run this command.
Restart the MySQL service by running the following command: mysqld -initialize Attempt the solutions in the order of the following sections. The solution varies depending on your version of MySQL. Some services stop automatically if they are not in use by other services or programs.
This article describes the process of resolving the following MySQL® for Windows® error: MySQL service on local computer started and then stopped.