Page 2 of 2

Re: Install setup URL

Posted: Tue Oct 23, 2018 10:56 am
by mikeb
What is the 1 quick popup that you see?

Re: Install setup URL

Posted: Tue Oct 23, 2018 1:06 pm
by dhananjay
TimeTrex_Community_Edition_v11.3.0-windows-installer shows up under background processes

the pop up is the splash screen for TimeTrex but then there's no active window or anything else that seems like it's doing anything for a while.

It took a while for the next active window to come up. The BitRock installer also seems to take a while at the prompt for the web server port screen (default 8085).

still getting the error 500 pop up after installation of 11.3.0 when it goes to

Code: Select all

http://localhost:8085/interface/html5/index.php?installer=1&disable_db=1&external_installer=0#!m=Install&a=license&external_installer=0

Re: Install setup URL

Posted: Tue Oct 23, 2018 1:58 pm
by mikeb
Could you attach your Apache error log and check the Windows Event Viewer for any other crash details please?

Re: Install setup URL

Posted: Thu Nov 22, 2018 9:04 pm
by dhananjay
event viewer shows an application error with details below, also attaching the file C:\TimeTrex\apache2\logs\error.log :

Faulting application name: php-win.exe, version: 7.2.11.0, time stamp: 0x5bbd66b7
Faulting module name: ntdll.dll, version: 10.0.17134.228, time stamp: 0x2c71c7b8
Exception code: 0xc0000409
Fault offset: 0x0007ea40
Faulting process id: 0x3228
Faulting application start time: 0x01d482e0b9dac2aa
Faulting application path: C:\TimeTrex\php\php-win.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b82b0b1a-306c-4c33-818d-e96c0a53efd9
Faulting package full name:
Faulting package-relative application ID:

Re: Install setup URL

Posted: Fri Nov 23, 2018 9:44 am
by mikeb
Can you try installing both of the following Microsoft Visual C++ Redistributable packages to see if that makes any difference:

https://aka.ms/vs/15/release/VC_redist.x86.exe
https://aka.ms/vs/15/release/VC_redist.x64.exe

Re: Install setup URL

Posted: Fri Nov 23, 2018 11:54 am
by dhananjay
just install these two packages? do I need to reboot or re-install before or after installing these packages?

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:11 pm
by dhananjay
seems to have worked.
  • installed both redistributable packages for x86 & x64
    rebooted
    went to

    Code: Select all

    http://localhost:8085/interface/html5/index.php?installer=1&disable_db=1&external_installer=0#!m=Install&a=license&external_installer=0

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:19 pm
by dhananjay
tried running the following php scripts in TimeTrex\timetrex\maint\ directory from command line

Code: Select all


php-win.exe cron.php
php-win.exe MiscDaily.php
php-win.exe MiscWeekly.php

I'm still missing a few weeks of pay periods from showing up in the payroll tab after running the scripts to update the tables.

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:24 pm
by mikeb
If you run the following command once for each pay period that you are missing, they should be created:

Code: Select all

php-win.exe AddPayPeriod.php

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:27 pm
by dhananjay
should I manually assign dates to pay periods?

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:30 pm
by mikeb
dhananjay wrote: Fri Nov 23, 2018 12:27 pm should I manually assign dates to pay periods?
I wouldn't recommend it, because if your dates are off by even 1 second it will prevent TimeTrex from ever being able to automatically creating pay periods for you again, due to conflicts.

TimeTrex will automatically "catch up", however by default it only creates one pay period per day, or each time the AddPayPeriod maintenance job is run. So if you are 6 pay periods behind, simply run the following command 6x and you will be caught up instantly:

Code: Select all

php-win.exe AddPayPeriod.php

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:33 pm
by dhananjay
sorry
dhananjay wrote: Fri Nov 23, 2018 12:27 pm should I manually assign dates to pay periods?
posted before a refresh where I saw your answer
mikeb wrote: Fri Nov 23, 2018 12:24 pm If you run the following command once for each pay period that you are missing, they should be created:

Code: Select all

php-win.exe AddPayPeriod.php
wouldn't cron.php, MiscDaily.php, or MiscWeekly.php already done that? will I have to continue to manually add the pay periods?

Re: Install setup URL

Posted: Fri Nov 23, 2018 12:34 pm
by dhananjay
gotcha! thanks! didn't mean to clutter the thread
mikeb wrote: Fri Nov 23, 2018 12:30 pm
dhananjay wrote: Fri Nov 23, 2018 12:27 pm should I manually assign dates to pay periods?
I wouldn't recommend it, because if your dates are off by even 1 second it will prevent TimeTrex from ever being able to automatically creating pay periods for you again, due to conflicts.

TimeTrex will automatically "catch up", however by default it only creates one pay period per day, or each time the AddPayPeriod maintenance job is run. So if you are 6 pay periods behind, simply run the following command 6x and you will be caught up instantly:

Code: Select all

php-win.exe AddPayPeriod.php

Re: Install setup URL

Posted: Sun Feb 24, 2019 4:33 pm
by dhananjay
MikeB,

trying to start up timetrex again, win10 may have had some automatic updates since last time timetrex started (note 100% sure, but most likely).

Getting Internal Server Error message again. Should I try to re-install timetrex? if so, which version?

Thanks

Re: Install setup URL

Posted: Mon Feb 25, 2019 9:00 am
by mikeb
You really shouldn't need to re-install TimeTrex again. Can you check your Windows update history to see what updates were applied?

Also are you able to login to TimeTrex at all, or are you always getting an error?

Re: Install setup URL

Posted: Wed Feb 27, 2019 8:49 am
by dhananjay
cannot login to timetrex at all. won't show the login screen, directly 500 Internal Server Error.


runnning updates now, will have to wait to see which other updates added. It's on Win10 build 1803

Re: Install setup URL

Posted: Wed Feb 27, 2019 10:06 am
by mikeb
Please check your error logs as you did in previous posts and attach them here.