Quantcast
Channel: Team Foundation Server - General forum
Viewing all articles
Browse latest Browse all 6687

Random, odd behavior in TFS.

$
0
0

It started out as random session timeouts for random people. This started after upgrading TFS 2015U1 to U3.

Things I’ve done:

Cleaned up two erroneous IPs that were on the server that never should have been there.

Cleaned up Corporate DNS records that were referencing bad IPs for the server.

Upgraded TFS 2015U3 to TFS 2017

Upgraded SQL to 2016 Standard from 2014 Express.

Moved some of the project databases to the same instance as the TFS Configuration database, and cleared the TFS cache directory.

Timeout tweaks.

Did a repair install on TFS.

Worked with the networking team to see if they’re noticing any traffic issues, but when they worked with Jeremy Ford, actual connectivity to the server was never lost, just HTTP traffic.

The server is far from being taxed.

 Now we're getting "The required anti-forgery cookie "__RequestVerificationToken_L3Rmcw2" is not present, and form and something cookie are mismatched.

Also, the "Assigned to me" query starts running as the first person to log in to TFS instead of the person actually running it even though the criteria is @me.

Any help is appreciated.


Viewing all articles
Browse latest Browse all 6687

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>