Start by opening the 7pace Timetracker website direct link
Getting 500.19 error after opening the direct link
HTTP Error 500.30 - ASP.NET Core app failed to start
Checking the certificate being used for the 7pace Timetracker website
Checking the port on which the 7pace Timetracker website is hosted
Checking the Application Pool Start Mode
Checking the Application Pool recycling interval
Modifying the Application Pool Idle Time-out Setting
If you are receiving the message "Timetracker is taking longer than expected to load" when you try to navigate to the Time tab in the DevOps Server web portal after a fresh install or after you have made changes to your DevOps/TFS instance and reinstalled Timetracker, below you will find the steps to troubleshoot this issue.
Starting troubleshooting
Check that you are able to open the direct link for the 7pace Timetracker website URL. To find it, run the 7pace Timetracker Configuration Tool and copy the link that is listed under the Bindings field:
If Timetracker is running properly, it should display an empty page with the following text: "Welcome to 7pace Timetracker".
If this is the case, and you are still seeing the taking longer than expected to load message, then please contact us at support@7pace.com.
Possible scenario 1
If you are seeing a 500.19 error after opening the direct link, this indicates that the ASP.NET Core Runtime Hosting Bundle is not installed, or the incorrect version is installed. To resolve the issue, please see the Prerequisites for 7pace Timetracker and install the correct version of the ASP.NET Core Runtime Hosting Bundle.
After installing ASP.NET Core, try to open the direct link again. If ASP.NET Core missing was the cause of your issue, Timetracker should work now without problems.
Possible scenario 2
If you are seeing the following message:
"HTTP Error 500.30 - ASP.NET Core app failed to start"
Then check the Application event viewer logs on the server where Timetracker is installed and they should give you an indication for the reason for this issue. If you need assistance to resolve it, please contact us at support@7pace.com.
Possible scenario 3
Check the certificate that you are using for the 7pace Timetracker website. Whatever URL you have configured for Timetracker under the Bindings in the 7pace Timetracker Configuration Tool, this URL must be contained in the certificate, or should be covered by a wildcard certificate used with the website.
If you are seeing the below certificate error (depending on your browser) when navigating to any Timetracker page, then there is an issue with the certificate:
To check the certificate that is used with the Timetracker website, open IIS and select the 7pace Timetracker website under Sites (1). Then in the Edit Site section, click on Bindings (2). Here you will be able to see a list of the bindings for the website. Select the binding you are using and click on the Edit button (3). In the SSL certificate section click on the View button (4) and ensure that the Timetracker website URL is contained in the Subject field on the Details tab of the certificate (5):
Once the certificate is updated correctly, check the direct link once more and if you are able to open any Timetracker pages from DevOps.
Possible scenario 4
Ensure that only 7pace Timetracker is hosted on port 8080 in IIS, which is the default port for Timetracker.
To check if you have any other websites hosted on the same port as you are hosting 7pace Timetracker, open the 7pace Timetracker Configuration Tool and check which port is configured for the Timetracker website. Then, open your IIS (Internet Information Services) and check the hosted websites by selecting each website in the navigation panel under Sites, and ensuring that port 8080 is not occupied by any of them, or whatever port you are using for the 7pace Timetracker website in the Browse Website section. On the screenshot below you can see a misconfiguration where the Azure DevOps Server website is using port 8080, which prevents Timetracker from using it since this port is configured by default under the Timetracker Bindings:
Check the direct link once more and if you are able to open any Timetracker pages from DevOps.
Possible scenario 5
If none of the previously described scenarios are valid for you, then ensure that 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".
Possible scenario 6
If none of the previously described scenarios are valid for you, then check the Application Pools' "Regular Time Interval" to ensure that it is recycling regularly.
1. On the "Edit Application Pool" panel, click "Advanced Settings" (screenshot in Step x)
2. Scroll down and check the "Regular Time Interval".
Step 8
Change the "Idle Time-out" Setting to "0".
Sometimes, IIS can send the application to the background when it is not getting requests (even if "Always Running" is true).
1. On the Edit Application Pool panel, click "Advanced Settings". (screenshot in Step x)
2. Scroll down and check the "Idle Time-out".
3. "Idle Time-out" is usually set to 20. Set it to "0".
If you were not able to resolve your issue after following all of the steps described, then please reach out to us at support@7pace.com for assistance.
Comments
0 comments
Article is closed for comments.