If you're reading this page chances are you've hit a roadbloack install Team Foundation Server. You're not alone. A quick search on MSDN will reveal a large number of unsolved questions. Fortunately, I've got a few answers. First off, the documentation is horrible. There are missing steps and incorrect information throughout. Add to that a setup experience akin to hugging a rabid bear and its no wonder people get upset. Funny enough, the TFS team realizes they have issues. Onto the errors and possible resolutions.

Error 28940 - TFServerStatusValidator: The tool could not call the Team Foundation Server ServerStatus Web service.
Open your browser and navigate to http://SERVER:PORT/services/v1.0/serverstatus.asmx. Replace SERVER and PORT with the name and port number of your TFS site. You should see the server status screen. If not, remove your Internet Explorer proxy settings and click retry.

Error 28805 - The setup program cannot complete the request to the server that is running SQL Server Reporting Services.
Despite what the documentation says, you need to configure SQL Report Services to run with the account you are using to run your TFS services. In the Reporting Services Configuration Tool under the Database Setup tab, ensure that you have it set to use Windows credentials.

TF220034 - The default URL for Windows SharePoint Services could not be found at the following location
This error appears during setup when you're configuring an existing SharePoint site to host your TFS sites. Aside from the obvious (check your spelling, correct URL, etc), the best course of action is to let TFS setup install SharePoint for you. Also, be sure that the "Default Web Site" exists on your IIS server. This will cause issues with Reporting Services as well as TFS installs. The best advice I can offer is to use a fresh IIS install and let TFS setup install and configure SharePoint for you. This is a very common issue with TFS. Yet another thing the team needs to work on.

Error TF31001 - Team Foundation cannot retrieve the list of team projects from the Team Foundation Server

1. This errors occurs when you attempt to connect to the Team Foundation Server from within Visual Studio. If you look at the entire message, you'll also notice a 503 Service Unavailable message. If you're using a proxy server, you either need to remove those settings from Internet Explorer or use the following registry entry to force Visual Studio to bypass the proxy.

Error TF30177 - Team Project Creation Failed.
This appears to be a generic error code. The details of the error message are contained in the box below. Here's some I've run across:

• TF30171 with TF30222 - The New Team Project Wizard could not find the data source TfsOlapReportDS on the SQL Server Reporting Services server <SERVERNAME>. You need to broswe to http://<SERVERNAME>/Reports the SQL Server Reporting Services server (usually the application tier). Click new data source. For TfsOlapReportDS: -Connection Type: Microsoft SQL Server Analysis Services -Connection String: Data source=DataTierMachineNameGoesHere;initial catalog=TFSWarehouse -Credentials: Use "Credentials stored in the report server". Specify the service account and its password and check the first check box: "Use as Windows credentials when connecting to the data source" For TfsReportDS: -Everything is the same except the Connection type which should be set to Microsoft SQL Server.

General Suggestions

• Use Windows Credentials for the SQL Server Reporting Services instead of Network Service
• You need to install at least Service Pack 1
• Do not run the configuration wizard after the install
• You must have the "Default Web Site" setup in IIS. I'd recommend using a fresh install of IIS without any lockdown.
• Install Windows SharePoint Services using the Team Foundation Server setup. It will greatly simplify the installation.
• Remove any proxy settings in Internet Explorer. The setup app doesn't seem to play nice with them.