[Freszh]

Hi guys, I recently just made a test server and yeah I installed XAMPP and Navicat for MYSQL as it was needed to run the database through there, so i could just start XAMPP and everything was fine, I was trying out some things and added some houses and dynamic doors, so I decided to edit something in the gamemode script and then I closed XAMPP and Navicat for MYSQL. But when I was done, I tried to run XAMPP again and I received the following error:

15:18:51 [mysql] Error: MySQL shutdown unexpectedly.
15:18:51 [mysql] This may be due to a blocked port, missing dependencies,
15:18:51 [mysql] improper privileges, a crash, or a shutdown by another method.
15:18:51 [mysql] Press the Logs button to view error logs and check
15:18:51 [mysql] the Windows Event Viewer for more clues
15:18:51 [mysql] If you need more help, copy and post this
15:18:51 [mysql] entire log window on the forums

I clicked logs and this is what I received:

2013-10-20 15:18:48 5868 [Note] Plugin 'FEDERATED' is disabled.
2013-10-20 15:18:48 f80 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.
2013-10-20 15:18:48 5868 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-20 15:18:48 5868 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-20 15:18:48 5868 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-20 15:18:48 5868 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-20 15:18:48 5868 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-20 15:18:48 5868 [Note] InnoDB: Completed initialization of buffer pool
2013-10-20 15:18:48 5868 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-20 15:18:48 5868 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1982376 in the ib_logfiles!
2013-10-20 15:18:48 5868 [Note] InnoDB: Database was not shutdown normally!
2013-10-20 15:18:48 5868 [Note] InnoDB: Starting crash recovery.
2013-10-20 15:18:48 5868 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-20 15:18:48 5868 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace ngrp_main/accounts which uses space ID: 1 at filepath: .\ngrp_main\accounts.ibd
InnoDB: Error: could not open single-table tablespace file .\ngrp_main\accounts.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-20 15:18:50 5604 [Note] Plugin 'FEDERATED' is disabled.
2013-10-20 15:18:50 1a50 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.
2013-10-20 15:18:50 5604 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-20 15:18:50 5604 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-20 15:18:50 5604 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-20 15:18:50 5604 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-20 15:18:50 5604 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-20 15:18:50 5604 [Note] InnoDB: Completed initialization of buffer pool
2013-10-20 15:18:50 5604 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-20 15:18:51 5604 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1982376 in the ib_logfiles!
2013-10-20 15:18:51 5604 [Note] InnoDB: Database was not shutdown normally!
2013-10-20 15:18:51 5604 [Note] InnoDB: Starting crash recovery.
2013-10-20 15:18:51 5604 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-20 15:18:51 5604 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace ngrp_main/accounts which uses space ID: 1 at filepath: .\ngrp_main\accounts.ibd
InnoDB: Error: could not open single-table tablespace file .\ngrp_main\accounts.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Does anyone know how to fix this?
Please reply or add me on skype =[[
Skype: justin-ijjigunz

[GWMPT]

I just know that you should, next time, use [code ][/ code] tags.
And, try to reinstall? lol.