Remember the step 2
On step 2 (from moving from MySQL to 5.6.10) I wrote about the important role of the file my.ini, the file that includes all configutarios. Copying this file and including it in our backup has a justification. Next, in step 4 you could verify that the server is up and running, although the thrth is that I would like to move the path to our database to another directory. Let’s modify some options in the config file.
Modifying server configuration
First of all, you need to stop the server just writting NET STOP mysql56 on a MS-DOS console:
Next, is open a file browser and navigate to the path where the my.ini file is, in my case C:\Documents and Settings\All Users\Datos de programa\MySQL\MySQL Server 5.6.
Before keep on, I recommend you to copy the original my.ini file (because I have test it and it works!, step 4).
The old file my.ini ewas located in C:\Documents and Settings\All Users\Datos de programa\MySQL\MySQL Server 5.5. Let’s copy to the MySQL 5.6 path.
Now, start the server typing NET START mysql56.
It could be perfect if it worked, but …. that’s not the end I desired. I have an extra work to do, because I received an #error (with almost no explanations!!) and the server doesn’t start. So, it’s time to work with my.ini file.
In fact, you can read in the official documentation that several parameters had changed from MySQL 5.5 server to version 5.6, and maybe one of those changes is affecting our server.
Experienced users will know how to configure my.ini files dependeing on the server characteristics, but for a novice, the easy way is to modify the initial my.ini file, changing one parameter at a time. Stop and start. As I am doing!
The thruth is that the only modification I am doing is the path to databases, the datadir parameter.
I copied the data dir (the same generated by the MySQL 5.6 installer) to a new path (it doesn’t matter another unit or directory), but the error is still there! Let’s check that modifying the default path (datadir), the error arises!!
In my personal opinion, it’s very frustrating that this errors occurs at this MySQL versions, but … that’s the way it is. So, lets start again with the originial MySQL 5.6.10 my.ini file (we know with this file, the server starts!), and store it on a safe location … maybe I need it in the future!
That’s not the only case that arise error 1067 whan trying to start a MySQL server, but it’s what had happend to me! I am using Windows XP SP3, but I also tried on Windows 7 x64 having the same error!!.
To find a solution, maybe I need to study the MySQL log file.
Be careful when moving a MySQL server
I want to state that doing a migrationg process on a production MySQL server can become in a titatic task if you get an error as described here, so I encourage you to try this updates on test server or in virtual machines, before proceeding on a production MySQL server.
How can you solve error 1067?
Well, … that’s the topic of step 6.
Have a nice day!.