mhunt
(MHunt)
1
I’ll try to ask the best question I can here, as I have had an issue dropped into my lap which I have no idea where to begin with.
Not really certain where to post this either!
Our TFS server has started rejecting previously working credentials from our Dev team. Initially we thought it was affecting users who had changed their AD password, but it seems that it has also affected users who have not yet changed that password.
We have 2 symptoms currently:
The server was updated over a month ago and has been working properly until this week, as far as I can tell no changes have been made to the AD (I have netwrix free AD monitoring tool, the only change to anything Dev related was to add a new staff member to their groups).
There don’t appear to be any reports of the authentication issue.
I can find reference to the text/html issue, though only for much older versions of TFS which don’t appear to be relevant.
Any guidance would be very much appreciated.
1 Spice up
Do you have a Certificate Authority issued Root certificate the has expired? I have seen this behavior triggered by a missing or expired Root cert. And it can seem erratic to the user.
Good luck!
mhunt
(MHunt)
3
Thanks, We are going to add that the the checklist.
mhunt
(MHunt)
4
Apparently no certificates expired recently and despite my best efforts I can’t even get a copy of the actual error message!
Backburnered.
Not long ago, I spent a great deal of time moving a TFS installation to a new server and know well some of the pitfalls. That is one of the primary reasons I have held off with an upgrade. It isn’t always smooth sailing.
Another thought is Visual Studio itself, provided you are using VS as the primary IDE where users are checking in their code. Have I assumed correctly?
One thing I have noticed is that when a user changes their AD password and and also has an O365 based email account (not necessarily synced with the onsite AD), there can cause some auth issues from within the VS app. For example, a user may have to refresh the VS creds upon changing their internal AD password.
Do you have a pulse on which users are being impacted? Say, 2 out of 20> Or maybe half of the total user base? Or does it seem to be a moving target?
Are you able to create a new test user and watch the login behavior?
Keep me posted and continued good luck!
mhunt
(MHunt)
6
One of the errors:
(Paraphrased from a french email our dev sent)
Received when the user tries to perform a “gated check in”

The client “then” asks for credentials and user provided credentials don’t work
Nothing then works until VS is restarted
It is not always the same file that causes the error
The issue is present in VX 2015 Update 1 and VS 2013 Update 5
What do you think?
@systemsadministrator1446
Can you verify that MahApps.Metro is installed on VS where the user(s) are having the issue? And verify that the version matched the error code. I wonder if you removed MahApps.Metro and installed it again via Package Manager, would that change the behavior.
mhunt
(MHunt)
8
They reinstalled the package, and report it seems to be hanging on a different file.
He also commented that he "simply removed the dll to see if [my] checking would pass without that reference at all.
I suspect that is the screenshot provided to me.

What do you think?