Initializing forever after update.

Ask your questions regarding TimeTrex installation here.
Post Reply
robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Initializing forever after update.

Post by robh »

Hi,

Just updated to the latest version (v11.5.4-20190817) on a Windows 10 pc. Update went well without any issues but when Timetrex started up after the update I get an Initializing message which never finishes, see attachement.

Checked that both Timetrex services were running, and they are.

I tried to install the update once more, but got the same result.

When I try to connect to the server from a remote system the login page loads, I am allowed to log in, but then I get the Maintenance message.

Does anyone know how to fix this?

Best regards, Rob.
Attachments
Screendump.PNG
Screendump.PNG (270.54 KiB) Viewed 20166 times

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

Please replicate the error then attach your TimeTrex log file here, its usually found in c:\timetrex\log\timetrex.log
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Thanks for having a look at this!

Actually I just migrated the system to another pc to see if a clean install would help. But unfortunately I experienced the same problem.

I checked the log directory and it is empty. Do I need to activate a debug mode?

Best regards, Rob.

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

See #5 in the following FAQ: viewtopic.php?f=6&t=89

Also if you bring up the developer tools in your web browser when you see the error and take a screenshot of any errors displayed in the Javascript console or Network tabs that would also be helpful.
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Okay, I switched on logging in the ini file.

Did a re-install (now processed as an update) on the pc I migrated to. I got one error message which I do not get on the original pc, see attachement. After clicking it away the install proceeded without any issues. Attached also the log file. Hope it gives some clues.
Attachments
timetrex.log
(40.12 KiB) Downloaded 168 times
error 1.PNG
error 1.PNG (21.41 KiB) Viewed 20131 times

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

That error is with installing the Microsoft Visual C++ 2017 redistributable library, which is required to install/run the PostgreSQL and Apache services (among many other applications too). For it to fail there is likely something severely wrong with your Windows installation and without it TimeTrex definitely won't function. Which your TimeTrex error log confirms, because it is unable to connect to the PostgreSQL server as it appears to not be running.

Have you installed all recent Windows 10 updates by chance?
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Yes, totally updated Windows 10 Pro... Both Timetrex services were actually running.

I will repeat the re-install on the target pc and post the log file from that system soon. There was no Windows error message there.

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

This is the log file from the target system. No error messages while re-installing, but still the "initializing..." problem.
Attachments
timetrex.log
(92.02 KiB) Downloaded 164 times

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

Still the same error, unable to connect to the database server.

Code: Select all

pg_connect(): Unable to connect to PostgreSQL server: could not connect to server: Connection refused (0x0000274D/10061)
	Is the server running on host "localhost" (::1) and accepting
	TCP/IP connections on port 5433?
If the PostgreSQL service is in fact running, then its likely you have some firewall or anti-virus software installed that may be preventing such connections.
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Switched off firewall, still same problem.
Attached screendump showing services running.
No other AV installed, just Windows 10 built in AV. Any suggestions what I could try?
Attachments
Services running.PNG
Services running.PNG (22.83 KiB) Viewed 20122 times

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

Please confirm in the Task Manager that the PostgreSQL process is running.

If it is, open a Command Prompt window as an administrator and run:

Code: Select all

netstat /nat
Then copy and paste the entire output here please.
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Yes, that prosess is running, about 18 instances.

Here is the output of the commands:

_______________________________________________________________
Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. Med enerett.

C:\WINDOWS\system32>CODE: SELECT ALL
'CODE:' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>netstat /nat

Active Connections

Proto Local Address Foreign Address State Offload State

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5001 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5060 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5061 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5090 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:7070 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:7680 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:8085 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:49669 0.0.0.0:0 LISTENING InHost
TCP 0.0.0.0:49746 0.0.0.0:0 LISTENING InHost
TCP 10.0.0.16:139 0.0.0.0:0 LISTENING InHost
TCP 10.0.0.16:2869 10.0.0.1:44885 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44886 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44888 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44889 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44890 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44891 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44893 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44894 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44896 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44897 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44899 TIME_WAIT InHost
TCP 10.0.0.16:2869 10.0.0.1:44900 TIME_WAIT InHost
TCP 10.0.0.16:5060 10.0.0.12:5077 ESTABLISHED InHost
TCP 10.0.0.16:5060 10.0.0.13:5061 ESTABLISHED InHost
TCP 10.0.0.16:5060 10.0.0.14:5062 ESTABLISHED InHost
TCP 10.0.0.16:49699 144.76.103.6:80 ESTABLISHED InHost
TCP 10.0.0.16:49726 64.233.161.125:5222 ESTABLISHED InHost
TCP 10.0.0.16:49734 172.217.21.170:443 ESTABLISHED InHost
TCP 10.0.0.16:49740 40.67.254.36:443 ESTABLISHED InHost
TCP 10.0.0.16:49749 37.252.254.174:5938 ESTABLISHED InHost
TCP 10.0.0.16:49793 31.216.147.136:443 ESTABLISHED InHost
TCP 10.0.0.16:49795 31.216.147.136:443 ESTABLISHED InHost
TCP 10.0.0.16:49826 188.172.223.100:5938 ESTABLISHED InHost
TCP 10.0.0.16:49828 199.232.42.2:443 ESTABLISHED InHost
TCP 10.0.0.16:49836 108.177.14.188:5228 ESTABLISHED InHost
TCP 10.0.0.16:49911 40.115.3.210:443 TIME_WAIT InHost
TCP 10.0.0.16:49913 172.217.21.131:443 ESTABLISHED InHost
TCP 10.0.0.16:49914 172.217.22.174:80 ESTABLISHED InHost
TCP 10.0.0.16:49917 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49918 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49919 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49921 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49922 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49923 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49924 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49925 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49926 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49927 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49928 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49929 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49930 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49931 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49932 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49933 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49934 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49935 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49936 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49937 13.107.246.254:443 ESTABLISHED InHost
TCP 10.0.0.16:49938 204.79.197.222:443 ESTABLISHED InHost
TCP 10.0.0.16:49939 13.107.21.200:443 ESTABLISHED InHost
TCP 10.0.0.16:49940 13.107.21.200:443 ESTABLISHED InHost
TCP 10.0.0.16:49941 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49942 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49943 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49944 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49945 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49946 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49947 13.107.4.254:443 ESTABLISHED InHost
TCP 10.0.0.16:49948 204.79.197.254:443 ESTABLISHED InHost
TCP 10.0.0.16:49949 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49950 10.0.0.1:5431 TIME_WAIT InHost
TCP 10.0.0.16:49951 172.217.20.42:443 ESTABLISHED InHost
TCP 10.0.0.16:49952 172.217.20.42:443 ESTABLISHED InHost
TCP 10.0.0.16:49953 40.115.3.210:443 ESTABLISHED InHost
TCP 10.0.0.16:49955 13.78.168.230:443 TIME_WAIT InHost
TCP 10.0.0.16:49956 13.78.168.230:443 TIME_WAIT InHost
TCP 10.0.0.16:49958 52.114.158.53:443 TIME_WAIT InHost
TCP 10.0.0.16:49959 13.83.149.67:443 ESTABLISHED InHost
TCP 10.0.0.16:49960 8.254.229.249:80 ESTABLISHED InHost
TCP 127.0.0.1:1688 127.0.0.1:49954 TIME_WAIT InHost
TCP 127.0.0.1:5004 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5433 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5480 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5480 127.0.0.1:49701 ESTABLISHED InHost
TCP 127.0.0.1:5480 127.0.0.1:49706 ESTABLISHED InHost
TCP 127.0.0.1:5480 127.0.0.1:49708 ESTABLISHED InHost
TCP 127.0.0.1:5480 127.0.0.1:49768 ESTABLISHED InHost
TCP 127.0.0.1:5480 127.0.0.1:49771 ESTABLISHED InHost
TCP 127.0.0.1:5480 127.0.0.1:49772 ESTABLISHED InHost
TCP 127.0.0.1:5482 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5482 127.0.0.1:49753 ESTABLISHED InHost
TCP 127.0.0.1:5482 127.0.0.1:49754 ESTABLISHED InHost
TCP 127.0.0.1:5482 127.0.0.1:49755 ESTABLISHED InHost
TCP 127.0.0.1:5484 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5485 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5485 127.0.0.1:49741 ESTABLISHED InHost
TCP 127.0.0.1:5485 127.0.0.1:49742 ESTABLISHED InHost
TCP 127.0.0.1:5485 127.0.0.1:49743 ESTABLISHED InHost
TCP 127.0.0.1:5485 127.0.0.1:49750 ESTABLISHED InHost
TCP 127.0.0.1:5485 127.0.0.1:49752 ESTABLISHED InHost
TCP 127.0.0.1:5485 127.0.0.1:49758 ESTABLISHED InHost
TCP 127.0.0.1:5485 127.0.0.1:49767 ESTABLISHED InHost
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:5939 127.0.0.1:49757 ESTABLISHED InHost
TCP 127.0.0.1:5939 127.0.0.1:49834 ESTABLISHED InHost
TCP 127.0.0.1:6341 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:6342 0.0.0.0:0 LISTENING InHost
TCP 127.0.0.1:49701 127.0.0.1:5480 ESTABLISHED InHost
TCP 127.0.0.1:49706 127.0.0.1:5480 ESTABLISHED InHost
TCP 127.0.0.1:49708 127.0.0.1:5480 ESTABLISHED InHost
TCP 127.0.0.1:49741 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49742 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49743 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49750 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49752 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49753 127.0.0.1:5482 ESTABLISHED InHost
TCP 127.0.0.1:49754 127.0.0.1:5482 ESTABLISHED InHost
TCP 127.0.0.1:49755 127.0.0.1:5482 ESTABLISHED InHost
TCP 127.0.0.1:49757 127.0.0.1:5939 ESTABLISHED InHost
TCP 127.0.0.1:49758 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49767 127.0.0.1:5485 ESTABLISHED InHost
TCP 127.0.0.1:49768 127.0.0.1:5480 ESTABLISHED InHost
TCP 127.0.0.1:49771 127.0.0.1:5480 ESTABLISHED InHost
TCP 127.0.0.1:49772 127.0.0.1:5480 ESTABLISHED InHost
TCP 127.0.0.1:49834 127.0.0.1:5939 ESTABLISHED InHost
TCP [::]:135 [::]:0 LISTENING InHost
TCP [::]:445 [::]:0 LISTENING InHost
TCP [::]:2869 [::]:0 LISTENING InHost
TCP [::]:5000 [::]:0 LISTENING InHost
TCP [::]:5001 [::]:0 LISTENING InHost
TCP [::]:5060 [::]:0 LISTENING InHost
TCP [::]:5061 [::]:0 LISTENING InHost
TCP [::]:5090 [::]:0 LISTENING InHost
TCP [::]:5357 [::]:0 LISTENING InHost
TCP [::]:7680 [::]:0 LISTENING InHost
TCP [::]:8085 [::]:0 LISTENING InHost
TCP [::]:49664 [::]:0 LISTENING InHost
TCP [::]:49665 [::]:0 LISTENING InHost
TCP [::]:49666 [::]:0 LISTENING InHost
TCP [::]:49667 [::]:0 LISTENING InHost
TCP [::]:49669 [::]:0 LISTENING InHost
TCP [::]:49746 [::]:0 LISTENING InHost
TCP [::1]:5433 [::]:0 LISTENING InHost
TCP [::1]:5480 [::]:0 LISTENING InHost
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5050 *:*
UDP 0.0.0.0:5060 *:*
UDP 0.0.0.0:5090 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:49237 *:*
UDP 0.0.0.0:50001 *:*
UDP 0.0.0.0:52492 *:*
UDP 0.0.0.0:53523 *:*
UDP 0.0.0.0:63402 *:*
UDP 0.0.0.0:64804 *:*
UDP 10.0.0.16:137 *:*
UDP 10.0.0.16:138 *:*
UDP 10.0.0.16:1900 *:*
UDP 10.0.0.16:5353 *:*
UDP 10.0.0.16:63400 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:5063 *:*
UDP 127.0.0.1:5080 *:*
UDP 127.0.0.1:5483 *:*
UDP 127.0.0.1:5488 *:*
UDP 127.0.0.1:52497 *:*
UDP 127.0.0.1:52498 *:*
UDP 127.0.0.1:52499 *:*
UDP 127.0.0.1:52500 *:*
UDP 127.0.0.1:52501 *:*
UDP 127.0.0.1:52502 *:*
UDP 127.0.0.1:52503 *:*
UDP 127.0.0.1:52504 *:*
UDP 127.0.0.1:53323 *:*
UDP 127.0.0.1:53324 *:*
UDP 127.0.0.1:53325 *:*
UDP 127.0.0.1:53517 *:*
UDP 127.0.0.1:53518 *:*
UDP 127.0.0.1:53519 *:*
UDP 127.0.0.1:53532 *:*
UDP 127.0.0.1:53534 *:*
UDP 127.0.0.1:53535 *:*
UDP 127.0.0.1:54890 *:*
UDP 127.0.0.1:54891 *:*
UDP 127.0.0.1:54892 *:*
UDP 127.0.0.1:56282 *:*
UDP 127.0.0.1:56283 *:*
UDP 127.0.0.1:63401 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:4500 *:*
UDP [::]:5060 *:*
UDP [::]:5090 *:*
UDP [::]:5353 *:*
UDP [::]:5355 *:*
UDP [::]:49238 *:*
UDP [::]:52493 *:*
UDP [::]:63403 *:*
UDP [::1]:1900 *:*
UDP [::1]:5353 *:*
UDP [::1]:55393 *:*
UDP [::1]:56284 *:*
UDP [::1]:63399 *:*
UDP [fe80::54f0:d5e3:4b1:5a3c%13]:1900 *:*
UDP [fe80::54f0:d5e3:4b1:5a3c%13]:63398 *:*

C:\WINDOWS\system32>
_______________________________________________________________

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

In the mean time I installed the previous version of Timetrex, v11.5.3, but that fails in the same way and it was working before. So this is not a version issue as far as I can see.

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Problem solved. :D

It was caused by the web browser. I use Opera and it has a built in Ad blocker. After switching off the Ad blocker I got passed the Initializing phase.

Anyway thanks for looking at this.

Best regards, Rob.

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

I don't see how a adblocker in the web browser would have any effect on TimeTrex being able to connect to its database, since the web browser has nothing to do with that. Its likely something else you changed that corrected the issue.
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Here is what I did:
On the system with the freshly installed Timetrex it failed using the Opera browser, stuck in "Initializing".
I closed Opera.
I changed default browser to Microsoft Edge.
I ran the "TimeTrex Community Edition On-Site Installer" shortcut.
It opened in Edge and got passed the Initializing message. Now I got the the Install Wizard.
I closed Edge.
I changed the default browser back to Opera.
Opened Opera and switched off Ad blocker and closed it again.
I ran the "TimeTrex Community Edition On-Site Installer" shortcut.
It opened in Opera but now got beyond the Initializing message, and also here the install wizard came up.
I did no other changes.
Then I tested on the target system with the same results. All I had to do was switching off the built in Ad blocker.
The system is up and running now.

I am quit sure you can recreate this yourself if you want to test this. I am using the latest version of Opera Developer.

mikeb
Posts: 609
Joined: Thu Jul 27, 2006 11:58 am

Re: Initializing forever after update.

Post by mikeb »

I installed Opera Developer version: 64.0.3416.0 on a fully updated Windows 10 instance, made it my default web browser, enabled the ad blocker (since it doesn't appear to be by default) and was able to replicate at least one of the problems where I see a "Initializing" on the screen without any formatting whatsoever.

For some reason the adblocker is erroneously blocking all CSS/JS/Images from the "localhost" domain. TimeTrex doesn't contain any ads whatsoever, but not sure why Opera's adblocker is using such a big stick to block 99% of resources its trying to load. In the address bar of the browser If you replace "localhost" with "127.0.0.1" it loads just fine.

I wasn't able to replicate the "vcredist" or the PostgreSQL connection errors in your log file though, which is what is confusing things for sure.
TimeTrex Community Edition is developed and supported by volunteers.
Help motivate us to continue by showing your appreciation!

robh
Posts: 24
Joined: Mon Nov 07, 2016 3:49 pm

Re: Initializing forever after update.

Post by robh »

Thanks for testing this. I will send some info to Opera.

Post Reply