Visual Studio Client connection issues after upgrading to TFS 2010

There are two Visual Studio client connection issues you may encounter under specific scenarios after upgrading to Team Foundation Server 2010. In both these scenarios customers must have upgraded to TFS 2010 and configured the system to use the same URL as their previous TFS 2005 or TFS 2008 instance. (Note: Customers could have configured the system to use the same URL by either clearing the “VDIR” input field when completing the TFS Upgrade Wizard or by using a CNAME mapping to connect to TFS)

Scenario 1: For the first 2 hours after the upgrade, check-ins will fail from any Visual Studio client. On Visual Studio 2010 clients check-ins will work after waiting 2 hours after the upgrade completes. On Visual Studio 2005 and Visual Studio 2008 clients you must stop and restart the Visual Studio client after the 2 hour window to enable check-ins to work again. An alternative workaround (if you do not want to wait the 2 hours) is to delete the client side cache directory and restart Visual Studio. See below for instructions for deleting the client side cache directory.

Scenario 2: If customers have a configuration that uses a TFS Proxy server, Visual Studio 2005 and Visual Studio 2008 clients will fail to take advantage of the proxy and go directly to Team Foundation Application Tier until their client side cache directory is recreated. The workaround is to delete the client side cache directory and restart Visual Studio.

(Note: If you are using either TFS Proxy Server from TFS 2005 or TFS 2008 you must also restart the proxy server after the upgrade completes on the TFS 2010 Application Tier. We do recommend that you upgrade proxy servers to the TFS 2010 RTM version.)

To delete the client side cache directory on the client machine:

1. Exit Visual Studio

2. Open a command window and navigate to the folder: "%localappdata%\Microsoft\Team Foundation\” (Note: For Windows Server 2003 navigate to \Documents and Settings\ <user> \Local Settings\Application Data\Microsoft\Team Foundation folder)

3. For Visual Studio 2010 clients navigate to the sub folder: “3.0” and delete the sub folder “cache” and its contents

Or

For Visual Studio 2008 clients navigate to the sub folder: “2.0” and delete the sub folder “cache” and its contents

Or

For Visual Studio 2005 clients navigate to the sub folder: “1.0” and delete the sub folder “cache” and its contents

4. Restart Visual Studio and connect to TFS.

Comments

• Anonymous
  April 29, 2010
  Hi,I have a question for this scenario. Even if you clear the VirtualDirectoryName in the upgrade, wouldn't the selection of the project colleciton name force a new URL (it would not be the same as TFS 2008)?Thanks
• Anonymous
  March 07, 2011
  I tried this and I still get the same problem.We just moved the database from one server to another server over the weekend.  Now I can't view any of my work items from a browser.