Uncaught exception 'ADODB_Exception'

poopa · Post by **poopa** » Tue Mar 20, 2007 1:01 am

Hi ,
Since today I'm getting this error when click on MyTimeSheet.

Fatal error: Uncaught exception 'ADODB_Exception' with message 'mysqlt error: [1030: Got error 134 from storage engine] in EXECUTE(" select a.*, c.date_stamp as user_date_stamp from punch as a, punch_control as b, user_date as c, users as d where a.punch_control_id = b.id AND b.user_date_id = c.id AND c.user_id = d.id AND d.company_id = '1' AND c.user_id = '19' AND c.date_stamp >= '2007-03-11 00:00:00' AND c.date_stamp <= '2007-03-17 23:59:59' AND ( a.deleted = 0 AND b.deleted = 0 AND c.deleted = 0 ) ORDER BY a.time_stamp asc, a.status_id desc, a.punch_control_id asc ") ' in C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb-exceptions.inc.php:78 Stack trace: #0 C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb.inc.php(886): adodb_throw('mysqlt', 'EXECUTE', 1030, 'Got error 134 f...', '??????select ?a...', false, Object(ADODB_mysqlt)) #1 C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb.inc.php(842): A in C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb-exceptions.inc.php on line 78

Also, a specific user when clicking on In/Out is getting this message:

Fatal error: Uncaught exception 'ADODB_Exception' with message 'mysqlt error: [1030: Got error 134 from storage engine] in EXECUTE(" select * from user_date where user_id = '5' AND date_stamp = '2007-03-20 09:58:02' AND deleted = 0 ") ' in C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb-exceptions.inc.php:78 Stack trace: #0 C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb.inc.php(886): adodb_throw('mysqlt', 'EXECUTE', 1030, 'Got error 134 f...', '??????select ?*...', false, Object(ADODB_mysqlt)) #1 C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb.inc.php(842): ADOConnection->_Execute('??????select ?*...') #2 C:\Program Files\xampp\htdocs\TimeTrex\classes\modules\core\UserDateListFactory.class.php(218): ADOConnection->Execute('??????select ?*...', Array) #3 C:\Program Files\xampp\htdocs\TimeTrex\classes\modules\schedule\ScheduleListFactory.class.php(294): UserDateListFactory->getByUserIdAndDate('5', 1174377482) #4 C:\Program Files\xampp\htdocs\TimeTrex\i in C:\Program Files\xampp\htdocs\TimeTrex\classes\adodb\adodb-exceptions.inc.php on line 78

Any ideas what went wrong?

poopa · Post by **poopa** » Tue Mar 20, 2007 1:22 am

I was able to fix it by running REPAIR TABLE on punch , punch_control , user_date and users

Post by **shaunw** » Tue Mar 20, 2007 10:18 am

I would confirm that you are using MySQL's InnoDB storage engine. Unfortunately corrupt tables can be quite common with MySQL if you are not using InnoDB.

This topic:

http://forums.timetrex.com/viewtopic.php?t=214

Explains how you can find out if you are using InnoDB or not.

poopa · Post by **poopa** » Wed Apr 11, 2007 12:25 am

I checked using the command you suggested
all the engine fields are myISAM.
I guess I should change that to innoDB.
How do I do that?

Post by **shaunw** » Wed Apr 11, 2007 9:07 am

Run the following commands at your MySQL console. Then double check that all tables have been converted to InnoDB with the same command you used to check before.

Code: Select all

alter table absence_policy ENGINE=InnoDB;
alter table accrual ENGINE=InnoDB;
alter table accrual_balance ENGINE=InnoDB;
alter table accrual_policy ENGINE=InnoDB;
alter table authentication ENGINE=InnoDB;
alter table authorizations ENGINE=InnoDB;
alter table bank_account ENGINE=InnoDB;
alter table branch ENGINE=InnoDB;
alter table bread_crumb ENGINE=InnoDB;
alter table company ENGINE=InnoDB;
alter table company_deduction ENGINE=InnoDB;
alter table company_deduction_pay_stub_entry_account ENGINE=InnoDB;
alter table cron ENGINE=InnoDB;
alter table department ENGINE=InnoDB;
alter table department_branch ENGINE=InnoDB;
alter table department_branch_user ENGINE=InnoDB;
alter table exception ENGINE=InnoDB;
alter table exception_policy ENGINE=InnoDB;
alter table exception_policy_control ENGINE=InnoDB;
alter table help ENGINE=InnoDB;
alter table help_group ENGINE=InnoDB;
alter table help_group_control ENGINE=InnoDB;
alter table hierarchy_control ENGINE=InnoDB;
alter table hierarchy_object_type ENGINE=InnoDB;
alter table hierarchy_share ENGINE=InnoDB;
alter table hierarchy_tree ENGINE=InnoDB;
alter table holiday ENGINE=InnoDB;
alter table holiday_policy ENGINE=InnoDB;
alter table holiday_policy_recurring_holiday ENGINE=InnoDB;
alter table holidays ENGINE=InnoDB;
alter table system_log ENGINE=InnoDB;
alter table meal_policy ENGINE=InnoDB;
alter table message ENGINE=InnoDB;
alter table other_field ENGINE=InnoDB;
alter table over_time_policy ENGINE=InnoDB;
alter table pay_period ENGINE=InnoDB;
alter table pay_period_schedule ENGINE=InnoDB;
alter table pay_period_schedule_user ENGINE=InnoDB;
alter table pay_stub ENGINE=InnoDB;
alter table pay_stub_amendment ENGINE=InnoDB;
alter table pay_stub_entry ENGINE=InnoDB;
alter table pay_stub_entry_account ENGINE=InnoDB;
alter table pay_stub_entry_account_link ENGINE=InnoDB;
alter table permission ENGINE=InnoDB;
alter table policy_group ENGINE=InnoDB;
alter table policy_group_over_time_policy ENGINE=InnoDB;
alter table policy_group_premium_policy ENGINE=InnoDB;
alter table policy_group_round_interval_policy ENGINE=InnoDB;
alter table policy_group_user ENGINE=InnoDB;
alter table premium_policy ENGINE=InnoDB;
alter table punch ENGINE=InnoDB;
alter table punch_control ENGINE=InnoDB;
alter table recurring_holiday ENGINE=InnoDB;
alter table recurring_ps_amendment ENGINE=InnoDB;
alter table recurring_ps_amendment_user ENGINE=InnoDB;
alter table recurring_schedule_control ENGINE=InnoDB;
alter table recurring_schedule_template ENGINE=InnoDB;
alter table recurring_schedule_template_control ENGINE=InnoDB;
alter table recurring_schedule_user ENGINE=InnoDB;
alter table request ENGINE=InnoDB;
alter table roe ENGINE=InnoDB;
alter table round_interval_policy ENGINE=InnoDB;
alter table round_policy ENGINE=InnoDB;
alter table schedule ENGINE=InnoDB;
alter table schedule_policy ENGINE=InnoDB;
alter table station ENGINE=InnoDB;
alter table station_user ENGINE=InnoDB;
alter table system_setting ENGINE=InnoDB;
alter table user ENGINE=InnoDB;
alter table user_date ENGINE=InnoDB;
alter table user_date_total ENGINE=InnoDB;
alter table user_deduction ENGINE=InnoDB;
alter table user_default ENGINE=InnoDB;
alter table user_default_company_deduction ENGINE=InnoDB;
alter table user_generic_data ENGINE=InnoDB;
alter table user_pay_period_total ENGINE=InnoDB;
alter table user_preference ENGINE=InnoDB;
alter table user_tax ENGINE=InnoDB;
alter table user_title ENGINE=InnoDB;
alter table user_wage ENGINE=InnoDB;
alter table pay_period_time_sheet_verify ENGINE=InnoDB;
alter table company_user_count ENGINE=InnoDB;
alter table client ENGINE=InnoDB;
alter table client_balance ENGINE=InnoDB;
alter table client_contact ENGINE=InnoDB;
alter table client_group ENGINE=InnoDB;
alter table client_group_tree ENGINE=InnoDB;
alter table client_payment ENGINE=InnoDB;
alter table document ENGINE=InnoDB;
alter table document_attachment ENGINE=InnoDB;
alter table document_group ENGINE=InnoDB;
alter table document_group_tree ENGINE=InnoDB;
alter table document_revision ENGINE=InnoDB;
alter table invoice ENGINE=InnoDB;
alter table invoice_config ENGINE=InnoDB;
alter table invoice_transaction ENGINE=InnoDB;
alter table job ENGINE=InnoDB;
alter table job_group ENGINE=InnoDB;
alter table job_group_tree ENGINE=InnoDB;
alter table job_item ENGINE=InnoDB;
alter table job_item_allow ENGINE=InnoDB;
alter table job_item_amendment ENGINE=InnoDB;
alter table job_item_group ENGINE=InnoDB;
alter table job_item_group_tree ENGINE=InnoDB;
alter table job_user_allow ENGINE=InnoDB;
alter table product ENGINE=InnoDB;
alter table product_group ENGINE=InnoDB;
alter table product_group_tree ENGINE=InnoDB;
alter table tax_policy ENGINE=InnoDB;
alter table tax_policy_object ENGINE=InnoDB;
alter table invoice_district ENGINE=InnoDB;
alter table tax_area_policy ENGINE=InnoDB;
alter table tax_area_policy_location ENGINE=InnoDB;
alter table income_tax_rate ENGINE=InnoDB;
alter table income_tax_rate_us ENGINE=InnoDB;
alter table user_generic_status ENGINE=InnoDB;
alter table user_group ENGINE=InnoDB;
alter table user_group_tree ENGINE=InnoDB;
alter table accrual_policy_milestone ENGINE=InnoDB;
alter table currency ENGINE=InnoDB;
alter table policy_group_accrual_policy ENGINE=InnoDB;
alter table users ENGINE=InnoDB;
alter table system_log ENGINE=InnoDB;

poopa · Post by **poopa** » Thu Apr 12, 2007 9:03 am

Did that, gave me this output but still all engines are myISAM.

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.18 sec)

Query OK, 23 rows affected (0.09 sec)

Query OK, 30 rows affected (0.09 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 2 rows affected (0.09 sec)

Query OK, 28 rows affected (0.08 sec)

Query OK, 1 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 8 rows affected (0.20 sec)

Query OK, 8 rows affected (0.09 sec)

Query OK, 2 rows affected (0.09 sec)

Query OK, 5 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 12 rows affected (0.09 sec)

Query OK, 1 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.10 sec)

Query OK, 0 rows affected (0.15 sec)

Query OK, 1 rows affected (0.08 sec)

Query OK, 1 rows affected (0.08 sec)

Query OK, 13 rows affected (0.08 sec)

Query OK, 16 rows affected (0.09 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 16952 rows affected (0.43 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 36 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 7 rows affected (0.08 sec)

Query OK, 3 rows affected (0.10 sec)

Query OK, 34 rows affected (0.08 sec)

Query OK, 17 rows affected (0.09 sec)

Query OK, 0 rows affected (0.13 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 14 rows affected (0.09 sec)

Query OK, 1 rows affected (0.09 sec)

Query OK, 1165 rows affected (0.12 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.21 sec)

Query OK, 0 rows affected (0.16 sec)

Query OK, 0 rows affected (0.20 sec)

Query OK, 0 rows affected (0.19 sec)

Query OK, 2086 rows affected (0.18 sec)

Query OK, 1116 rows affected (0.11 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.12 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 27 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.10 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 1087 rows affected (0.12 sec)

Query OK, 1 rows affected (0.07 sec)

Query OK, 8 rows affected (0.06 sec)

Query OK, 1017 rows affected (0.10 sec)

Query OK, 2983 rows affected (0.13 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 16 rows affected (0.09 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 30 rows affected (0.08 sec)

Query OK, 0 rows affected (0.10 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 5 rows affected (0.07 sec)

Query OK, 2 rows affected (0.08 sec)

Query OK, 118 rows affected (0.09 sec)

Query OK, 680 rows affected (0.09 sec)

Query OK, 17 rows affected (0.10 sec)

Query OK, 0 rows affected (0.26 sec)

Query OK, 1 rows affected (0.09 sec)

Query OK, 19 rows affected (0.10 sec)

Query OK, 16952 rows affected (0.43 sec)

Post by **shaunw** » Thu Apr 12, 2007 9:41 am

Your MySQL version doesn't have InnoDB tables enabled then. You will need to find a version that supports InnoDB, or find out how to enable InnoDB with your current version.

Most recent versions of MySQL support InnoDB out of the box, so this is somewhat strange.

TimeTrex Time and Attendance

Uncaught exception 'ADODB_Exception'

Uncaught exception 'ADODB_Exception'

Time and Attendance