I have a TFS 2013 system (with no updates) and am upgrading SharePoint from 2010 to 2013. The new SharePoint farm was up and running OK. It was constructed using AutoSPInstaller as far as the July 2014 CU and then patched to the Sept 2014 CU and is running on Windows 2012 R2. It is a simple farm, 2 web nodes and a separate database node, the same layout I used with 2010. I have also tried this with a single web node and there was no difference.
When I install TFS 2013 (without even configuring it) on any node in the farm if stops SharePoint from working correctly. By not working I specifically mean ASMX SharePoint services are broken for example http:://hostname/_vti_bin/Lists.asmx, the rest of SharePoint appears to be OK.
All the ASMX services return this error message...
startIndex cannot be larger than length of string.
Parameter name: startIndex
I have narrowed down the cause to the install of the aspnetwebpages2.msi that is run by the TFS installer, which causes the problem. Installing that onto SharePoint node on its own causes the damage and uninstalling it does not undo the damage. There is no obvious issues reported during the installation or configuration only by explicitly connecting to an ASMX web service do I see the problem. The lack of functioning web services means TFS can not create new projects and its Team Explorer cannot connect to SharePoint which is how I first spotted the problem.
I rolled everything back as this was in a virtual deployment and was considered a show stopper.
This question was originally asked on the TFS Admin forum and they suggested raising it here.