Connection between Client and Server forbidden

Implemented

Comments

12 comments

  • Avatar
    Maxim

    Hi Carsten,

    Are you using Timetracker for TFS or VSTS?

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Hi Maxim,

     

    I'm preparing our move from TFS 2017 to TFS 2018.

    I use the RTM Version of TFS 2018.

     

    Carsten

     

     

    0
    Comment actions Permalink
  • Avatar
    Maxim

    Carsten,

    Do you have Timetracker previously installed?

    Could you please give us some additional info:
    1) Are you using the same user account in the Timetracker client as you use for TFS?
    2) If you are using Login/Pass, do you enter Domain name?
    3) Could you please check if you previous user was not cached in Credential Manager? If cached, can you delete them for Timetracker?


    Maxim

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Do you have Timetracker previously installed?

    - on the server side I installed Version 4.0 and yesterday 4.1.1.16784
    - I had the Problem in every Version

    1) Are you using the same user account in the Timetracker client as you use for TFS?

    2) If you are using Login/Pass, do you enter Domain Name?

    -  We are using single sign on with our domain accoutns on each machine
    - I used the preproduction option for the installation of TFS2018. This changed some internal keys in the TFS-Databases.
    - Have this key changes any Impact?

    3) Could you please check if you previous user was not cached in Credential Manager? If cached, can you delete them for Timetracker?

    I removed all saved credentials to the new server, but there is no Change

     

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Found this error message on the server side (event log) if the paring fails:

     
    Response 403.0 from Timetracker server.
     

     

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Hi Maxim,

     

    are there any updates on this Topic?

    Do you Need further Information?

     

     

    0
    Comment actions Permalink
  • Avatar
    Maxim

    Hi Carsten, 

    We are working on identifying this issue. 

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

     Hi,

    I'm back at work.

    Installed the newest version 4.5.6.17881, but the error still exists.
    All Clients have this problem, so I think the issue is located on the server side.

    Best Regards

    Carsten

     

     

     

     

    0
    Comment actions Permalink
  • Avatar
    dev

    Hi Carsten, 

    Could you please run this API request to Timetracker and provide results here?

    http://{your_server_and_port}/api/DefaultCollection/tracking/client/latest/1?api-version=2.1

    Please change {your_server_and_port} with your own server and port which could be found in Bindings section in Configuration Tool?

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Hi,

    my configuration is:


    result for both collections, if it matters

    Best regards

    Carsten

     

     

    0
    Comment actions Permalink
  • Avatar
    Carsten Scheel

    Hi,

    with Version 4.7 it's only a problem with one client machine.
    All other known clients are working.

    I think we can close the ticket.

     

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Hi!

    We've created a Zendesk ticket to help you to solve the problem with this client machine.

    Kind regards,

    Andarth

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk