错误InnoDB:Attemptedtoopenapreviouslyopenedtablespace.

启用MySql服务的时候出现“windows无法启动mysql服务（位于本地计算机上。错误1067：进程意外终止）”,看看mysql服务并没有其他的依赖安系啊，于是突然想到进系统日志看看。果然发现非常多MySql的非常多错误，最终找到问题所在。

没错，查看系统日志就可以了。

可以看到，系统显示无法识别的变量“default-character-set=utf-8”，直接百度，将配置文件my.ini里[mysqld]下的“default-character-set=utf-8”改为“character-set-server=utf-8”，简单粗暴解决问题。

再深入一点（再百度一下），原来起因是我在安装了数据库后，重新配置了数据库的编码，在配置文件里添加了default-character-set=utf-8，但是由于MYSQL版本限制，我的MYSQL版本（5.5）要使用“character-set-server”进行编码配置，而不能使用“default-character-set”。

2019-02-14 13:48:22 760 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace isaactest/wp_usermeta uses space ID: 2 at filepath: .\isaactest\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
 

出现这个问题好几次了，每次的解决问题都是重新弄下Mysql.

我用的是XAMPP 1.83,今天终于找到解决办法了

在D:\xampp\mysql\bin下面的my.ini中添加

innodb_force_recovery = 1

OK,谢谢。