Issues with pay periods

General support regarding TimeTrex, such as
configuring policies/taxes or processing payroll.
Locked
StAugIT
Posts: 21
Joined: Wed Oct 25, 2006 6:07 am

Issues with pay periods

Post by StAugIT »

1. Clearly state what is happening, or what isn't happening that you feel should. If there are any error messages include the FULL EXACT error message.

Employees aren't getting assigned to pay periods even though they exist. Also when I attempt to close the pay period it doesn't allow me to amd gives me the output that follows. The pay periods are generated automatically and shows that all employees are assigned to it.


2. Clearly state the EXACT steps you took before the issue occurred, or steps to reproduce the issue.

Any time I try to close the pay period. or any time I look at the timesheet and it says "employee not assigned to pay period"

3. What version of TimeTrex you are running.
v1.4.1


4. What version of PHP you are using.
5.2.0-8


5. What operating system you are running.
linux -- debian
6. What web server you are using.
apache
7. Have you configured PHP to log errors to a file, and what errors are showing up in this file? yes, none
("error_log = <filename>" in PHP.INI)

Debug output:

(mysqlt): SET SESSION sql_mode='ansi'
(mysqlt): select session_id,user_id,ip_address,created_date,updated_date from authentication WHERE session_id = 'a87e09d1bb8f475cea020c9934363681' AND ip_address = '192.168.1.118' AND updated_date >= 1172583273
(mysqlt): update authentication set updated_date = 1172597674 where session_id = 'a87e09d1bb8f475cea020c9934363681'
(mysqlt): SET SESSION time_zone='EST5EDT'
(mysqlt): select * from station where company_id = '1' AND station_id = 'aef86cd496b87785015ae2c48bbcf5a8' AND deleted = 0
(mysqlt): select * from cron WHERE deleted = 0 ORDER BY last_run_date DESC LIMIT 1
(mysqlt): SELECT count(*) FROM message as a LEFT JOIN users as d ON a.object_type_id = 5 AND a.object_id = d.id LEFT JOIN request as b ON a.object_type_id = 50 AND a.object_id = b.id AND b.deleted=0 LEFT JOIN user_date as c ON b.user_date_id = c.id AND c.deleted = 0 WHERE a.object_type_id in (5,50) AND a.status_id = 10 AND ( ( c.user_id = '5' OR d.id = '5' OR a.parent_id in ( select parent_id FROM message WHERE created_by = '5' AND parent_id != 0 ) OR a.parent_id in ( select id FROM message WHERE created_by = '5' AND parent_id = 0 ) ) AND a.created_by != '5' ) AND a.deleted = 0
(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 = '5' AND b.date_stamp < '2007-02-27 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 permission where company_id = '1' AND user_id in (-1, '5' ) AND deleted = 0 ORDER BY company_id ASC, user_id ASC
(mysqlt): select * from pay_period where company_id = '1' AND id = '16' AND deleted=0
(mysqlt): SET AUTOCOMMIT=0
(mysqlt): BEGIN
(mysqlt): select * from pay_period_schedule where id = '6' AND deleted=0
FailTrans was called
ADOConnection.FailTrans() % line 58, file: Exception.class.php
GeneralError.__construct(Invalid Data, not saving.) % line 774, 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/timetrex/classes/modules/core/Factory.class.php
Line Number: 774
======================================================================
EXCEPTION!
======================================================================

Debug Buffer
============================================================================
Memory Usage: 8112364
----------------------------------------------------------------------------
DEBUG [135]: [Function](): URI: /timetrex/interface/payperiod/ViewPayPeriod.php
DEBUG [137]: [Function](): Production: 1
DEBUG [92]: TTDate::setTimeZone(): Setting TimeZone: PST8PDT
DEBUG [444]: Authentication::Check(): Session Name: SessionID
DEBUG [450]: Authentication::Check(): Session ID: a87e09d1bb8f475cea020c9934363681
DEBUG [301]: Validator::stripNonAlphaNumeric(): Alpha Numeric String:a87e09d1bb8f475cea020c9934363681
DEBUG [78]: Authentication::getIdle(): Idle Seconds Allowed: 14400
DEBUG [301]: Validator::stripNonAlphaNumeric(): Alpha Numeric String:a87e09d1bb8f475cea020c9934363681
DEBUG [62]: [Function](): User Authenticated: mark
DEBUG [1696]: UserFactory::isInformationComplete(): User Information is Complete:
DEBUG [92]: TTDate::setTimeZone(): Setting TimeZone: EST5EDT
DEBUG [108]: TTDate::setDateFormat(): Setting Default Date Format: D, F d Y
DEBUG [122]: TTDate::setTimeFormat(): Setting Default Time Format: g:i A
DEBUG [136]: TTDate::setTimeUnitFormat(): Setting Default Time Unit Format: 20
DEBUG [1696]: UserFactory::isInformationComplete(): User Information is Complete:
DEBUG [954]: UserPreferenceFactory::isPreferencesComplete(): User Preferences IS Complete:
DEBUG [105]: [Function](): Station ID Cookie found! aef86cd496b87785015ae2c48bbcf5a8
DEBUG [196]: [Function](): UnRead Messages: 0
DEBUG [94]: Validator::inArrayKey(): Key: 12
DEBUG [720]: Factory::StartTransaction(): StartTransaction(): Transaction Count: 0 Trans Off: 0
DEBUG [766]: Factory::Save(): Calling preSave()
DEBUG [720]: Factory::StartTransaction(): StartTransaction(): Transaction Count: 1 Trans Off: 1
DEBUG [737]: Factory::isValid(): Calling Validate()
DEBUG [488]: PayPeriodFactory::Validate(): Start Date: 1170824400 End Date: 1172033999
DEBUG [536]: PayPeriodFactory::Validate(): Pay Period Type is NOT Monthly + Advance:
DEBUG [405]: Validator::Error(): Validation Error: Label: advance_end_date Msg: Advance end date is set
DEBUG [405]: Validator::Error(): Validation Error: Label: advance_transaction_date Msg: Advance transaction date is set
DEBUG [384] 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"
}
}

============================================================================
--------------------
Atlantique Press
St. Augustine Florida
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Post by shaunw »

This issue is fixed in the latest version of TimeTrex, please upgrade.
Locked