Exception error, followed "how to ask for help" st

[StAugIT]

1. + 2.
I have 9 employees set to use Timetrex on a bi-weekly pay schedule. I
set up the first pay period to start Dec. 13th. and end on the 26th
with a transaction day of the 27th. The next pay period was supposed to
start on the 27th and go through Jan. 9th, but everyone's timesheet
shows that no one is assigned to a pay period on the 27th, but they are
on the 28th. When I go to close the last pay period in hopes that
closing the last one will help everyone to start fresh and get rid of
the bug, I get an error:

3. TimeTrex_Standard_Edition_v1.3.0-beta2.zip

4. 5.2 (DateTime > TTDate global search and replace fix used)

5. Debian

6. Apache

7. No PHP log errors, and yes, it is set up because I created a false positive error and it appeared in the log

8.
(mysqlt): SET SESSION sql_mode='ansi' (mysqlt): select
session_id,user_id,ip_address,created_date,updated_date from
authentication WHERE session_id = '6646f1cad715838e58ad8d368a1a5cea'
AND ip_address = '192.168.1.57' AND updated_date >= 1167317998
(mysqlt): update authentication set updated_date = 1167332398 where
session_id = '6646f1cad715838e58ad8d368a1a5cea' (mysqlt): SET SESSION
time_zone='America/New_York' (mysqlt): select * from station where
company_id = '1' AND station_id = '3de521df982d47e9fda993a73776ee9e'
AND deleted = 0 (mysqlt): select * from cron WHERE deleted = 0 ORDER
BY last_run_date DESC LIMIT 1 (mysqlt): select d.severity_id as
severity_id, count(*) as count from exception as a LEFT JOIN user_date
as b ON a.user_date_id = b.id LEFT JOIN users as c ON b.user_id = c.id
LEFT JOIN exception_policy as d ON a.exception_policy_id = d.id LEFT
JOIN pay_period as e ON b.pay_period_id = e.id where b.user_id = '1'
AND b.date_stamp < '2006-12-28 00:00:00' AND e.status_id = 10 AND NOT
EXISTS ( select z.id from request as z where z.user_date_id =
a.user_date_id AND z.status_id = 30 ) AND ( a.deleted = 0 AND b.deleted
= 0 AND e.deleted=0) GROUP BY d.severity_id ORDER BY d.severity_id desc
(mysqlt): select * from pay_period where company_id = '1' AND id =
'2' AND deleted=0 (mysqlt): SET AUTOCOMMIT=0 (mysqlt): BEGIN
(mysqlt): select * from pay_period_schedule where id = '3' AND
deleted=0 FailTrans was called

ADOConnection.FailTrans() % line 60, file: Exception.class.php
GeneralError.__construct(Invalid Data, not saving.) % line 748, file:
Factory.class.php
Factory.Save() % line 62, file: ViewPayPeriod.php

======================================================================
EXCEPTION!
======================================================================
Error message: Invalid Data, not saving.
Error code: 0
Script Name:
/var/www/php/timetrex/classes/modules/core/Factory.class.php
Line Number: 748
======================================================================
EXCEPTION!
Debug Buffer
========================================================================
====
Memory Usage: 7702960
------------------------------------------------------------------------
----
DEBUG [136]: [Function](): URI:
/php/timetrex/interface/payperiod/ViewPayPeriod.php
DEBUG [138]: [Function](): Production: 1
DEBUG [92]: TTDate::setTimeZone(): Setting TimeZone: PST8PDT
DEBUG [423]: Authentication::Check(): Session Name: SessionID
DEBUG [429]: Authentication::Check(): Session ID:
6646f1cad715838e58ad8d368a1a5cea
DEBUG [278]: Validator::stripNonAlphaNumeric(): Alpha Numeric
String:6646f1cad715838e58ad8d368a1a5cea
DEBUG [78]: Authentication::getIdle(): Idle Seconds Allowed: 14400
DEBUG [278]: Validator::stripNonAlphaNumeric(): Alpha Numeric
String:6646f1cad715838e58ad8d368a1a5cea
DEBUG [62]: [Function](): User Authenticated: admin
DEBUG [1543]: UserFactory::isInformationComplete(): User Information is
Complete:
DEBUG [92]: TTDate::setTimeZone(): Setting TimeZone: America/New_York
DEBUG [108]: TTDate::setDateFormat(): Setting Default Date Format: d-M-y
DEBUG [122]: TTDate::setTimeFormat(): Setting Default Time Format: g:i A
DEBUG [136]: TTDate::setTimeUnitFormat(): Setting Default Time Unit
Format: 10
DEBUG [1543]: UserFactory::isInformationComplete(): User Information is
Complete:
DEBUG [954]: UserPreferenceFactory::isPreferencesComplete(): User
Preferences IS Complete:
DEBUG [105]: [Function](): Station ID Cookie found!
3de521df982d47e9fda993a73776ee9e
DEBUG [192]: [Function](): UnRead Messages: 0
DEBUG [94]: Validator::inArrayKey(): Key: 20
DEBUG [694]: Factory::StartTransaction(): StartTransaction():
Transaction Count: 0 Trans Off: 0
DEBUG [740]: Factory::Save(): Calling preSave()
DEBUG [694]: Factory::StartTransaction(): StartTransaction():
Transaction Count: 1 Trans Off: 1
DEBUG [711]: Factory::isValid(): Calling Validate()
DEBUG [488]: PayPeriodFactory::Validate(): Start Date: 1165986000 End
Date: 1167195539
DEBUG [536]: PayPeriodFactory::Validate(): Pay Period Type is NOT
Monthly + Advance:
DEBUG [382]: Validator::Error(): Validation Error: Label:
advance_end_date Msg: Advance end date is set
DEBUG [382]: Validator::Error(): Validation Error: Label:
advance_transaction_date Msg: Advance transaction date is set
DEBUG [361] Array: Validator::isValid(): Errors

array(2) {
["advance_end_date"]=>
array(1) {
[0]=>
string(23) "Advance end date is set"
}
["advance_transaction_date"]=>
array(1) {
[0]=>
string(31) "Advance transaction date is set"
}
}


========================================================================
====

[shaunw]

Try upgrading to version 1.4.0-final (released today, and supports PHP version 5.2 out of the box) and see if that helps. The version you are running is pretty old now and combined with your custom changes it could be the cause of your problem.

[mikeb]

This topic may solve your problem:

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

However we still recommend you upgrade.