00330-80000-00000-AA737-Admin-2018-12运行日志

分类
数据协解
更新时间
2018-12-13 12:00:06

Qampp Version: 2.7.1-2018-09-26 Microsoft Windows 10 专业版 10.0.10240

[1]2018-12-13 11:55:31:
Application 错误:Windows 无法加载可扩展计数器 DLL rdyboost。数据部分的前四个字节(DWORD)包含 Windows 错误代码。
Details: rdyboost4 - (338643)

[2]2018-12-13 11:58:12:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (338668)

[3]2018-12-13 11:58:12:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338667)

[4]2018-12-13 11:58:12:
Application 警告:Failed to open optimizer cost constant tables
For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to open optimizer cost constant tables
 - (338676)

[5]2018-12-13 11:58:12:
Application 警告:InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338675)

[6]2018-12-13 11:58:12:
Application 警告:Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened - (338670)

[7]2018-12-13 11:58:12:
Application 警告:InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338669)

[8]2018-12-13 11:58:13:
Application 警告:Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without themFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them - (338678)

[9]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338677)

[10]2018-12-13 11:58:13:
Application 错误:Can't open and lock privilege tables: Table 'mysql.servers' doesn't existFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist - (338681)

[11]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338680)

[12]2018-12-13 11:58:13:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (338685)

[13]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338684)

[14]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338683)

[15]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338682)

[16]2018-12-13 11:58:13:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (338688)

[17]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338687)

[18]2018-12-13 11:58:13:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (338686)

[19]2018-12-13 11:58:18:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (338693)

Cont:19; Cstr:9033

Qampp Version: 2.7.1-2018-09-26 Microsoft Windows 10 专业版 10.0.10240

[1]2018-12-11 11:29:27:
Application 错误:Windows 无法加载可扩展计数器 DLL rdyboost。数据部分的前四个字节(DWORD)包含 Windows 错误代码。
Details: rdyboost4 - (337845)

[2]2018-12-11 11:31:52:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (337872)

[3]2018-12-11 11:31:52:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337871)

[4]2018-12-11 11:31:52:
Application 警告:Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened - (337874)

[5]2018-12-11 11:31:52:
Application 警告:InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337873)

[6]2018-12-11 11:31:52:
Application 警告:Failed to open optimizer cost constant tables
For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to open optimizer cost constant tables
 - (337880)

[7]2018-12-11 11:31:52:
Application 警告:InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337879)

[8]2018-12-11 11:31:52:
Application 警告:Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without themFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them - (337882)

[9]2018-12-11 11:31:52:
Application 警告:InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337881)

[10]2018-12-11 11:31:53:
Application 错误:Can't open and lock privilege tables: Table 'mysql.servers' doesn't existFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist - (337885)

[11]2018-12-11 11:31:53:
Application 警告:InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337884)

[12]2018-12-11 11:31:53:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (337889)

[13]2018-12-11 11:31:53:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337888)

[14]2018-12-11 11:31:53:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337887)

[15]2018-12-11 11:31:53:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337886)

[16]2018-12-11 11:31:53:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (337892)

[17]2018-12-11 11:31:53:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337891)

[18]2018-12-11 11:31:53:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337890)

[19]2018-12-11 11:31:56:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (337897)

[20]2018-12-11 11:32:42:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `cjshw1`.`mc_yunyin_nav` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `cjshw1`.`mc_yunyin_nav` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337900)

[21]2018-12-11 11:32:42:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337899)

[22]2018-12-11 11:32:42:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `cjshw1`.`mc_cms_zhuanti` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `cjshw1`.`mc_cms_zhuanti` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337902)

[23]2018-12-11 11:32:42:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337901)

[24]2018-12-11 11:32:42:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `cjshw1`.`mc_yunyin_theme` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `cjshw1`.`mc_yunyin_theme` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337904)

[25]2018-12-11 11:32:42:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337903)

[26]2018-12-11 11:32:42:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `cjmall`.`ecjia_users` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `cjmall`.`ecjia_users` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337906)

[27]2018-12-11 11:32:42:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337905)

[28]2018-12-11 13:07:02:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: TQUERY.DLL,版本: 7.0.10240.16384,时间戳: 0x559f3a16
异常代码: 0xc0000005
错误偏移量: 0x0000000000064d2c
错误进程 ID: 0x260
错误应用程序启动时间: 0x01d4910f505e8616
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\system32\TQUERY.DLL
报告 ID: a1e06fd5-c1a0-4604-a4ae-894e1b211b66
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390aTQUERY.DLL7.0.10240.16384559f3a16c00000050000000000064d2c26001d4910f505e8616C:\Windows\system32\SearchIndexer.exeC:\Windows\system32\TQUERY.DLLa1e06fd5-c1a0-4604-a4ae-894e1b211b66 - (337958)

[29]2018-12-11 13:11:35:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: ntdll.dll,版本: 10.0.10240.16384,时间戳: 0x559f384f
异常代码: 0xc0000005
错误偏移量: 0x000000000002f222
错误进程 ID: 0x2a8c
错误应用程序启动时间: 0x01d4910fe64ba450
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\SYSTEM32\ntdll.dll
报告 ID: 882aec09-e4eb-47d0-b38d-800c194edc46
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390antdll.dll10.0.10240.16384559f384fc0000005000000000002f2222a8c01d4910fe64ba450C:\Windows\system32\SearchIndexer.exeC:\Windows\SYSTEM32\ntdll.dll882aec09-e4eb-47d0-b38d-800c194edc46 - (337966)

[30]2018-12-11 13:53:02:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: TQUERY.DLL,版本: 7.0.10240.16384,时间戳: 0x559f3a16
异常代码: 0xc0000005
错误偏移量: 0x0000000000064d2c
错误进程 ID: 0x37f4
错误应用程序启动时间: 0x01d49115bde99ae9
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\system32\TQUERY.DLL
报告 ID: 3558d8b6-921e-4bcb-a6df-4851def28e2d
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390aTQUERY.DLL7.0.10240.16384559f3a16c00000050000000000064d2c37f401d49115bde99ae9C:\Windows\system32\SearchIndexer.exeC:\Windows\system32\TQUERY.DLL3558d8b6-921e-4bcb-a6df-4851def28e2d - (338014)

[31]2018-12-11 13:57:46:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: KERNELBASE.dll,版本: 10.0.10240.16384,时间戳: 0x559f38c3
异常代码: 0xc0000005
错误偏移量: 0x0000000000049c50
错误进程 ID: 0x434c
错误应用程序启动时间: 0x01d4911657fda0cd
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\system32\KERNELBASE.dll
报告 ID: 8731d615-1162-4d63-b250-eb40c2c3c521
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390aKERNELBASE.dll10.0.10240.16384559f38c3c00000050000000000049c50434c01d4911657fda0cdC:\Windows\system32\SearchIndexer.exeC:\Windows\system32\KERNELBASE.dll8731d615-1162-4d63-b250-eb40c2c3c521 - (338022)

[32]2018-12-11 14:03:02:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: KERNELBASE.dll,版本: 10.0.10240.16384,时间戳: 0x559f38c3
异常代码: 0xc0000005
错误偏移量: 0x0000000000049c50
错误进程 ID: 0x2774
错误应用程序启动时间: 0x01d491171ae2da2f
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\system32\KERNELBASE.dll
报告 ID: 6f811d74-f536-425c-9016-cb8483f4a5e8
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390aKERNELBASE.dll10.0.10240.16384559f38c3c00000050000000000049c50277401d491171ae2da2fC:\Windows\system32\SearchIndexer.exeC:\Windows\system32\KERNELBASE.dll6f811d74-f536-425c-9016-cb8483f4a5e8 - (338037)

[33]2018-12-11 18:16:25:
Application 警告:具有指纹 70 04 3c 28 93 39 60 37 92 da 92 8f 73 f5 50 86 60 3f bf 27 的 本地系统 的证书将到期或已到期。
Details: 本地系统70 04 3c 28 93 39 60 37 92 da 92 8f 73 f5 50 86 60 3f bf 27 - (338127)

Cont:33; Cstr:17040

Qampp Version: 2.7.1-2018-09-26 Microsoft Windows 10 专业版 10.0.10240

[1]2018-12-10 15:24:35:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: elscore.dll,版本: 10.0.10240.16384,时间戳: 0x559f3872
异常代码: 0xc0000005
错误偏移量: 0x00000000000025c3
错误进程 ID: 0xf24
错误应用程序启动时间: 0x01d4905960211763
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\system32\elscore.dll
报告 ID: dc87e48a-7750-40a3-ba54-3623c49a3686
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390aelscore.dll10.0.10240.16384559f3872c000000500000000000025c3f2401d4905960211763C:\Windows\system32\SearchIndexer.exeC:\Windows\system32\elscore.dlldc87e48a-7750-40a3-ba54-3623c49a3686 - (336802)

[2]2018-12-10 15:24:49:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (336826)

[3]2018-12-10 15:24:49:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336825)

[4]2018-12-10 15:24:50:
Application 警告:Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened - (336828)

[5]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336827)

[6]2018-12-10 15:24:50:
Application 警告:Failed to open optimizer cost constant tables
For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to open optimizer cost constant tables
 - (336834)

[7]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336833)

[8]2018-12-10 15:24:50:
Application 警告:Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without themFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them - (336836)

[9]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336835)

[10]2018-12-10 15:24:50:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (336843)

[11]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336842)

[12]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336841)

[13]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336840)

[14]2018-12-10 15:24:50:
Application 错误:Can't open and lock privilege tables: Table 'mysql.servers' doesn't existFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist - (336839)

[15]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336838)

[16]2018-12-10 15:24:50:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (336846)

[17]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336845)

[18]2018-12-10 15:24:50:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336844)

[19]2018-12-10 15:24:54:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (336851)

[20]2018-12-10 15:25:38:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: ntdll.dll,版本: 10.0.10240.16384,时间戳: 0x559f384f
异常代码: 0xc0000005
错误偏移量: 0x000000000002f222
错误进程 ID: 0x3f50
错误应用程序启动时间: 0x01d49059856f3879
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\SYSTEM32\ntdll.dll
报告 ID: ea6d821c-7981-4d47-a9f7-ad3ed7566cf4
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390antdll.dll10.0.10240.16384559f384fc0000005000000000002f2223f5001d49059856f3879C:\Windows\system32\SearchIndexer.exeC:\Windows\SYSTEM32\ntdll.dllea6d821c-7981-4d47-a9f7-ad3ed7566cf4 - (336860)

[21]2018-12-10 15:30:04:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: ntdll.dll,版本: 10.0.10240.16384,时间戳: 0x559f384f
异常代码: 0xc0000005
错误偏移量: 0x000000000002aa1c
错误进程 ID: 0x1410
错误应用程序启动时间: 0x01d4905a23b15548
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\SYSTEM32\ntdll.dll
报告 ID: fd65d9d1-e3e6-454d-841f-f92d8f178423
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390antdll.dll10.0.10240.16384559f384fc0000005000000000002aa1c141001d4905a23b15548C:\Windows\system32\SearchIndexer.exeC:\Windows\SYSTEM32\ntdll.dllfd65d9d1-e3e6-454d-841f-f92d8f178423 - (336868)

[22]2018-12-10 15:30:35:
Application 错误:错误应用程序名称: SearchIndexer.exe,版本: 7.0.10240.16384,时间戳: 0x559f390a
错误模块名称: TQUERY.DLL,版本: 7.0.10240.16384,时间戳: 0x559f3a16
异常代码: 0xc0000005
错误偏移量: 0x0000000000064d2c
错误进程 ID: 0x1478
错误应用程序启动时间: 0x01d4905a36918c46
错误应用程序路径: C:\Windows\system32\SearchIndexer.exe
错误模块路径: C:\Windows\system32\TQUERY.DLL
报告 ID: 4b72d6b7-fb8b-44e1-b280-afb983fd49fc
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: SearchIndexer.exe7.0.10240.16384559f390aTQUERY.DLL7.0.10240.16384559f3a16c00000050000000000064d2c147801d4905a36918c46C:\Windows\system32\SearchIndexer.exeC:\Windows\system32\TQUERY.DLL4b72d6b7-fb8b-44e1-b280-afb983fd49fc - (336884)

[23]2018-12-10 15:33:26:
Application 警告:Child process [3588 - E:/UPUPW/UPUPW_ANK_W64/Modules/Memcached/memcached.exe -m 256 -l 127.0.0.1 -p 11211 -c 1920] finished with -1

[24]2018-12-10 15:33:34:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (336935)

[25]2018-12-10 15:33:34:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336934)

[26]2018-12-10 15:33:34:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (336954)

[27]2018-12-10 15:33:34:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336953)

[28]2018-12-10 15:33:34:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336952)

[29]2018-12-10 15:33:34:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (336951)

[30]2018-12-10 15:33:34:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336950)

[31]2018-12-10 15:33:34:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (336949)

[32]2018-12-10 15:33:35:
Application 警告:Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine

For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine

 - (336960)

[33]2018-12-10 15:34:13:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (336967)

[34]2018-12-10 15:35:03:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_token` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_token` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (336971)

[35]2018-12-10 15:35:03:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (336970)

[36]2018-12-10 15:35:31:
Application 警告:Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine

For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine

 - (337012)

[37]2018-12-10 15:35:32:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (337026)

[38]2018-12-10 15:35:32:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337025)

[39]2018-12-10 15:35:32:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (337045)

[40]2018-12-10 15:35:32:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337044)

[41]2018-12-10 15:35:32:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337043)

[42]2018-12-10 15:35:32:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (337042)

[43]2018-12-10 15:35:32:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337041)

[44]2018-12-10 15:35:32:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337040)

[45]2018-12-10 15:35:57:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (337053)

[46]2018-12-10 15:36:18:
Application 警告:Child process [20844 - E:/UPUPW/UPUPW_ANK_W64/Modules/Memcached/memcached.exe -m 256 -l 127.0.0.1 -p 11211 -c 1920] finished with -1

[47]2018-12-10 15:36:27:
Application 警告:Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine

For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine

 - (337087)

[48]2018-12-10 15:36:36:
Application 警告:Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened - (337115)

[49]2018-12-10 15:36:36:
Application 警告:InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337114)

[50]2018-12-10 15:36:36:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (337113)

[51]2018-12-10 15:36:36:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337112)

[52]2018-12-10 15:36:36:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (337132)

[53]2018-12-10 15:36:36:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337131)

[54]2018-12-10 15:36:36:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337130)

[55]2018-12-10 15:36:36:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (337129)

[56]2018-12-10 15:36:36:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337128)

[57]2018-12-10 15:36:36:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (337127)

[58]2018-12-10 15:37:17:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (337144)

[59]2018-12-10 15:37:33:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337147)

[60]2018-12-10 15:37:33:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337146)

[61]2018-12-10 15:37:42:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_token` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_token` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337149)

[62]2018-12-10 15:37:42:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337148)

[63]2018-12-10 15:37:43:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337151)

[64]2018-12-10 15:37:43:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337150)

[65]2018-12-10 15:37:43:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337153)

[66]2018-12-10 15:37:43:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337152)

[67]2018-12-10 15:37:49:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337157)

[68]2018-12-10 15:37:49:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member_cate` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member_cate` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337156)

[69]2018-12-10 15:37:49:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337155)

[70]2018-12-10 15:37:49:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337154)

[71]2018-12-10 15:38:21:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337159)

[72]2018-12-10 15:38:21:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337161)

[73]2018-12-10 15:38:21:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337160)

[74]2018-12-10 15:38:22:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_admin` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_admin` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337164)

[75]2018-12-10 15:38:22:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337163)

[76]2018-12-10 15:38:22:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337162)

[77]2018-12-10 15:38:22:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_admin_log` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_admin_log` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337168)

[78]2018-12-10 15:38:22:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337167)

[79]2018-12-10 15:38:22:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337166)

[80]2018-12-10 15:38:22:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337165)

[81]2018-12-10 15:38:22:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337169)

[82]2018-12-10 15:38:23:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_attachment` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_attachment` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337172)

[83]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337171)

[84]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337170)

[85]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337173)

[86]2018-12-10 15:38:23:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_auth_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_auth_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337176)

[87]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337175)

[88]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337174)

[89]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337177)

[90]2018-12-10 15:38:23:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_auth_group_access` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_auth_group_access` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337180)

[91]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337179)

[92]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337178)

[93]2018-12-10 15:38:23:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337181)

[94]2018-12-10 15:38:24:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_auth_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_auth_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337184)

[95]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337183)

[96]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337182)

[97]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337185)

[98]2018-12-10 15:38:24:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_category` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_category` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337188)

[99]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337187)

[100]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337186)

[101]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337189)

[102]2018-12-10 15:38:24:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_config` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_config` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337192)

[103]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337191)

[104]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337190)

[105]2018-12-10 15:38:24:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337193)

[106]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337195)

[107]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337194)

[108]2018-12-10 15:38:25:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_hezi` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_hezi` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337198)

[109]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337197)

[110]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337196)

[111]2018-12-10 15:38:25:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337202)

[112]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337201)

[113]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337200)

[114]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337199)

[115]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337203)

[116]2018-12-10 15:38:25:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member_cate` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_member_cate` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337206)

[117]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337205)

[118]2018-12-10 15:38:25:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337204)

[119]2018-12-10 15:38:29:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337221)

[120]2018-12-10 15:38:29:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_shebei` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_shebei` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337224)

[121]2018-12-10 15:38:29:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337223)

[122]2018-12-10 15:38:29:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337222)

[123]2018-12-10 15:38:29:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337225)

[124]2018-12-10 15:38:29:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337227)

[125]2018-12-10 15:38:29:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337226)

[126]2018-12-10 15:38:30:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_test` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_test` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337230)

[127]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337229)

[128]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337228)

[129]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337231)

[130]2018-12-10 15:38:30:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337234)

[131]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337233)

[132]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337232)

[133]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337235)

[134]2018-12-10 15:38:30:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337238)

[135]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337237)

[136]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337236)

[137]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337239)

[138]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337241)

[139]2018-12-10 15:38:30:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337240)

[140]2018-12-10 15:38:31:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337244)

[141]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337243)

[142]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337242)

[143]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337245)

[144]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337247)

[145]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337246)

[146]2018-12-10 15:38:31:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_token` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_user_token` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337250)

[147]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337249)

[148]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337248)

[149]2018-12-10 15:38:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337251)

[150]2018-12-10 15:38:32:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_version` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `zhsc`.`fa_version` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (337254)

[151]2018-12-10 15:38:32:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337253)

[152]2018-12-10 15:38:32:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337252)

[153]2018-12-10 15:38:41:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_hezi` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_hezi` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337256)

[154]2018-12-10 15:38:41:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337255)

[155]2018-12-10 15:38:51:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_auth_group_access` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_auth_group_access` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337258)

[156]2018-12-10 15:38:51:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337257)

[157]2018-12-10 15:39:01:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_member` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_member` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337260)

[158]2018-12-10 15:39:01:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337259)

[159]2018-12-10 15:39:11:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_attachment` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_attachment` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337262)

[160]2018-12-10 15:39:11:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337261)

[161]2018-12-10 15:39:21:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_member_cate` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_member_cate` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337264)

[162]2018-12-10 15:39:21:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337263)

[163]2018-12-10 15:39:31:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_auth_rule` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_auth_rule` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337266)

[164]2018-12-10 15:39:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337265)

[165]2018-12-10 15:39:41:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_test` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_test` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337268)

[166]2018-12-10 15:39:41:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337267)

[167]2018-12-10 15:39:51:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_admin_log` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_admin_log` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337270)

[168]2018-12-10 15:39:51:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337269)

[169]2018-12-10 15:40:01:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337272)

[170]2018-12-10 15:40:01:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337271)

[171]2018-12-10 15:40:11:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_category` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_category` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337274)

[172]2018-12-10 15:40:11:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337273)

[173]2018-12-10 15:40:21:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user_group` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user_group` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337276)

[174]2018-12-10 15:40:21:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337275)

[175]2018-12-10 15:40:31:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_auth_group` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_auth_group` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337278)

[176]2018-12-10 15:40:31:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337277)

[177]2018-12-10 15:40:41:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user_rule` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user_rule` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337280)

[178]2018-12-10 15:40:41:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337279)

[179]2018-12-10 15:40:51:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_config` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_config` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337282)

[180]2018-12-10 15:40:51:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337281)

[181]2018-12-10 15:41:01:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user_token` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_user_token` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337293)

[182]2018-12-10 15:41:01:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337292)

[183]2018-12-10 15:41:11:
Application 警告:InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_admin` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Recalculation of persistent statistics requested for table `zhsc`.`fa_admin` but the required persistent statistics storage is not present or is corrupted. Using transient stats instead - (337295)

[184]2018-12-10 15:41:11:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (337294)

[185]2018-12-10 16:11:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337306)

[186]2018-12-10 16:11:00:
Application 错误:svchost (2016) SRUJet: 系统错误 112 (0x00000070): "磁盘空间不足。 " 发生 0.000 秒后,在文件 "C:\Windows\system32\SRU\SRUtmp.log" 中偏移量 0 (0x0000000000000000) 写入 65536 (0x00010000) 字节的尝试失败。写入操作将失败,并出现错误 -1808 (0xfffff8f0)。如果此错误持续存在,文件可能会被损坏,并可能需要从以前的备份中还原。
Details: svchost2016SRUJet: C:\Windows\system32\SRU\SRUtmp.log0 (0x0000000000000000)65536 (0x00010000)-1808 (0xfffff8f0)112 (0x00000070)磁盘空间不足。 0.000 - (337305)

[187]2018-12-10 16:12:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337311)

[188]2018-12-10 16:12:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337310)

[189]2018-12-10 16:12:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337309)

[190]2018-12-10 16:11:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337308)

[191]2018-12-10 16:11:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337307)

[192]2018-12-10 16:13:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337313)

[193]2018-12-10 16:13:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337312)

[194]2018-12-10 16:14:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337316)

[195]2018-12-10 16:14:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337315)

[196]2018-12-10 16:13:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337314)

[197]2018-12-10 16:15:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337319)

[198]2018-12-10 16:15:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337318)

[199]2018-12-10 16:14:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337317)

[200]2018-12-10 16:16:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337323)

[201]2018-12-10 16:16:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337322)

[202]2018-12-10 16:16:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337321)

[203]2018-12-10 16:15:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337320)

[204]2018-12-10 16:17:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337324)

[205]2018-12-10 16:18:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337329)

[206]2018-12-10 16:18:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337328)

[207]2018-12-10 16:18:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337327)

[208]2018-12-10 16:17:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337326)

[209]2018-12-10 16:17:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337325)

[210]2018-12-10 16:19:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337332)

[211]2018-12-10 16:19:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337331)

[212]2018-12-10 16:19:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337330)

[213]2018-12-10 16:20:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337334)

[214]2018-12-10 16:20:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337333)

[215]2018-12-10 16:21:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337337)

[216]2018-12-10 16:21:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337336)

[217]2018-12-10 16:20:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337335)

[218]2018-12-10 16:22:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337341)

[219]2018-12-10 16:22:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337340)

[220]2018-12-10 16:22:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337339)

[221]2018-12-10 16:21:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337338)

[222]2018-12-10 16:23:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337343)

[223]2018-12-10 16:23:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337342)

[224]2018-12-10 16:24:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337347)

[225]2018-12-10 16:24:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337346)

[226]2018-12-10 16:24:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337345)

[227]2018-12-10 16:23:00:
Application 错误:svchost (2016) SRUJet: 无法创建新的日志文件,因为数据库无法写入日志驱动器。该驱动器可能为只读、磁盘空间不足、配置错误或已损坏。错误 -529。
Details: svchost2016SRUJet: -529 - (337344)

Cont:227; Cstr:86834

Qampp Version: 2.7.1-2018-09-26 Microsoft Windows 10 专业版 10.0.10240

[1]2018-12-04 10:50:16:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (335227)

[2]2018-12-04 10:50:16:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335226)

[3]2018-12-04 10:50:16:
Application 警告:Failed to open optimizer cost constant tables
For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to open optimizer cost constant tables
 - (335235)

[4]2018-12-04 10:50:16:
Application 警告:InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335234)

[5]2018-12-04 10:50:16:
Application 警告:Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened - (335229)

[6]2018-12-04 10:50:16:
Application 警告:InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335228)

[7]2018-12-04 10:50:17:
Application 警告:Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without themFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them - (335237)

[8]2018-12-04 10:50:17:
Application 警告:InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335236)

[9]2018-12-04 10:50:17:
Application 错误:Can't open and lock privilege tables: Table 'mysql.servers' doesn't existFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist - (335239)

[10]2018-12-04 10:50:17:
Application 警告:InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335238)

[11]2018-12-04 10:50:18:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (335244)

[12]2018-12-04 10:50:18:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335243)

[13]2018-12-04 10:50:18:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335242)

[14]2018-12-04 10:50:18:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335241)

[15]2018-12-04 10:50:19:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (335248)

[16]2018-12-04 10:50:18:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (335247)

[17]2018-12-04 10:50:18:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335246)

[18]2018-12-04 10:50:18:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (335245)

[19]2018-12-04 10:51:25:
Application 错误:搜索服务已在索引{id=4810 - base\appmodel\search\search\ytrip\common\util\jetutil.cpp (240)}中检测到损坏的数据文件。该服务将尝试通过重建索引来自动更正此问题。

详细信息:
	 0x8e5e0713 (0x8e5e0713)

Details: 

详细信息:
	 0x8e5e0713 (0x8e5e0713)
4810 - base\appmodel\search\search\ytrip\common\util\jetutil.cpp (240) - (335257)

[20]2018-12-04 10:51:25:
Application 错误:无法初始化插件管理器 <Search.TripoliIndexer>。

上下文: Windows 应用程序

详细信息:
	(HRESULT : 0x8e5e0713) (0x8e5e0713)

Details: 

上下文: Windows 应用程序

详细信息:
	(HRESULT : 0x8e5e0713) (0x8e5e0713)
Search.TripoliIndexer - (335260)

[21]2018-12-04 10:51:25:
Application 错误:Windows Search 服务已停止,因为索引器有问题: The catalog is corrupt。

详细信息:
	内容索引编录已损坏。   0xc0041801 (0xc0041801)

Details: 

详细信息:
	内容索引编录已损坏。   0xc0041801 (0xc0041801)
The catalog is corrupt - (335258)

[22]2018-12-04 10:51:25:
Application 错误:无法初始化索引。

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)

Details: 

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)
 - (335264)

[23]2018-12-04 10:51:25:
Application 错误:无法初始化应用程序。

上下文: Windows 应用程序

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)

Details: 

上下文: Windows 应用程序

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)
 - (335263)

[24]2018-12-04 10:51:25:
Application 错误:无法初始化 Gatherer 对象。

上下文: Windows 应用程序,SystemIndex 编录

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)

Details: 

上下文: Windows 应用程序,SystemIndex 编录

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)
 - (335262)

[25]2018-12-04 10:51:25:
Application 错误:无法初始化 <Search.TripoliIndexer> 中的插件。

上下文: Windows 应用程序,SystemIndex 编录

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)

Details: 

上下文: Windows 应用程序,SystemIndex 编录

详细信息:
	找不到指定的对象。请指定一个已有对象的名称。  (HRESULT : 0x80040d06) (0x80040d06)
Search.TripoliIndexer - (335261)

[26]2018-12-04 10:52:37:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_admin` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_admin` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (335268)

[27]2018-12-04 10:52:37:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (335267)

[28]2018-12-04 10:52:37:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_admin_log` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_admin_log` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (335270)

[29]2018-12-04 10:52:37:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (335269)

[30]2018-12-04 10:52:37:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (335273)

[31]2018-12-04 10:52:37:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_auth_group_access` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_auth_group_access` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (335272)

[32]2018-12-04 10:52:37:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (335271)

[33]2018-12-04 10:52:37:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_auth_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_auth_rule` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (335276)

[34]2018-12-04 10:52:37:
Application 错误:InnoDB: Table `mysql`.`innodb_table_stats` not found.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Table `mysql`.`innodb_table_stats` not found - (335275)

[35]2018-12-04 10:52:37:
Application 错误:InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_auth_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Fetch of persistent statistics requested for table `xiaoqu`.`fa_auth_group` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead - (335274)

Cont:35; Cstr:16021

Qampp Version: 2.7.1-2018-09-26 Microsoft Windows 10 专业版 10.0.10240

[1]2018-12-04 10:32:29:
Application 错误:Can't open the mysql.plugin table. Please run mysql_upgrade to create it.For more information, see Help and Support Center at http://www.mysql.com
Details: Can't open the mysql.plugin table. Please run mysql_upgrade to create it - (334897)

[2]2018-12-04 10:32:29:
Application 警告:InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334896)

[3]2018-12-04 10:32:29:
Application 警告:Failed to open optimizer cost constant tables
For more information, see Help and Support Center at http://www.mysql.com
Details: Failed to open optimizer cost constant tables
 - (334905)

[4]2018-12-04 10:32:29:
Application 警告:InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334904)

[5]2018-12-04 10:32:29:
Application 警告:Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened - (334899)

[6]2018-12-04 10:32:29:
Application 警告:InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334898)

[7]2018-12-04 10:32:30:
Application 警告:Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without themFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them - (334909)

[8]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334908)

[9]2018-12-04 10:32:30:
Application 错误:Can't open and lock privilege tables: Table 'mysql.servers' doesn't existFor more information, see Help and Support Center at http://www.mysql.com
Details: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist - (334912)

[10]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334911)

[11]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334914)

[12]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334913)

[13]2018-12-04 10:32:30:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened - (334916)

[14]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334915)

[15]2018-12-04 10:32:30:
Application 警告:Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.For more information, see Help and Support Center at http://www.mysql.com
Details: Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened - (334919)

[16]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334918)

[17]2018-12-04 10:32:30:
Application 警告:InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue - (334917)

[18]2018-12-04 10:32:37:
Application 错误:The Apache service named  reported the following error:
>>> AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist
Details: The Apache service namedreported the following error:
>>>AH00112: Warning: DocumentRoot [E:/M_PROJECT/HuaDianE/public] does not exist - (334924)

Cont:18; Cstr:8832

腾讯云 / 腾讯AI / 腾讯开源 / 南沙新区 / 信用
分享工作室[粤ICP备16004795号-2] Date:2019-07-15 21:08:27(UTC) RunTime:0.019