7pace Timetracker "taking longer than expected to load" questions

How to solve "Timetracker by 7pace failed to load" error?

Why am I seeing "Timetracker failed to load" after installation? (on-premise only)

Why am I seeing "Timetracker is taking longer than expected to load" and our browser's Dev console shows errors about DOM elements?

Why am I getting a "Timetracker is taking longer than expected to load" message and the 'Add time' dialog popup is displaying inconsistently? (on-premise only)

Question

I'm using DevOps Server over HTTPS  and am experiencing loading issues.

Timetracker pages show red notifications with text "TimetrackerOnPremises by 7pace failed to load":

In the browser console (F12), I receive the following error when I try to try to open the Timetracker address directly in my browser: "7pace.TimetrackerOnPremises.TimeMonthly:1 Mixed Content: The page at <_____> was loaded over HTTPS, but requested an insecure resource 'http://timetracker_url_'. This request has been blocked; the content must be served over HTTPS."

Answer

You are using DevOps Server over HTTPS, therefore, 7pace Timetracker needs to be configured over HTTPS as well. This is because Timetracker (and any other extension for DevOps Server) is located in the iframe, and browsers prevent HTTPS iframes from loading on pages with HTTPS.

Please go to the Timetracker Configuration Tool and change it so that the DevOps URL is the same for your end-users (it looks like this: https://TFS_URL/tfs/). After that, you should be asked to configure HTTPS binding for Timetracker and to select the SSL certificate. 

After these steps, 7pace Timetracker should load as expected.

Question (on-premise only)

After installing Timetracker, I received the message "Timetracker by 7pace failed to load" when I tried to navigate to the TIME tab in the DevOps Server web portal. We tried waiting, restarting the server, and using different browser - can you help?

Answer (on-premise only)

This kind of error usually means that you cannot reach the Timetracker web application. To diagnose Timetracker availability, just open it directly by the address you provided during installation. You can find your address in the 7pace Timetracker Configuration Tool:

If Timetracker runs properly, it should display an empty page with the following text: "Welcome to 7pace Timetracker".

Common issues:

• Port is blocked by firewall
• The Certificate is not trusted and the browser revokes connection
• The address is not reachable from your PC

Question

I'm seeing "Timetracker is taking longer than expected to load" messages. I looked in our browser's Dev console and see multiple errors about DOM elements. Can you help?

Answer

This can occur if your browser has some extensions or security settings that prevents the Referer header from being passed to iFrames. 7paceTimetracker relies on this header and expects that it is present when you open a page. Please check your browser settings and see if something is blocking this header (it can be settings in browser, ad-blocking extension or any script blocking extensions).

Question (on-premise only)

When loading any page of Timetracker for the first time I am receiving the following message: "Timetracker is taking longer than expected to load." If I don't use the page for awhile, it also takes some time to add "New Time", however, if I try to add a second time entry immediately, I can do so. Can you help?

Answer (on-premise only)

This kind of delay is usual for IIS-based applications and can depend on many factors in the system. Try one of the solutions, below, to see if it fixes your issue.

Step 1:

Ensure the Application Pools "Start Mode" is set to "Always Running".

1. Open IIS.
2. Open Application Pools list.
3. Select 7pace Timetracker App Pool.
4. Click the "Advanced Settings" button on the right panel (see screenshot, below).
5. In the resulting dialog box, ensure that the "Start Mode" setting is set to "Always Running".

Step 2:

Check the Application Pools' "Regular Time Interval" to ensure that it is recycling regularly. 

1. Referencing the screenshot, above, click "Advanced Settings".
2. Scroll down and check the "Regular Time Interval".

Step 3:

Change the "Idle Time-out" Setting to "0".

Sometimes, IIS can send the application to the background when it's not getting requests (even if "Always Running" is true). 

1. Referencing the first screenshot, above, click "Advanced Settings".
2. Scroll down and check the "Idle Time-out".
3. "Idle Time-out" is usually set to 20. Set it to "0".