API tools faq
paste
Advertisement
Guest User

mysql err contents

a guest
Sep 12th, 2013
263
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 233.40 KB | None | 0 0
raw download clone embed print report
  1. 2013-09-13 12:13:06 960 [Note] Plugin 'FEDERATED' is disabled.
  2. 2013-09-13 12:13:06 960 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
  3. 2013-09-13 12:13:06 9e0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
  4. 2013-09-13 12:13:06 960 [Note] InnoDB: The InnoDB memory heap is disabled
  5. 2013-09-13 12:13:06 960 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
  6. 2013-09-13 12:13:06 960 [Note] InnoDB: Compressed tables use zlib 1.2.3
  7. 2013-09-13 12:13:06 960 [Note] InnoDB: Not using CPU crc32 instructions
  8. 2013-09-13 12:13:06 960 [Note] InnoDB: Initializing buffer pool, size = 25.0M
  9. 2013-09-13 12:13:06 960 [Note] InnoDB: Completed initialization of buffer pool
  10. 2013-09-13 12:13:06 960 [Note] InnoDB: Highest supported file format is Barracuda.
  11. 2013-09-13 12:13:06 960 [Note] InnoDB: 128 rollback segment(s) are active.
  12. 2013-09-13 12:13:06 960 [Note] InnoDB: Waiting for purge to start
  13. 2013-09-13 12:13:06 960 [Note] InnoDB: 5.6.13 started; log sequence number 1625977
  14. 2013-09-13 12:13:06 960 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 0748b8e5-1c1a-11e3-ba1a-001c25125d01.
  15. 2013-09-13 12:13:06 960 [Note] Server hostname (bind-address): '*'; port: 3306
  16. 2013-09-13 12:13:06 960 [Note] IPv6 is available.
  17. 2013-09-13 12:13:06 960 [Note] - '::' resolves to '::';
  18. 2013-09-13 12:13:06 960 [Note] Server socket created on IP: '::'.
  19. 2013-09-13 12:13:07 960 [Note] Event Scheduler: Loaded 0 events
  20. 2013-09-13 12:13:07 960 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
  21. Version: '5.6.13-log' socket: '' port: 3306 MySQL Community Server (GPL)
  22. 2013-09-13 12:14:00 960 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Statement: INSERT INTO film VALUES (1,'ACADEMY DINOSAUR','A Epic Drama of a Feminist And a Mad Scientist who must Battle a Teacher in The Canadian Rockies',2006,1,NULL,6,'0.99',86,'20.99','PG','Deleted Scenes,Behind the Scenes','2006-02-15 05:03:42'),(2,'ACE GOLDFINGER','A Astounding Epistle of a Database Administrator And a Explorer who must Find a Car in Ancient China',2006,1,NULL,3,'4.99',48,'12.99','G','Trailers,Deleted Scenes','2006-02-15 05:03:42'),(3,'ADAPTATION HOLES','A Astounding Reflection of a Lumberjack And a Car who must Sink a Lumberjack in A Baloon Factory',2006,1,NULL,7,'2.99',50,'18.99','NC-17','Trailers,Deleted Scenes','2006-02-15 05:03:42'),(4,'AFFAIR PREJUDICE','A Fanciful Documentary of a Frisbee And a Lumberjack who must Chase a Monkey in A Shark Tank',2006,1,NULL,5,'2.99',117
  23. 2013-09-13 12:19:11 960 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Normal shutdown
  24.  
  25. 2013-09-13 12:19:11 960 [Note] Giving 0 client threads a chance to die gracefully
  26. 2013-09-13 12:19:11 960 [Note] Event Scheduler: Purging the queue. 0 events
  27. 2013-09-13 12:19:11 960 [Note] Shutting down slave threads
  28. 2013-09-13 12:19:11 960 [Note] Forcefully disconnecting 0 remaining clients
  29. 2013-09-13 12:19:11 960 [Note] Binlog end
  30. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'partition'
  31. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
  32. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
  33. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
  34. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
  35. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
  36. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
  37. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
  38. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
  39. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
  40. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
  41. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
  42. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
  43. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
  44. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
  45. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_FT_DELETED'
  46. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
  47. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_METRICS'
  48. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
  49. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
  50. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
  51. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
  52. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
  53. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
  54. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_CMPMEM'
  55. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_CMP_RESET'
  56. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_CMP'
  57. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
  58. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_LOCKS'
  59. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'INNODB_TRX'
  60. 2013-09-13 12:19:11 960 [Note] Shutting down plugin 'InnoDB'
  61. 2013-09-13 12:19:11 960 [Note] InnoDB: FTS optimize thread exiting.
  62. 2013-09-13 12:19:11 960 [Note] InnoDB: Starting shutdown...
  63. 2013-09-13 12:19:12 960 [Note] InnoDB: Shutdown completed; log sequence number 8526142
  64. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'BLACKHOLE'
  65. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'ARCHIVE'
  66. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'MRG_MYISAM'
  67. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'MyISAM'
  68. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'MEMORY'
  69. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'CSV'
  70. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'sha256_password'
  71. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'mysql_old_password'
  72. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'mysql_native_password'
  73. 2013-09-13 12:19:12 960 [Note] Shutting down plugin 'binlog'
  74. 2013-09-13 12:19:12 960 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Shutdown complete
  75.  
  76. 2013-09-13 12:20:27 3668 [Note] Plugin 'FEDERATED' is disabled.
  77. 2013-09-13 12:20:27 3668 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
  78. 2013-09-13 12:20:27 538 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
  79. 2013-09-13 12:20:27 3668 [Note] InnoDB: The InnoDB memory heap is disabled
  80. 2013-09-13 12:20:27 3668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
  81. 2013-09-13 12:20:27 3668 [Note] InnoDB: Compressed tables use zlib 1.2.3
  82. 2013-09-13 12:20:27 3668 [Note] InnoDB: Not using CPU crc32 instructions
  83. 2013-09-13 12:20:27 3668 [Note] InnoDB: Initializing buffer pool, size = 25.0M
  84. 2013-09-13 12:20:27 3668 [Note] InnoDB: Completed initialization of buffer pool
  85. 2013-09-13 12:20:27 3668 [Note] InnoDB: Highest supported file format is Barracuda.
  86. 2013-09-13 12:20:28 3668 [Note] InnoDB: 128 rollback segment(s) are active.
  87. 2013-09-13 12:20:28 3668 [Note] InnoDB: Waiting for purge to start
  88. 2013-09-13 12:20:28 3668 [Note] InnoDB: 5.6.13 started; log sequence number 8526142
  89. 2013-09-13 12:20:28 3668 [Note] Server hostname (bind-address): '*'; port: 3306
  90. 2013-09-13 12:20:28 3668 [Note] IPv6 is available.
  91. 2013-09-13 12:20:28 3668 [Note] - '::' resolves to '::';
  92. 2013-09-13 12:20:28 3668 [Note] Server socket created on IP: '::'.
  93. 2013-09-13 12:20:28 3668 [Note] Event Scheduler: Loaded 0 events
  94. 2013-09-13 12:20:28 3668 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
  95. Version: '5.6.13-log' socket: '' port: 3306 MySQL Community Server (GPL)
  96. 2013-09-13 12:35:58 3668 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Normal shutdown
  97.  
  98. 2013-09-13 12:35:58 3668 [Note] Giving 4 client threads a chance to die gracefully
  99. 2013-09-13 12:35:58 3668 [Note] Event Scheduler: Purging the queue. 0 events
  100. 2013-09-13 12:35:58 3668 [Note] Shutting down slave threads
  101. 2013-09-13 12:36:00 3668 [Note] Forcefully disconnecting 4 remaining clients
  102. 2013-09-13 12:36:00 3668 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 2 user: 'root'
  103.  
  104. 2013-09-13 12:36:00 3668 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 3 user: 'root'
  105.  
  106. 2013-09-13 12:36:00 3668 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 4 user: 'root'
  107.  
  108. 2013-09-13 12:36:00 3668 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 6 user: 'root'
  109.  
  110. 2013-09-13 12:36:00 3668 [Note] Binlog end
  111. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'partition'
  112. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
  113. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
  114. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
  115. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
  116. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
  117. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
  118. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
  119. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
  120. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
  121. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
  122. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
  123. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
  124. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
  125. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
  126. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_FT_DELETED'
  127. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
  128. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_METRICS'
  129. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
  130. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
  131. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
  132. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
  133. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
  134. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
  135. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_CMPMEM'
  136. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_CMP_RESET'
  137. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_CMP'
  138. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
  139. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_LOCKS'
  140. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'INNODB_TRX'
  141. 2013-09-13 12:36:00 3668 [Note] Shutting down plugin 'InnoDB'
  142. 2013-09-13 12:36:00 3668 [Note] InnoDB: FTS optimize thread exiting.
  143. 2013-09-13 12:36:00 3668 [Note] InnoDB: Starting shutdown...
  144. 2013-09-13 12:36:01 3668 [Note] InnoDB: Shutdown completed; log sequence number 8526152
  145. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'BLACKHOLE'
  146. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'ARCHIVE'
  147. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'MRG_MYISAM'
  148. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'MyISAM'
  149. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'MEMORY'
  150. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'CSV'
  151. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'sha256_password'
  152. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'mysql_old_password'
  153. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'mysql_native_password'
  154. 2013-09-13 12:36:01 3668 [Note] Shutting down plugin 'binlog'
  155. 2013-09-13 12:36:01 3668 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Shutdown complete
  156.  
  157. 2013-09-13 12:36:03 3456 [Note] Plugin 'FEDERATED' is disabled.
  158. 2013-09-13 12:36:03 3456 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
  159. 2013-09-13 12:36:03 fe4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
  160. 2013-09-13 12:36:03 3456 [Note] InnoDB: The InnoDB memory heap is disabled
  161. 2013-09-13 12:36:03 3456 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
  162. 2013-09-13 12:36:04 3456 [Note] InnoDB: Compressed tables use zlib 1.2.3
  163. 2013-09-13 12:36:04 3456 [Note] InnoDB: Not using CPU crc32 instructions
  164. 2013-09-13 12:36:04 3456 [Note] InnoDB: Initializing buffer pool, size = 25.0M
  165. 2013-09-13 12:36:04 3456 [Note] InnoDB: Completed initialization of buffer pool
  166. 2013-09-13 12:36:04 3456 [Note] InnoDB: Highest supported file format is Barracuda.
  167. 2013-09-13 12:36:04 3456 [Note] InnoDB: 128 rollback segment(s) are active.
  168. 2013-09-13 12:36:04 3456 [Note] InnoDB: Waiting for purge to start
  169. 2013-09-13 12:36:04 3456 [Note] InnoDB: 5.6.13 started; log sequence number 8526152
  170. 2013-09-13 12:36:04 3456 [Note] Server hostname (bind-address): '*'; port: 3306
  171. 2013-09-13 12:36:04 3456 [Note] IPv6 is available.
  172. 2013-09-13 12:36:04 3456 [Note] - '::' resolves to '::';
  173. 2013-09-13 12:36:04 3456 [Note] Server socket created on IP: '::'.
  174. 2013-09-13 12:36:05 3456 [Note] Event Scheduler: Loaded 0 events
  175. 2013-09-13 12:36:05 3456 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
  176. Version: '5.6.13-log' socket: '' port: 3306 MySQL Community Server (GPL)
  177. 2013-09-13 12:36:27 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  178. 2013-09-13 12:36:27 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  179. 2013-09-13 12:36:27 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  180. 2013-09-13 12:36:27 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  181. 2013-09-13 12:36:27 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  182. 2013-09-13 12:36:27 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  183. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  184. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  185. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  186. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  187. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  188. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  189. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  190. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  191. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  192. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  193. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  194. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  195. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  196. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  197. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  198. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  199. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  200. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  201. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  202. 2013-09-13 12:36:28 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  203. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  204. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  205. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  206. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  207. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  208. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  209. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  210. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  211. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  212. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  213. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  214. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  215. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  216. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  217. 2013-09-13 12:36:29 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  218. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  219. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  220. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  221. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  222. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  223. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  224. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  225. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  226. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  227. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  228. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  229. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  230. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  231. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  232. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  233. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  234. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  235. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  236. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  237. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  238. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  239. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  240. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  241. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  242. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  243. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  244. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  245. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  246. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  247. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  248. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  249. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  250. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  251. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  252. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  253. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  254. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  255. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  256. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  257. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  258. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  259. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  260. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  261. 2013-09-13 12:36:30 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  262. 2013-09-13 12:37:07 3456 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Normal shutdown
  263.  
  264. 2013-09-13 12:37:07 3456 [Note] Giving 4 client threads a chance to die gracefully
  265. 2013-09-13 12:37:07 3456 [Note] Event Scheduler: Purging the queue. 0 events
  266. 2013-09-13 12:37:07 3456 [Note] Shutting down slave threads
  267. 2013-09-13 12:37:09 3456 [Note] Forcefully disconnecting 3 remaining clients
  268. 2013-09-13 12:37:09 3456 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 3 user: 'root'
  269.  
  270. 2013-09-13 12:37:09 3456 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 4 user: 'root'
  271.  
  272. 2013-09-13 12:37:09 3456 [Warning] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 5 user: 'root'
  273.  
  274. 2013-09-13 12:37:09 3456 [Note] Binlog end
  275. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'partition'
  276. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
  277. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
  278. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
  279. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
  280. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
  281. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
  282. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
  283. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
  284. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
  285. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
  286. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
  287. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
  288. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
  289. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
  290. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_FT_DELETED'
  291. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
  292. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_METRICS'
  293. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
  294. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
  295. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
  296. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
  297. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
  298. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
  299. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_CMPMEM'
  300. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_CMP_RESET'
  301. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_CMP'
  302. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
  303. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_LOCKS'
  304. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'INNODB_TRX'
  305. 2013-09-13 12:37:09 3456 [Note] Shutting down plugin 'InnoDB'
  306. 2013-09-13 12:37:09 3456 [Note] InnoDB: FTS optimize thread exiting.
  307. 2013-09-13 12:37:09 3456 [Note] InnoDB: Starting shutdown...
  308. 2013-09-13 12:37:10 3456 [Note] InnoDB: Shutdown completed; log sequence number 8526162
  309. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'BLACKHOLE'
  310. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'ARCHIVE'
  311. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'MRG_MYISAM'
  312. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'MyISAM'
  313. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'MEMORY'
  314. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'CSV'
  315. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'sha256_password'
  316. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'mysql_old_password'
  317. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'mysql_native_password'
  318. 2013-09-13 12:37:10 3456 [Note] Shutting down plugin 'binlog'
  319. 2013-09-13 12:37:10 3456 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Shutdown complete
  320.  
  321. 2013-09-13 12:39:05 2060 [Note] Plugin 'FEDERATED' is disabled.
  322. 2013-09-13 12:39:05 2060 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
  323. 2013-09-13 12:39:05 f6c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
  324. 2013-09-13 12:39:05 2060 [Note] InnoDB: The InnoDB memory heap is disabled
  325. 2013-09-13 12:39:05 2060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
  326. 2013-09-13 12:39:05 2060 [Note] InnoDB: Compressed tables use zlib 1.2.3
  327. 2013-09-13 12:39:05 2060 [Note] InnoDB: Not using CPU crc32 instructions
  328. 2013-09-13 12:39:05 2060 [Note] InnoDB: Initializing buffer pool, size = 25.0M
  329. 2013-09-13 12:39:05 2060 [Note] InnoDB: Completed initialization of buffer pool
  330. 2013-09-13 12:39:05 2060 [Note] InnoDB: Highest supported file format is Barracuda.
  331. 2013-09-13 12:39:06 2060 [Note] InnoDB: 128 rollback segment(s) are active.
  332. 2013-09-13 12:39:06 2060 [Note] InnoDB: Waiting for purge to start
  333. 2013-09-13 12:39:06 2060 [Note] InnoDB: 5.6.13 started; log sequence number 8526162
  334. 2013-09-13 12:39:06 2060 [Note] Server hostname (bind-address): '*'; port: 3306
  335. 2013-09-13 12:39:06 2060 [Note] IPv6 is available.
  336. 2013-09-13 12:39:06 2060 [Note] - '::' resolves to '::';
  337. 2013-09-13 12:39:06 2060 [Note] Server socket created on IP: '::'.
  338. 2013-09-13 12:39:06 2060 [Note] Event Scheduler: Loaded 0 events
  339. 2013-09-13 12:39:06 2060 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
  340. Version: '5.6.13-log' socket: '' port: 3306 MySQL Community Server (GPL)
  341. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_category_colors from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  342. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_feeds from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  343. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_instances from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  344. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_events from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  345. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  346. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_categories from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  347. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_config from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  348. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  349. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  350. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  351. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  352. 2013-09-13 13:57:07 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  353. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  354. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_group_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  355. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  356. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_security from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  357. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  358. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  359. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  360. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  361. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  362. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  363. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  364. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  365. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  366. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_attribute_taxonomies from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  367. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_downloadable_product_permissions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  368. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_itemmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  369. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_items from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  370. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rate_locations from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  371. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rates from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  372. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  373. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  374. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  375. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  376. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  377. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  378. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  379. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  380. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  381. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  382. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  383. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  384. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  385. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  386. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  387. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  388. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  389. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  390. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  391. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  392. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  393. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  394. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  395. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  396. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  397. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  398. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  399. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  400. 2013-09-13 13:57:08 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  401. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  402. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  403. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  404. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  405. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  406. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  407. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  408. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  409. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  410. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  411. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  412. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  413. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  414. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_event_category_colors from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  415. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_event_feeds from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  416. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_event_instances from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  417. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_events from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  418. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  419. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  420. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_cpt_sentry_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  421. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  422. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ngg_album from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  423. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ngg_gallery from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  424. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ngg_pictures from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  425. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  426. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  427. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  428. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ps_group_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  429. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ps_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  430. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ps_security from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  431. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  432. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  433. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  434. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  435. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  436. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  437. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_calendar from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  438. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_calendar_categories from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  439. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_calendar_config from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  440. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  441. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  442. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  443. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_ngg_album from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  444. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_ngg_gallery from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  445. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_ngg_pictures from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  446. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  447. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  448. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  449. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_purehtml_functions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  450. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  451. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  452. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  453. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  454. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  455. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  456. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  457. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  458. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  459. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  460. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  461. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  462. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  463. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_errorlogs from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  464. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_fb_friend_lists from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  465. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_fb_friends from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  466. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_postcomments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  467. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_postlogs from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  468. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_process_queue from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  469. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_userdata from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  470. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_userstatus from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  471. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  472. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  473. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  474. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  475. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  476. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  477. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  478. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  479. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  480. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  481. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  482. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_carousel_albums from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  483. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_carousel_images from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  484. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  485. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  486. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  487. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_new_royalsliders from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  488. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  489. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  490. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  491. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  492. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  493. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  494. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  495. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  496. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  497. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  498. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  499. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  500. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  501. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  502. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  503. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  504. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_vslider from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  505. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  506. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  507. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  508. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_ngg_album from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  509. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_ngg_gallery from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  510. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_ngg_pictures from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  511. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  512. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  513. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  514. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  515. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  516. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  517. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  518. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  519. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  520. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  521. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  522. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  523. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  524. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  525. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  526. 2013-09-13 13:57:09 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  527. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  528. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  529. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  530. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_nxs_log from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  531. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  532. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  533. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  534. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  535. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  536. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  537. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  538. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  539. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  540. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  541. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  542. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  543. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  544. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  545. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  546. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  547. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_category_colors from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  548. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_feeds from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  549. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_instances from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  550. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_events from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  551. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  552. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_categories from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  553. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_config from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  554. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  555. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  556. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  557. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  558. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  559. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  560. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_group_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  561. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  562. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_security from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  563. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  564. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  565. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  566. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  567. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  568. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  569. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  570. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  571. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  572. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_attribute_taxonomies from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  573. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_downloadable_product_permissions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  574. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_itemmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  575. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_items from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  576. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rate_locations from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  577. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rates from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  578. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  579. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  580. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  581. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  582. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  583. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  584. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  585. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  586. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  587. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  588. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  589. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table 3dphoto/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  590. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  591. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  592. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  593. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  594. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  595. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  596. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  597. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  598. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  599. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  600. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table alexcudlindb/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  601. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  602. 2013-09-13 13:57:10 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  603. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  604. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  605. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  606. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  607. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  608. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  609. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  610. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  611. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  612. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  613. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  614. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  615. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  616. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  617. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  618. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  619. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table db167272_stk0025_db/stk0025_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  620. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_event_category_colors from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  621. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_event_feeds from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  622. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_event_instances from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  623. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ai1ec_events from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  624. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  625. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  626. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_cpt_sentry_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  627. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  628. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ngg_album from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  629. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ngg_gallery from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  630. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ngg_pictures from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  631. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  632. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  633. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  634. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ps_group_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  635. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ps_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  636. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_ps_security from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  637. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  638. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  639. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  640. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  641. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  642. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table doddsfamilyblog/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  643. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_calendar from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  644. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_calendar_categories from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  645. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_calendar_config from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  646. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  647. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  648. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  649. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_ngg_album from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  650. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_ngg_gallery from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  651. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_ngg_pictures from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  652. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  653. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  654. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  655. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_purehtml_functions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  656. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  657. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  658. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  659. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  660. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  661. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  662. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  663. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  664. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  665. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  666. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  667. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  668. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  669. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_errorlogs from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  670. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_fb_friend_lists from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  671. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_fb_friends from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  672. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_postcomments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  673. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_postlogs from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  674. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_process_queue from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  675. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_userdata from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  676. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table ftbawordpress/wp_wordbooker_userstatus from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  677. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  678. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  679. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  680. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  681. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  682. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  683. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  684. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  685. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  686. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  687. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table gourmetmeats/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  688. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_carousel_albums from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  689. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_carousel_images from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  690. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  691. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  692. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  693. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_new_royalsliders from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  694. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  695. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  696. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  697. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  698. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  699. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  700. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  701. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  702. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  703. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  704. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  705. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  706. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  707. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  708. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  709. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  710. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table landtrecruitment/wp_vslider from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  711. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  712. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  713. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  714. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_ngg_album from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  715. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_ngg_gallery from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  716. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_ngg_pictures from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  717. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  718. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  719. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  720. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  721. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  722. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  723. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  724. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  725. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  726. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  727. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  728. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  729. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  730. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  731. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  732. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table lillypillyps/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  733. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  734. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  735. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  736. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_nxs_log from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  737. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  738. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  739. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  740. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_form from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  741. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_form_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  742. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_form_view from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  743. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  744. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_detail from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  745. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_detail_long from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  746. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  747. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_rg_lead_notes from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  748. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  749. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  750. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  751. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  752. 2013-09-13 13:57:11 2060 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  753. 2013-09-13 14:00:45 2060 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Normal shutdown
  754.  
  755. 2013-09-13 14:00:45 2060 [Note] Giving 0 client threads a chance to die gracefully
  756. 2013-09-13 14:00:45 2060 [Note] Event Scheduler: Purging the queue. 0 events
  757. 2013-09-13 14:00:45 2060 [Note] Shutting down slave threads
  758. 2013-09-13 14:00:45 2060 [Note] Forcefully disconnecting 0 remaining clients
  759. 2013-09-13 14:00:45 2060 [Note] Binlog end
  760. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'partition'
  761. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
  762. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
  763. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
  764. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
  765. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
  766. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
  767. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
  768. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
  769. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
  770. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
  771. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
  772. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
  773. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
  774. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
  775. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_FT_DELETED'
  776. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
  777. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_METRICS'
  778. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
  779. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
  780. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
  781. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
  782. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
  783. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
  784. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_CMPMEM'
  785. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_CMP_RESET'
  786. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_CMP'
  787. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
  788. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_LOCKS'
  789. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'INNODB_TRX'
  790. 2013-09-13 14:00:45 2060 [Note] Shutting down plugin 'InnoDB'
  791. 2013-09-13 14:00:45 2060 [Note] InnoDB: FTS optimize thread exiting.
  792. 2013-09-13 14:00:45 2060 [Note] InnoDB: Starting shutdown...
  793. 2013-09-13 14:00:47 2060 [Note] InnoDB: Shutdown completed; log sequence number 8526172
  794. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'BLACKHOLE'
  795. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'ARCHIVE'
  796. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'MRG_MYISAM'
  797. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'MyISAM'
  798. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'MEMORY'
  799. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'CSV'
  800. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'sha256_password'
  801. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'mysql_old_password'
  802. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'mysql_native_password'
  803. 2013-09-13 14:00:47 2060 [Note] Shutting down plugin 'binlog'
  804. 2013-09-13 14:00:47 2060 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Shutdown complete
  805.  
  806. 2013-09-13 14:00:48 3456 [Note] Plugin 'FEDERATED' is disabled.
  807. 2013-09-13 14:00:48 3456 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
  808. 2013-09-13 14:00:48 112c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
  809. 2013-09-13 14:00:48 3456 [Note] InnoDB: The InnoDB memory heap is disabled
  810. 2013-09-13 14:00:48 3456 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
  811. 2013-09-13 14:00:48 3456 [Note] InnoDB: Compressed tables use zlib 1.2.3
  812. 2013-09-13 14:00:48 3456 [Note] InnoDB: Not using CPU crc32 instructions
  813. 2013-09-13 14:00:49 3456 [Note] InnoDB: Initializing buffer pool, size = 25.0M
  814. 2013-09-13 14:00:49 3456 [Note] InnoDB: Completed initialization of buffer pool
  815. 2013-09-13 14:00:49 3456 [Note] InnoDB: Highest supported file format is Barracuda.
  816. 2013-09-13 14:00:49 3456 [Note] InnoDB: 128 rollback segment(s) are active.
  817. 2013-09-13 14:00:49 3456 [Note] InnoDB: Waiting for purge to start
  818. 2013-09-13 14:00:49 3456 [Note] InnoDB: 5.6.13 started; log sequence number 8526172
  819. 2013-09-13 14:00:50 3456 [Note] Server hostname (bind-address): '*'; port: 3306
  820. 2013-09-13 14:00:50 3456 [Note] IPv6 is available.
  821. 2013-09-13 14:00:50 3456 [Note] - '::' resolves to '::';
  822. 2013-09-13 14:00:50 3456 [Note] Server socket created on IP: '::'.
  823. 2013-09-13 14:00:50 3456 [Note] Event Scheduler: Loaded 0 events
  824. 2013-09-13 14:00:50 3456 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
  825. Version: '5.6.13-log' socket: '' port: 3306 MySQL Community Server (GPL)
  826. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_category_colors from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  827. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_feeds from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  828. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_instances from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  829. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_events from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  830. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  831. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_categories from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  832. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_config from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  833. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  834. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  835. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  836. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  837. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  838. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  839. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_group_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  840. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  841. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_security from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  842. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  843. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  844. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  845. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  846. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  847. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  848. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  849. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  850. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  851. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_attribute_taxonomies from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  852. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_downloadable_product_permissions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  853. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_itemmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  854. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_items from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  855. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rate_locations from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  856. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rates from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  857. 2013-09-13 14:01:27 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  858. 2013-09-13 14:01:32 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  859. 2013-09-13 14:01:32 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  860. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_category_colors from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  861. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_feeds from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  862. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_event_instances from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  863. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ai1ec_events from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  864. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  865. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_categories from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  866. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_calendar_config from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  867. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  868. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  869. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  870. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  871. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  872. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  873. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_group_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  874. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_groups from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  875. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_ps_security from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  876. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  877. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_meta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  878. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_smooth_slider_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  879. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  880. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  881. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  882. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  883. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  884. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  885. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_attribute_taxonomies from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  886. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_downloadable_product_permissions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  887. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_itemmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  888. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_order_items from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  889. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rate_locations from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  890. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_tax_rates from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  891. 2013-09-13 14:02:39 3456 [Warning] InnoDB: Cannot open table 3dinfo/wp_woocommerce_termmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  892. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  893. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  894. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  895. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  896. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  897. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  898. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  899. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  900. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  901. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  902. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  903. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  904. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  905. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  906. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  907. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  908. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  909. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  910. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  911. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  912. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  913. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  914. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  915. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  916. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  917. 2013-09-13 14:03:47 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  918. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  919. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  920. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  921. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  922. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  923. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  924. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  925. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  926. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  927. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  928. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  929. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  930. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  931. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  932. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  933. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  934. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  935. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  936. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  937. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  938. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  939. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  940. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  941. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  942. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  943. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  944. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  945. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  946. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  947. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  948. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  949. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  950. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  951. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  952. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  953. 2013-09-13 14:03:48 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  954. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  955. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  956. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  957. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  958. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  959. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  960. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  961. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  962. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  963. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  964. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  965. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  966. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  967. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  968. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  969. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  970. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  971. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  972. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  973. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  974. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  975. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  976. 2013-09-13 14:03:49 3456 [Warning] InnoDB: Cannot open table thelawcompanywp/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  977. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  978. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  979. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  980. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  981. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  982. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  983. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  984. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  985. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  986. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  987. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  988. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  989. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  990. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  991. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  992. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  993. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  994. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  995. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  996. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  997. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  998. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  999. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1000. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1001. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1002. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1003. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1004. 2013-09-13 14:06:45 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1005. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1006. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1007. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1008. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1009. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1010. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1011. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1012. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1013. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1014. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1015. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1016. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1017. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1018. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1019. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1020. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1021. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1022. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1023. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1024. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1025. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1026. 2013-09-13 14:06:46 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1027. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1028. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1029. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1030. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1031. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1032. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1033. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1034. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1035. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1036. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1037. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1038. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1039. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1040. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1041. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1042. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1043. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1044. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1045. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1046. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1047. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1048. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1049. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1050. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1051. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1052. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1053. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1054. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_users from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1055. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_usermeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1056. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_posts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1057. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_comments from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1058. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_links from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1059. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1060. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_postmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1061. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_terms from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1062. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_taxonomy from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1063. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_term_relationships from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1064. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_commentmeta from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1065. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1066. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1067. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1068. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1069. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1070. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1071. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1072. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1073. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1074. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  1075. 2013-09-13 14:06:47 3456 [Warning] InnoDB: Cannot open table ftbawordpress/wp_options from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!