I am really at a loss here. I have searched through the forms and made corrections as needed; I am still getting the infamous ‘WARNING: TimeTrex maintenance jobs have not run in the last 48hours. Please contact your TimeTrex administrator immediately’ message.
TimeTrex is running on my pc which I do not turn off and reboot at most once per week.
Below are, I think, all of the pertinent details regarding my installation/configuration/schedule. Assistance would be greatly appreciated and thanks in advance.
OPERATING SYSTEM
Windows XP SP2
PATH:
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Co
mmon Files\Roxio Shared\DLLShared\;C:\Program Files\GNU\GnuPG\pub;C:\Program Fil
es\QuickTime\QTSystem\;D:\Program Files\MySQL\MySQL Server 5.0\bin;C:\Program Fi
les\MOVEit;C:\Program Files\TimeTrex;C:\Program Files\TimeTrex\php;C:\Program Fi
les\TimeTrex\postgresql\bin;
SCHEDULED TASK
"C:\Program Files\TimeTrex\php\php-win.exe" "C:\Program Files\TimeTrex\timetrex\maint\cron.php"
Name Schedule Next Run Time Last Run Time
timetrex_maintenance Every 1 minust(s) from 11:56 AM for 24 hours(s) every day, starting 1/22/2008 10:40:00 AM 1/29/2008 10:39:00 AM 1/29/2008
SYSTEM INFORMATION
Product Edition: Standard
Version: 2.2.3
Tax Engine Version: 1.0.7
Tax Data Version: 20080101
Registration Key: 6ca35ce7ac1b44ace0686a3ecf90b4eb
Maintenance Jobs Last Ran: Never
CRON RESULTS
timetrex=> select * from cron;
id | status_id | name | minute | hour | day_of_month |
month | day_of_week | command | last_run_date
| created_date | created_by | updated_date | updated_by | deleted_date | deleted
_by | deleted
----+-----------+------------------------------+--------+------+--------------+-
------+-------------+----------------------------------+------------------------
+--------------+------------+--------------+------------+--------------+--------
----+---------
11 | 10 | TimeClockSync | * | * | * |
* | * | TimeClockSync.php |
| 1201025127 | | 1201025127 | | |
| 0
3 | 10 | calcExceptions | 30 | 0 | * |
* | * | calcExceptions.php | 2008-01-29 00:31:00-06
| 1201025117 | | 1201588205 | | |
| 0
7 | 10 | AddRecurringScheduleShift | 20,50 | * | * |
* | * | AddRecurringScheduleShift.php | 2008-01-29 10:20:00-06
| 1201025117 | | 1201623600 | | |
| 0
4 | 10 | AddRecurringPayStubAmendment | 45 | 0 | * |
* | * | AddRecurringPayStubAmendment.php | 2008-01-29 00:45:00-06
| 1201025117 | | 1201589100 | | |
| 0
5 | 10 | AddRecurringHoliday | 55 | 0 | * |
* | * | AddRecurringHoliday.php | 2008-01-29 00:56:00-06
| 1201025117 | | 1201589701 | | |
| 0
6 | 10 | UserCount | 15 | 1 | * |
* | * | UserCount.php | 2008-01-29 01:16:00-06
| 1201025117 | | 1201590901 | | |
| 0
9 | 10 | AddAccrualPolicyTime | 30 | 1 | * |
* | * | AddAccrualPolicyTime.php | 2008-01-29 01:31:00-06
| 1201025124 | | 1201591801 | | |
| 0
8 | 10 | CheckForUpdate | 20 | 23 | * |
* | * | CheckForUpdate.php | 2008-01-28 23:21:00-06
| 1201025117 | | 1201584006 | | |
| 0
1 | 10 | AddPayPeriod | 0 | 0 | * |
* | * | AddPayPeriod.php | 2008-01-29 00:01:00-06
| 1201025117 | | 1201586401 | | |
| 0
2 | 10 | AddUserDate | 15 | 0 | * |
* | * | AddUserDate.php | 2008-01-29 00:16:00-06
| 1201025117 | | 1201587301 | | |
| 0
10 | 10 | UpdateCurrencyRates | 45 | 1 | * |
* | * | UpdateCurrencyRates.php | 2008-01-29 01:46:00-06
| 1201025124 | | 1201592701 | | |
| 0
(11 rows)
TimeTrex maintenance jobs have not run in the last 48 hours
It looks like your maintenance jobs are in fact running as they should. I will pass this on to our developers and see if they can figure out why that message is still showing up for you, in the mean time I would just ignore the message, things should be working fine.
Did you install TimeTrex with the windows installer? If not, which database are you using?
Did you install TimeTrex with the windows installer? If not, which database are you using?
Can you please download this test version of TimeTrex and see if it fixes the issue for you:
http://www.timetrex.com/download/TimeTr ... taller.exe
It may take between 1-60minutes after you have completed the installation for the message to disappear.
http://www.timetrex.com/download/TimeTr ... taller.exe
It may take between 1-60minutes after you have completed the installation for the message to disappear.
I have the same problem...
I am also really really at a loss here......
I get the warning "WARNING: TimeTrex maintenance jobs have not run in the last 48hours. Please contact your TimeTrex administrator immediately."
I have downloaded the TimeTrex_Standard_Edition_v2.2.5-linux-installer.
but it didn't solve ...
The warning occurs after I changed the time and date to a date in the next month after the current pay period date .
I do that since I need to test TimeTrex before I customize it.
I want to see if wage and pay stub amendments settings also work for the next pay period.
but, like I have said, instead i get that such warning, and also, the status for the current pay period is "N/A"..
I am really really confuse.....
help me...
I am also really really at a loss here......
I get the warning "WARNING: TimeTrex maintenance jobs have not run in the last 48hours. Please contact your TimeTrex administrator immediately."
I have downloaded the TimeTrex_Standard_Edition_v2.2.5-linux-installer.
but it didn't solve ...
The warning occurs after I changed the time and date to a date in the next month after the current pay period date .
I do that since I need to test TimeTrex before I customize it.
I want to see if wage and pay stub amendments settings also work for the next pay period.
but, like I have said, instead i get that such warning, and also, the status for the current pay period is "N/A"..
I am really really confuse.....
help me...
If you manually change the date/time of the computer TimeTrex is on into the future (more then 24hrs) then you are circumventing TimeTrex's maintenance job functionality and it will cause all sorts of issues.
TimeTrex has to run certain jobs at certain times, but if you instantly change the time to be two weeks into the future, it didn't get a chance to run its maintenance jobs for those two weeks so things won't work properly.
TimeTrex has to run certain jobs at certain times, but if you instantly change the time to be two weeks into the future, it didn't get a chance to run its maintenance jobs for those two weeks so things won't work properly.