Visual Studio Team System 2010 Team Foundation Server Beta 1 Installation Problems

First of all, see my last post Visual Studio Team System 2010 Beta 1 Download Links for all the download links and installation docs. Also check out Brian Keller’s post on Using a download manager to quickly download Visual Studio 2010 Beta 1.

We greatly value your feedback. Please fill in the Visual Studio 2010 and .NET Framework 4 Beta 1 Survey and visit the Microsoft Connect Beta 1 Feedback page to submit a bug or a suggestion.

Also, the Microsoft Visual Studio Team Foundation Server 2010 Beta1 Forums are being tracked by the product team so that you can get help with your installation issues and share feedback.

If you don’t like forums, or you’d like to discuss TFS2010 with other people over email, you can also join the OzTFS.com mailing list for the latest buss.

The Readme File

In this post, I want to bring your attention to the Team Foundation Server Beta 1 Readme and the common gotchas I’ve seen people hit when installing TFS2010 Beta1.

These are the issues I’ve hit myself (because I didn’t read the readme…)

TF31001 "The ServicePointManager does not support proxies with the https scheme."

If you are trying to connect to a TFS server that is configured using HTTPS, then you might run into this issue.

See Aaron Block’s blog post for all the details.

On all machines:

reg add hklm\SOFTWARE\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

reg add hklm\SOFTWARE\Microsoft\TeamFoundationServer\10.0\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

Additionally on a 64-bit machine:

reg add hklm\SOFTWARE\Wow6432Node\Microsoft\TeamFoundationServer\10.0\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

reg add hklm\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\TeamFoundation\RequestSettings /v BypassProxyOnLocal /t REG_SZ /d False

Initial Configuration of Team Foundation Server Should be Run From MSI Program or by Command Line

Initial Team Foundation Server configuration fails on Windows SharePoint configuration if you access the Team Foundation Configuration Tool by clicking the link in the Team Foundation Administration Console instead of by launching Team Foundation Configuration Tool at the end of the installation phase.

To resolve this issue:

If you want to setup Windows SharePoint Server during Team Foundation Server configuration, you must launch the Team Foundation Server Configuration Tool by using one of the two following methods:

• Launch the Team Foundation Configuration Tool by selecting the check box at the end of the Team Foundation Server installation
• If you exited Team Foundation Server MSI program (setup.exe) without launching Team Foundation Configuration Tool, do not start the Administration Console from the Start menu item shortcut. Instead use following command line:

%programfiles%\Microsoft team foundation server 10.0\tools\tfsmgmt.exe configure

After Team Foundation Server has installed and configured Windows SharePoint, you can configure Team Foundation Server by using the Start menu to launch Team Foundation Server Administration Console.

If you don’t do this, then your SharePoint configuration will be broken and you’ll get a 404 on the SharePoint Administration site.

Team Foundation Server Name May Not Be Over 14 Characters

The name of the server running Team Foundation Server may not be over 14 characters.

To resolve this issue:

Use a valid NETBIOS name of 14 Characters or less for Team Foundation Server. Configuration fails if the name of the server running Team Foundation Server uses more than 14 characters.

TF50363: The following display name is not valid

This is due to a known bug in our upgrade scripts where in the Version Control db (TfsVersionControl) tbl_Identity table there exists one or more rows where the DisplayName field contains data that is not in the expected format of domain\username. 

If you hit this error, the workaround is to update the row and prefix the existing value with a dummy domain name like 'domain\'.

See Bryan Krieger’s blog post TFS 2010 Beta1 - Upgrade may fail with TF50363: The following display name is not valid.

Windows Server 2008 R2 RC & SQL Express

Although Windows Server 2008 R2 RC is not officially supported by this build, it is possible to get TFS running using a couple of workarounds. See Installing TFS 2010 on Windows Server 2008 R2 RC from the TFS Developer Support team.

I’ve also heard talking that that install will work OK with an odd error message, but SQL Express won’t run. Not sure on the details of this one. YMMV. It might need SQL Server 2008 SP1.

Visual Studio 2008 Compatibility with a Team Foundation Server 2010 server

We are planning a Forward Compat GDR for the VSTS 2008 SP1 client.  This set of features will allow the VSTS 2008 client users to have a good experience when connected to a TFS 2010 team project, but will not provide full 2010 functionality.

Things that you should know:

• Most admin functionality can only be performed from a new client.
  • For example, we block PCW from the 2008 client to the 2010 server.
  • We require the admin to have a 2010 client.
• In Work Item Tracking, we added hierarchy and other link types which the older client does not support.  The user experience is being improved with the GDR so the 2008 client user can distinguish which queries  are supported and which do you need the 2010 client for.
• Work Item Tracking, also has a new location for Reports with the addition of the Team Project Collection structure.  The GDR will allow the 2008 client to navigate to the new report location.
• Shared Documents, Process Guidance and the Project Portal locations can be configured so again we need the GDR to assist with the new navigation.
• Test Case Management is also being enabled in the 2008 client using the GDR.
• Version Control is improving the rename scenarios in the GDR.
• There are a bunch of error messages which will be more helpful as well.

Readme Topics

I know that people don’t read the Readme files (I’m guilty too) – so here are the headings from the Readme in the hope that you’ll at least browse these for potential issues first :)

• Installing
  • Upgrade Breaks Links on the SharePoint Products and Technology Portal
  • Some Visual Studio Team System 2010 Features Not Available After Upgrade
  • Initial Configuration of Team Foundation Server Should be Run From MSI Program or by Command Line
• Uninstalling
  • Need to uninstall TFS Object Model before uninstalling VSTS if installed from the web
• Product Issues
  • Managing Users on Upgraded Team Projects Might Result in Error TF50620
  • Cannot Install Team Foundation Build Service on Windows XP
  • Require SSL Option Not Supported
  • No Work Item Only View feature in Team System Web Access
  • You Can Only Associate a Single URL with a Team Project in Team Explorer
  • Team Foundation Server Service Account must be different then the account used for installing Team Foundation Server
  • Uninstall Team Explorer Does Not Remove Visual Studio Shell
  • Installing Team Foundation Server on a Windows Domain Requires a Live Connection to the Domain Controller
  • Team Foundation Server Name May Not Be Over 14 Characters
  • Do Not Launch Teamfoundation.msc Directly or Add to Microsoft Management Console (MMC)
  • Changes to Lab Management Network Location Tab Requires an IIS Reset
• Converters
  • VSSConverter.exe Not Supported
• Office Integration
  • Office Integration Requires Manual Installation of Office Primary Interop Assemblies (PIA) on Windows XP
  • Visual Studio Team System 2010 Installation Program Appears After You Launch Microsoft Project
• Process Templates and Team Project Portal
  • No Process Guidance Updates
  • Capability Maturity Model Integration (CMMI) 5.0 Process Template Incomplete
  • Remote Portal Running as Network Service Can Cause Broken Dashboards
• Reporting
  • Team Foundation Server Stops Collecting Reporting Data from the Team Project Collection
  • Team Foundation Server Reports Are Out-of-date After Install/Upgrade
  • Team Foundation Server Data Warehouse Custom Adapters Do Not Work
• Test Integration
  • No Test Steps, Repro Steps or Associated Automation Controls in Team System Web Access
• Compatibiltiy
  • Team Explorer 2008 or older client users can create new build definitions but they will not be able to edit them or to edit other, existing build definitions.
  • Team Explorer 2008 or older clients will be able to submit changes that affect gated build definitions, but they will not be prompted with the confirmation dialog and, if their check-in affects multiple gated definitions, it will fail.
  • Team Explorer 2008 or older clients will not be able to manage build resources using the “Manage Build Agents” dialog box.
  • Microsoft Project plan documents created using a Team Explorer 2010 client, break when opened from a Team Explorer 2008 or older client.
  • Navigation to non-default Shared Document, Project Portal and Process Guidance locations is broken for a Team Explorer 2008 SP1 or older clients.
  • Navigation to new Reports is not supported for a Team Explorer 2008 SP1 or older clients.
  • Work Item Tracking Queries with new functionality are not supported for a Team Explorer 2008 SP1 or older clients.
  • Rename in Version Control is not supported for Team Explorer 2008 SP1 or older clients.
  • Test Results Publishing is not supported for a Team Explorer 2008 SP1 or older clients.
  • How to connect to Team Explorer 2010 to Team Foundation Server 2008
  • How to connect a Team Explorer 2008 SP1 to a Team Foundation Server 2010 Server
  • Team Foundation Server 2010 administrative functions are only supported using Team Explorer 2010.