00328-10000-00001-AA007-Administrator-2018-12运行日志

分类
数据协解
更新时间
2018-12-07 13:43:07

Qampp Version: 2.7.0-2018-04-28 Microsoft Windows 10 教育版 10.0.17763

[1]2018-12-07 11:42:04:
Application 警告:
Details: phpMyAdmin[7936]user denied: root (no-activity) from 127.0.0.1 - (4687)

[2]2018-12-07 12:02:26:
Application 错误:错误应用程序名称: kuaiyatpopxxrl.exe,版本: 1.0.0.1,时间戳: 0x5bc730cd
错误模块名称: unknown,版本: 0.0.0.0,时间戳: 0x00000000
异常代码: 0xc0000005
错误偏移量: 0x0793d220
错误进程 ID: 0x1db8
错误应用程序启动时间: 0x01d48de1a5302a9d
错误应用程序路径: C:\Users\Administrator\AppData\Roaming\kuaiya\12all-allall\kuaiyatpopxxrl.exe
错误模块路径: unknown
报告 ID: ca86345f-4243-4a38-a91e-c1d336fd7167
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: kuaiyatpopxxrl.exe1.0.0.15bc730cdunknown0.0.0.000000000c00000050793d2201db801d48de1a5302a9dC:\Users\Administrator\AppData\Roaming\kuaiya\12all-allall\kuaiyatpopxxrl.exeunknownca86345f-4243-4a38-a91e-c1d336fd7167 - (4688)

[3]2018-12-07 12:02:32:
Application 错误:错误应用程序名称: kuaiyatipsylkx.exe,版本: 1.0.8.8,时间戳: 0x5bbb103c
错误模块名称: unknown,版本: 0.0.0.0,时间戳: 0x00000000
异常代码: 0xc0000005
错误偏移量: 0x075681e8
错误进程 ID: 0x3138
错误应用程序启动时间: 0x01d48de1a5135a86
错误应用程序路径: C:\Users\Administrator\AppData\Roaming\aprilmarch\FsepMallallttxs\kuaiyatipsylkx.exe
错误模块路径: unknown
报告 ID: 1bcb2e61-3a60-4314-9d9a-c0ae3d73c71c
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: kuaiyatipsylkx.exe1.0.8.85bbb103cunknown0.0.0.000000000c0000005075681e8313801d48de1a5135a86C:\Users\Administrator\AppData\Roaming\aprilmarch\FsepMallallttxs\kuaiyatipsylkx.exeunknown1bcb2e61-3a60-4314-9d9a-c0ae3d73c71c - (4690)

Cont:3; Cstr:1772

Qampp Version: 2.7.0-2018-04-28 Microsoft Windows 10 教育版 10.0.17763

[1]2018-12-06 17:06:49:
Application 错误:卷影复制服务错误: 查询 IVssWriterCallback 接口时的错误。hr = 0x80070005, 拒绝访问。
。 此错误通常是由编写器或请求方过程中的错误安全设置造成的。 

操作:
   正在搜集写入程序数据

上下文:
   写入程序类 ID: {e8132975-6f93-4464-a53e-1050253ae220}
   写入程序名称: System Writer
   写入程序实例 ID: {1589a0cb-2370-4a0e-b085-c3ed91cdabbe}
Details: 0x80070005, 拒绝访问。


操作:
   正在搜集写入程序数据

上下文:
   写入程序类 ID: {e8132975-6f93-4464-a53e-1050253ae220}
   写入程序名称: System Writer
   写入程序实例 ID: {1589a0cb-2370-4a0e-b085-c3ed91cdabbe} - (4655)

[2]2018-12-06 17:06:49:
Application 错误:卷影复制服务错误: 调用程序 IVssAsrWriterBackup::GetDiskComponents 时的意外错误。hr = 0x8007085a, 工作站服务没有启动。
。 

操作:
   OnIdentify 事件
   正在搜集写入程序数据

上下文:
   执行上下文: ASR Writer
   写入程序类 ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   写入程序名称: ASR Writer
   写入程序实例 ID: {6f82bc44-ed1e-425a-99c1-2147cb1fad86}
Details: IVssAsrWriterBackup::GetDiskComponents0x8007085a, 工作站服务没有启动。


操作:
   OnIdentify 事件
   正在搜集写入程序数据

上下文:
   执行上下文: ASR Writer
   写入程序类 ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   写入程序名称: ASR Writer
   写入程序实例 ID: {6f82bc44-ed1e-425a-99c1-2147cb1fad86} - (4656)

[3]2018-12-06 17:06:50:
Application 警告:卷影复制服务警告: ASR writer Error 0x8007085a。hr = 0x00000000, 操作成功完成。
。 

操作:
   PrepareForBackup 事件

上下文:
   执行上下文: ASR Writer
   执行上下文: Writer
   写入程序类 ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   写入程序名称: ASR Writer
   写入程序实例 ID: {6f82bc44-ed1e-425a-99c1-2147cb1fad86}

错误特定详细信息:
   ASR Writer: 工作站服务没有启动。 (0x8007085A)
Details: ASR writer Error 0x8007085a0x00000000, 操作成功完成。


操作:
   PrepareForBackup 事件

上下文:
   执行上下文: ASR Writer
   执行上下文: Writer
   写入程序类 ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   写入程序名称: ASR Writer
   写入程序实例 ID: {6f82bc44-ed1e-425a-99c1-2147cb1fad86}

错误特定详细信息:
   ASR Writer: 工作站服务没有启动。 (0x8007085A) - (4658)

[4]2018-12-06 17:06:50:
Application 错误:卷影复制服务错误: 调用程序 Check OnIdentifyError 时的意外错误。hr = 0x8007085a, 工作站服务没有启动。
。 

操作:
   PrepareForBackup 事件

上下文:
   执行上下文: ASR Writer
   执行上下文: Writer
   写入程序类 ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   写入程序名称: ASR Writer
   写入程序实例 ID: {6f82bc44-ed1e-425a-99c1-2147cb1fad86}

错误特定详细信息:
   ASR Writer: 工作站服务没有启动。 (0x8007085A)
Details: Check OnIdentifyError0x8007085a, 工作站服务没有启动。


操作:
   PrepareForBackup 事件

上下文:
   执行上下文: ASR Writer
   执行上下文: Writer
   写入程序类 ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   写入程序名称: ASR Writer
   写入程序实例 ID: {6f82bc44-ed1e-425a-99c1-2147cb1fad86}

错误特定详细信息:
   ASR Writer: 工作站服务没有启动。 (0x8007085A) - (4657)

Cont:4; Cstr:3477

Qampp Version: 2.7.0-2018-04-28 Microsoft Windows 10 教育版 10.0.17763

[1]2018-12-06 10:55:37:
Application 警告:InnoDB: Resizing redo log from 2*3072 to 2*512 pages, LSN=2524914For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Resizing redo log from 2*3072 to 2*512 pages, LSN=2524914 - (4100)

[2]2018-12-06 10:55:37:
Application 警告:InnoDB: Starting to delete and rewrite log files.For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: Starting to delete and rewrite log files - (4101)

[3]2018-12-06 10:55:37:
Application 警告:InnoDB: New log files created, LSN=2524914For more information, see Help and Support Center at http://www.mysql.com
Details: InnoDB: New log files created, LSN=2524914 - (4105)

[4]2018-12-06 10:55:44:
Application 错误:The Apache service named  reported the following error:
>>> AH00015: Unable to open logs
Details: The Apache service namedreported the following error:
>>>AH00015: Unable to open logs - (4126)

[5]2018-12-06 10:55:44:
Application 错误:The Apache service named  reported the following error:
>>> AH00451: no listening sockets available, shutting down
Details: The Apache service namedreported the following error:
>>>AH00451: no listening sockets available, shutting down - (4125)

[6]2018-12-06 10:55:44:
Application 错误:The Apache service named  reported the following error:
>>> (OS 10013)以一种访问权限不允许的方式做了一个访问套接字的尝试。  : AH00072: make_sock: could not bind to address 0.0.0.0:80
Details: The Apache service namedreported the following error:
>>>(OS 10013)以一种访问权限不允许的方式做了一个访问套接字的尝试。  : AH00072: make_sock: could not bind to address 0.0.0.0:80 - (4124)

[7]2018-12-06 10:55:44:
Application 错误:The Apache service named  reported the following error:
>>> (OS 10013)以一种访问权限不允许的方式做了一个访问套接字的尝试。  : AH00072: make_sock: could not bind to address [::]:80
Details: The Apache service namedreported the following error:
>>>(OS 10013)以一种访问权限不允许的方式做了一个访问套接字的尝试。  : AH00072: make_sock: could not bind to address [::]:80 - (4123)

[8]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4131)

[9]2018-12-06 11:03:06:
Application 警告:
Details: phpMyAdmin[11552]user denied: root (mysql-denied) from 127.0.0.1 - (4130)

[10]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4140)

[11]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4139)

[12]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/score 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 jx/score 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 - (4138)

[13]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/perf 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 jx/perf 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 - (4137)

[14]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/id 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 jx/id 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 - (4136)

[15]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/have 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 jx/have 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 - (4135)

[16]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/grade 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 jx/grade 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 - (4134)

[17]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/duties 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 jx/duties 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 - (4133)

[18]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4132)

[19]2018-12-06 11:05:03:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4147)

[20]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/score 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 jx/score 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 - (4146)

[21]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/perf 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 jx/perf 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 - (4145)

[22]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/id 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 jx/id 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 - (4144)

[23]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/have 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 jx/have 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 - (4143)

[24]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/grade 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 jx/grade 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 - (4142)

[25]2018-12-06 11:05:01:
Application 警告:InnoDB: Cannot open table jx/duties 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 jx/duties 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 - (4141)

[26]2018-12-06 11:05:05:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4148)

[27]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4149)

[28]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/id 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 jx/id 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 - (4154)

[29]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/have 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 jx/have 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 - (4153)

[30]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/grade 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 jx/grade 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 - (4152)

[31]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/duties 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 jx/duties 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 - (4151)

[32]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4150)

[33]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/grade 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 jx/grade 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 - (4160)

[34]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/duties 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 jx/duties 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 - (4159)

[35]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4158)

[36]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4157)

[37]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/score 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 jx/score 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 - (4156)

[38]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/perf 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 jx/perf 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 - (4155)

[39]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/score 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 jx/score 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 - (4164)

[40]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/perf 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 jx/perf 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 - (4163)

[41]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/id 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 jx/id 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 - (4162)

[42]2018-12-06 11:05:11:
Application 警告:InnoDB: Cannot open table jx/have 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 jx/have 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 - (4161)

[43]2018-12-06 11:14:19:
Application 错误:规则引擎未能评估规则。
原因:0x80070057
阶段:BUILD_FULL_MACHINE_STATE
其他数据:
<none>
Details: 0x80070057BUILD_FULL_MACHINE_STATE - (4225)

[44]2018-12-06 11:14:30:
Application 错误:规则引擎未能评估规则。
原因:0x80070057
阶段:BUILD_FULL_MACHINE_STATE
其他数据:
<none>
Details: 0x80070057BUILD_FULL_MACHINE_STATE - (4243)

[45]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4248)

[46]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/id 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 jx/id 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 - (4253)

[47]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/have 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 jx/have 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 - (4252)

[48]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/grade 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 jx/grade 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 - (4251)

[49]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/duties 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 jx/duties 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 - (4250)

[50]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4249)

[51]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/duties 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 jx/duties 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 - (4258)

[52]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/dep 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 jx/dep 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 - (4257)

[53]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4256)

[54]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/score 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 jx/score 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 - (4255)

[55]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/perf 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 jx/perf 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 - (4254)

[56]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/score 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 jx/score 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 - (4263)

[57]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/perf 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 jx/perf 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 - (4262)

[58]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/id 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 jx/id 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 - (4261)

[59]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/have 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 jx/have 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 - (4260)

[60]2018-12-06 11:14:41:
Application 警告:InnoDB: Cannot open table jx/grade 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 jx/grade 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 - (4259)

[61]2018-12-06 11:17:28:
Application 警告:InnoDB: Cannot open table jx/category 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 jx/category 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 - (4265)

[62]2018-12-06 11:38:55:
Application 错误:
Details: php[10396]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4297)

[63]2018-12-06 11:38:56:
Application 错误:
Details: php[10228]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4298)

[64]2018-12-06 11:44:58:
Application 警告:
Details: phpMyAdmin[10228]user denied: root (no-activity) from 127.0.0.1 - (4299)

[65]2018-12-06 11:46:47:
Application 错误:
Details: php[10776]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4300)

[66]2018-12-06 11:46:48:
Application 错误:
Details: php[11256]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4301)

[67]2018-12-06 11:48:13:
Application 错误:
Details: php[2176]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4302)

[68]2018-12-06 11:48:14:
Application 错误:
Details: php[11260]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4303)

[69]2018-12-06 11:49:34:
Application 错误:
Details: php[8868]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4304)

[70]2018-12-06 11:49:35:
Application 错误:
Details: php[2368]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4305)

[71]2018-12-06 11:54:07:
Application 错误:
Details: php[10204]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4306)

[72]2018-12-06 11:54:08:
Application 错误:
Details: php[7628]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4307)

[73]2018-12-06 11:55:50:
Application 错误:
Details: php[6240]PHP Warning: PHP Startup: Unable to load dynamic library 'php_libmcrypt.dll' (tried: D:/qampp/php/ext\php_libmcrypt.dll (%1 锟斤拷锟斤拷锟斤拷效锟斤拷 Win32 应锟矫筹拷锟斤拷), D:/qampp/php/ext\php_php_libmcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4309)

[74]2018-12-06 11:55:50:
Application 错误:
Details: php[6240]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) ("D:\qampp\apache\bin\httpd.exe" -k runservice) - (4308)

[75]2018-12-06 11:55:51:
Application 错误:
Details: php[11032]PHP Warning: PHP Startup: Unable to load dynamic library 'php_libmcrypt.dll' (tried: D:/qampp/php/ext\php_libmcrypt.dll (%1 锟斤拷锟斤拷锟斤拷效锟斤拷 Win32 应锟矫筹拷锟斤拷), D:/qampp/php/ext\php_php_libmcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4311)

[76]2018-12-06 11:55:51:
Application 错误:
Details: php[11032]PHP Warning: PHP Startup: Unable to load dynamic library 'php_mcrypt.dll' (tried: D:/qampp/php/ext\php_mcrypt.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。), D:/qampp/php/ext\php_php_mcrypt.dll.dll (锟揭诧拷锟斤拷指锟斤拷锟斤拷模锟介。)) (D:\qampp\apache\bin\httpd.exe -d D:/qampp/apache) - (4310)

[77]2018-12-06 13:25:54:
Application 错误:错误应用程序名称: kuaiyatpopxxrl.exe,版本: 1.0.0.1,时间戳: 0x5bc730cd
错误模块名称: unknown,版本: 0.0.0.0,时间戳: 0x00000000
异常代码: 0xc0000005
错误偏移量: 0x0bbb99b0
错误进程 ID: 0x29ac
错误应用程序启动时间: 0x01d48d1ad98ef1a9
错误应用程序路径: C:\Users\Administrator\AppData\Roaming\kuaiya\12all-allall\kuaiyatpopxxrl.exe
错误模块路径: unknown
报告 ID: 7782c8fb-1b87-4944-a96a-1df386afc79b
错误程序包全名: 
错误程序包相对应用程序 ID:
Details: kuaiyatpopxxrl.exe1.0.0.15bc730cdunknown0.0.0.000000000c00000050bbb99b029ac01d48d1ad98ef1a9C:\Users\Administrator\AppData\Roaming\kuaiya\12all-allall\kuaiyatpopxxrl.exeunknown7782c8fb-1b87-4944-a96a-1df386afc79b - (4320)

Cont:77; Cstr:40437

腾讯云 / 腾讯AI / 腾讯开源 / 南沙新区 / 信用
分享工作室[粤ICP备16004795号-2] Date:2019-10-15 17:38:14(UTC) RunTime:0.052