We’ve launched a new Help Center!

Visit the new Documentation space for Azure DevOps, monday.com, and Jira. Or, if you require any assistance or have any questions, please visit the new Customer Support Portal for Azure DevOps, monday.com and Jira.

On-Prem Windows error event log - HTTP status of response is not 200

Officially Answered

Comments

11 comments

  • Avatar
    7pace tech support

    Hi Dan, 

    Can you please send version of Timetracker you have installed? We had this issue with logging too much and it was fixed in latest versions. 

     

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    My bad, I should have included this.

    4.5.6.17881

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Interesting, 

    It should be fixed long time ago and we do not have indications that it is still present.

    Are all these log entries new? 

    You can just delete all such entries from you event log.

     

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    We have now updated to the latest version. 

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    We have had 10 occurrences this morning.

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Ok, I will check it with the team this and post update here.

     

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    Ok thanks.

    We are running TFS2018.1

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    I also ran into an issue when applying the latest release. The IIS applicaiton pool used by the timetracker application was not set to the TFS service account I had input, so it could not connect to the database. I have adjusted this.

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    Now we can't export times from the budgets tab and seeing a lot of 500 errors in the windows event logs. The browser client throws the following error:

    WebSocket connection to 'ws://servername:8090/internalSignalr/connect?transport=webSockets&clientProtocol=1.5&Bearer=xxx&collectionName=collectionname&connectionToken=token&connectionData=%5B%7B%22name%22%3A%22trackinghub%2Fv2.1%22%7D%5D&tid=1' failed: HTTP Authentication failed; no valid credentials available

    I've de-identified a bunch of the data in the error. This is now a critical issue as its stopping us from performing daily tasks.

    0
    Comment actions Permalink
  • Avatar
    Dan Kellett

    We performed a repair on the install that resolved the websocket issue.

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Hi!

    Could you please provide the version of Timetracker that you are using?

    You could check it at Configuration page->About.

    Because this Event log entry was filtered in Timetracker 4.7.0

    Regards,

    Andarth

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk