TimeTrex on site not updating

General support regarding TimeTrex, such as
configuring policies/taxes or processing payroll.
Post Reply
gregory
Posts: 102
Joined: Fri Oct 28, 2011 3:39 pm

TimeTrex on site not updating

Post by gregory »

Have 2 TimeTrex installations on same server in different directories and pointing to different databases. Both running on Ubuntu 16.04 with PHP 7.0.22. One instance updated fine to 11.0 the other is still on 10.7.2 even though it shows the Maintenance Job ran in the last 24 hours.

Is there an ini setting I should check?

Gregory
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: TimeTrex on site not updating

Post by shaunw »

Could be a myriad of different reasons, but the first things to check is that your timetrex.ini.php has:

Code: Select all

production = TRUE
but does not have any of the following:

Code: Select all

deployment_on_demand = TRUE

Code: Select all

disable_auto_upgrade = TRUE
gregory
Posts: 102
Joined: Fri Oct 28, 2011 3:39 pm

Re: TimeTrex on site not updating

Post by gregory »

Double checked and

production = TRUE

Other 2 variables do NOT show up in timetrex.ini.php file
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: TimeTrex on site not updating

Post by shaunw »

Please attach a copy of your TimeTrex log file for the last few days here, it might shed some more light on this.
gregory
Posts: 102
Joined: Fri Oct 28, 2011 3:39 pm

Re: TimeTrex on site not updating

Post by gregory »

Updated manually previously as had no time to debug. Issue continues. Here is relevant section of log:
DEBUG [L0923] [00033ms]: Install::checkPHPVersion(): Comparing with Version: 7.0.22-0ubuntu0.16.04.1
DEBUG [L0548] [00034ms]: TTi18n::chooseBestLocale(): Unable to find and set a locale.
DEBUG [L0187] [00034ms]: TTDate::setTimeZone(): TimeZone already set to: GMT
DEBUG [L0145] [00034ms]: [Function](): Version: 11.1.1 (PHP: v7.0.22-0ubuntu0.16.04.1) Edition: 10 Production: 1 Server: N/A Database: Type: postgres8 Name: plastex_timetrex Config: /var/www/html/xxxTT/includes/../timetrex.ini.php Demo
DEBUG [L0145] [00034ms]: [Function](): Mode: 0
DEBUG [L0165] [00034ms]: [Function](): Lock File: /tmp/xxxTT/UnAttended_Upgrade_2473014221.lock
DEBUG [L0084] [00034ms]: LockFile::getCurrentPID(): Current PID: 11086DEBUG [L0477] [00034ms]: [Function](): New version available, check current system requirements...
DEBUG [L0487] [00034ms]: [Function](): Checking if new version is available, current version: 11.1.1 Force: 0
DEBUG [L0234] [00037ms]: TimeTrexSoapClient::getPrimaryCompanyData(): ERROR: Primary company does not exist: 11e7e456-xxxxxxxxxxx
DEBUG [L0730] [00037ms]: [Function](): Already running latest version: 11.1.1
DEBUG [L2405] [00038ms]: Factory::isValid(): Calling Validate()
DEBUG [L0056] [00038ms] Array: SystemSettingFactory::isUniqueName(): Unique Name: auto_upgrade_failedstring(36) "6e080cc1-5fc7-4a62-06dd-000000000012"

Thanks
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: TimeTrex on site not updating

Post by shaunw »

The problem is this:
ERROR: Primary company does not exist
Unfortunately you have censored the ID, so I can't even suggest a quick solution, but in your timetrex.ini.php file, the "primary_company_id" must match the ID of your company in the "company" database table.
gregory
Posts: 102
Joined: Fri Oct 28, 2011 3:39 pm

Re: TimeTrex on site not updating

Post by gregory »

Worked and updated automatically to 11.1.3 from 11.1.2 . Now says there is a new version to download manually. Should it not continue automatically?

Also, where can we see the changes in the new version? Last available is for 11.1.0 . Changes may address some issues and if we see listed we can retest and not have to bother through the forum

Thanks.
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: TimeTrex on site not updating

Post by shaunw »

Yes, the auto-update should continue upgrading, and likely will if you give it another day or two.

Not all patch level releases (last digit in the version) get release notes due to the fact that they can be minor changes that might not warrant notifying all customers about.
Post Reply