Timetracker by 7pace failed to load.Learn More about this extension, including available support options.
Officially AnsweredHello
We just installed the trial of timetracker since we urgently need a new solution. We have TFS 2015 update 4.0, no sharepoint, no analysis server. I did not find any documentation regarding software requirements or which features of TFS must be activated. Also the installer did not warn me about any deactivated TFS features.
After installation according to your documentation I receive the error message below when I try to navigate to the TIME tab in TFS web portal. We tried waiting, restarting server, different browser, always with the same results.
Thanks for your help
-
Hi Christian,
This kind of error usually means that you cannot reach Timetracker web application. To diagnose Timetracker availability just open it directly by the address you provided during installation. If Timetracker runs properly it should display empty page with text "Welcome to 7pace Timetracker".
Common issues:
- port is blocked by firewall
- certificate is not trusted and browser revokes connection
- address is not reachable from your PCMaxim
-
Ok, not solved. I can reach the service site of timetracker. It is of course telling me to open the TFS page instead. However when I navigate to TFS and open the Timetracker tab I get exactly the same error message. Port 8090 is definitely open and can be reached from our developer machines.
Long story short: what other ports need to be opened? If I try to use timetracker from the TFS machine itself it works... And my security departement will only open specific ports.
I also checked the installation Guide for network related information. Unfortunately I did not find anything regarding firewalls.
-
We are using HTTP, Edge and Firefox.
On Edge, when I open the Developer Tools and switch to the Network Tab, it shows a HTTP GET on >>>>http://dom.datagovernance.local:8080/tfs/DefaultCollection/DGPrototype/_apps/hub/7pace.TimetrackerOnPremises.TimeMonthly<<<< results in a 401 Unauthorized.
All other requests seem fine.
Sorry, we are no web developers :-) What does it mean?
-
This Ticket can be closed.
We had an internal configuration problem:
We entered just "dom" as hostname in the configuration of the timetracker. The name "dom" could however not be resolved from the development network, only inside the server network. We changed the configuration to the full "dom.datagovernance.local" and everything works.
Please sign in to leave a comment.
Comments
7 comments