Our TFS Server has become unstable after going to Update 2 though the jury is out on this one (i.e. issues on Update 1 may have been under reported).
Microsoft (break fix support) have been working on the issues for more than 2 weeks and we are no closer to a resolution.
TFS 2013 Update 2 on Server 2012 R2
Symptoms :
W3wp.exe crashes
Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16496, time stamp: 0x52b3f283
Exception code: 0xc0020001
Fault offset: 0x0000000000005a88
Faulting process id: 0x1740
Faulting application start time: 0x01cf78b662bac513
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 82c37c7e-e4aa-11e3-80e5-005056866c74
Event 3081 Detailed Message: TF400850: The request context was not disposed by the caller. AspRequestContext[POSThttp://xxx-tfs01:8080/tfs/OOSA/Build/v4.0/BuildQueueService.asmx,
Event 3000 Detailed Message: TF30065: An unhandled exception occurred.
http://syd-tfs01:8080/tfs/OOSA/Build/v4.0/BuildQueueService.asmx [method: POST]
Generally build related however, others
Url:http://xxx-tfs01:8080/tfs/OOSA/VersionControl/v1.0/item.ashx?type
TFS going “offline” for some / new connections – A view of tasks running in IIS show things ticking over, bet it at a high CPU. A stop and start of IIS does NOT resolve issue, only a server reboot resolves. After the IIS restart it seems that the previous clients who were getting serviced are still being serviced.
Typical item client sees is a 500 based web request. This is what a build controller sees (not on TFS Server)
TFS server memory increased to 10G (on VM) which is plenty for 50 odd users, SQL pegged not to consume all memory. Most web references to these errors have been tried or where
not applicable.
Security shows no auth failures.
To me with the fact that IIS stop / restart (which drops all connections) does not fix, but a reboot does seems to suggest to me some IP / kernel level issue, or some weird AntiVirus action (awaiting av rule changes from corporate)
Many thanks and my undying gratitude if you can resolve!!