Troubleshooting caused by MySQL reinstallation in Windows

 

Solved the problem of plugin 'innodb' init function returned error and the security setting password login problem of error1405. I personally think the key point is to delete C: /Documents and Settings/all users/Application Data/MySQL Server 5.1, but look at this post can try to only this step can solve the problem, of course, there is also the deletion of MySQL installation directory in the residual file steps is also more important cite from: http://forums.mysql.com/read.php? 250105, # msg-250105Re: plugin 'innodb' init function returned error. Posted: Richard Lee() Date: February 27,200 9 AM

 

For Windows OS:

OK, I struggled with this for ages. There are varous partial fixes that did not fix it for me on the web, but in the end the following worked:

If you 've installed it, then uninstall (an earlier version that had been removed coshould have left crap that is causing an issue, so best to start off clean). Do this as follows:
-Add/Remove Programs and remove MySQL.
-Delete the programs file/MySQL folder (it gets left behind)
-Delete the data file (where ever you stored it) #:/MySQL datafiles> This is assuming you have no data to as yet to worry about !!!!
-Run regedit and delete all the MySQL keys (search and F3) and the half a dozen or so clsids that COE up with just a single non-defailt key for MySQL. you can leave Adobe/keys that mention it if you have Dreamweaver etc. as allways back up you Registry first before choppig it!

OK. Now run te install and go through the config wizard until it fails at the start up. Then close it.

Now open up services and open MySQL properties-I set it to run under the Administrator account rather than system/another to ensure it had permissions.

Next, go to your new MySQL datafile and delete 'ibdata1 '.
Then go to 'C: /Documents and Settings/all users/Application Data/MySQL Server 5.1/data' and delete all tje 'ib _ logfile' prefixed files (shocould be 0 and 1) -useful to notice. err log here to which is a text file.

Then go back to services and manually start it and all shoshould be fine.

Hopefully I have saved you a few hourse peeing around with Windows-mysql devs, about time this bug was fixed eh? Been hanging around und a long while now and the Web is chok full of unanswered or half answered requests for help. Remember-some of us have no choice but to use Windows.