MySql: Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.

To resolve this error, please go into the following location:
C:\Documents and Settings\All Users\Application Data\MySQL\MySQL Server 5.1\Data

and delete “ib_logfile0″ and “ib_logfile1″.

Then go to Services and start your MySql. It will resolve the error and start you MySql.
Why: According to my search: Open the my.ini file and check the InnoDB variables’s size. When above file exides the mentioned size it will prompt this(“Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.”) error.

Regards,

Vijay Modi

Advertisements

About Vijay Modi

Having 12+ years of experience in web application development. Expertise in various domains like E-Commerce, E-Learning, Insurance. I have expertise in web application development, window application development, Performance improvement, bug fixing etc. I am believing in quality work and achieving deadlines. Also like to work on new technologies and quick learner.
This entry was posted in Uncategorized and tagged . Bookmark the permalink.

34 Responses to MySql: Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.

  1. James Modi says:

    Hi Dude

    jigarchaudhari.wordpress.com

  2. Mark says:

    You are AWESOME!! I have searched for over an hour on MySQL.com and other sites. I’ve edited the registry, uninstalled/reinstalled, change admin passwords, added a local admin account, all to no avail. Your simple solution worked perfectly!!!

    Thanks!!!

    Mark

  3. Nilesh says:

    Hi Vijay,
    jigarchaudhari.wordpress.com
    Is this our jigar chaudhari’s worpress blog from patan. 🙂

    Gr8 work man.. your site is very good.

  4. pankaj Joshi says:

    Hey Great solution man , it works!!!

  5. Yaroukh says:

    THANK YOU VERY MICH SIR
    oh how i hate this db 😦

  6. Volkan says:

    [mysqld]
    tmpdir=C:/temp

    The C:\temp directory must exist and have sufficient space for the MySQL server to write to

  7. mpcmanch says:

    THANKS SO MUCH! I was going nutz

  8. Smon says:

    Been having the exact same problem, except that deleting the two mentioned files doesn’t seem to do anything at all.

    • Jon Spencer says:

      These people apparently are using Windows. When I try this on Linux, the problem persists. I have two different Linux versions (RHEL 5.5 and Centos 6.3) with exactly the same MySQL distribution [
      MySQL-client-advanced-5.5.28-1.rhel4.x86_64.rpm
      MySQL-devel-advanced-5.5.28-1.rhel4.x86_64.rpm
      MySQL-server-advanced-5.5.28-1.rhel4.x86_64.rpm
      ]

      The server comes up on RHEL but it does not on Centos. I have deleted the ib_logfile* files on both systems. This does not change the behavior.

  9. Ranjan says:

    thanks vijay, it works for me..i did so many things but i got the answer from u only…….thnk u very much

  10. Jane Fonda says:

    deleting those files doesn’t make a difference

  11. Brian says:

    It worked for me. Saved a lot of time, thanks.

  12. Great, I did not know about that up to now. Thankz!

  13. Bruno says:

    Thank you so much man !
    I’ve had this error monday morning and thank to you I fixed it before any customer can notice our server was down.

  14. Alex says:

    Thank you so much!!!

  15. Sudarpo says:

    Spot on..
    You are right on this.
    Thank you !!!

  16. eramue says:

    I had the same error and in my situation in addition to the mentioned log files I also had to delete ibdata1 file in the same directory.
    And then I could restart the server.

  17. Michael Mior says:

    If you don’t want to lose data, instead execute the MySQL command set global innodb_fast_shutdown=0; before you shut down the server. When you shut down, this should solve the problem without causing you to lose data. Then you can reconfigure and restart.

  18. rafael sanzio says:

    Great solution and explanation, work for me fine; upgrading form mysql 5.1.47 to 5.5.9
    Thanks you very much

  19. Ho says:

    Great solution, it work!!!
    Thank you very much.

  20. khalid mehmood awan says:

    That helped for MySQL 5.5 too.

  21. Worked for me on 5.5! Huge props.

  22. Joe says:

    Thank you for this!

  23. Majid Nazeer says:

    Thanks a lot

  24. Ben says:

    Saved me a lot of time. Great post! Thanks!

  25. Ken says:

    I wish I found your post six hours ago and I wouldn’t have had wasted half a day uninstalling and reinstalling MySQL trying to figure out what the problem was.

    Thank you very much for this solution!

  26. steven yip says:

    Thanks my friend. This really works. I was trying to reinstall mysql 5.5 on my windows 7 machine, and somehow it just can’t start.

    What I did was go to
    C:\ProgramData\MySQL\MySQL Server 5.5\data

    to find those log files, and then delete as you stated.

    Then I restarted, and it works.

    I hope this message helps anyone with reinstalling mysql on windows 7.

    Cheers

    Steven Yip

  27. Pat G says:

    You rock! Thanks for the tip – had this same problem with MySQL 5.5 on Windows 2008 R2

  28. sakthi says:

    Thanks …. It works…

  29. SK Imdad says:

    Great!
    It resolved my issue.

  30. 1MoreAnonymous says:

    Thank you, save me a starting headache !

  31. Rida Shamasneh says:

    Thanks A lot man
    God bless you 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s