When I start WampServer 2.4 the MySQL instance does not start.
One day it works fine, the next day there was this issue.
I have tried restarting all services, include "innodb_force_recovery = 1" in my.ini and I removed the skip-innodb also in my.ini.
I get the following error:
2014-04-28 16:06:51 4408 [Note] Plugin 'FEDERATED' is disabled.
2014-04-28 16:06:51 13dc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-04-28 16:06:51 4408 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-28 16:06:51 4408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-04-28 16:06:51 4408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-28 16:06:51 4408 [Note] InnoDB: Not using CPU crc32 instructions
2014-04-28 16:06:51 4408 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-04-28 16:06:51 4408 [Note] InnoDB: Completed initialization of buffer pool
2014-04-28 16:06:51 13dc InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2014-04-28 16:06:51 13dc InnoDB: File name C:\mysql\data\ibdata1
2014-04-28 16:06:51 13dc InnoDB: File operation call: 'create' returned OS error 103.
2014-04-28 16:06:51 13dc InnoDB: Cannot continue operation.
I have searched for both Operating system error number 3 and OS error 103 and I cannot find an answer for the problem.
I got the ibdata1 file, but since I got data in my databases, I do not want to delete it and let WampServer recreate it.
It is not possible to log on to phpMyAdmin, but I can access the Localhost.
Also, I am pretty sure I have not changed anything in the folder structure.
Resolved
I just wanted to let everyone know, that I don't have this problem any longer.
The problem was caused by enabling InnoDB.
The problem disappeared wheh I reinstalled WampServer, and after that I was able to enable InnoDB with no problem at all.