Get command hangs using VS 2012 and TFS 2008 (TFS error TF400307)

Question

Today, all of a sudden, I found out I am not able to succesfully complete any type of get command on our TFS. All the time the process just hangs at some point, progress bar and status message with currently processed file staying the same forever, no errors thrown. This happens on a different file every time, sooner or later into the process with both the IDE and the command line utility.

I'm using Visual Studio Premium 2012 with TFS 2008.

I've never had a similar problem before and yesterday everything worked fine. I'm not aware of any configuration changes since then and I am the only one in the company experiencing the problem.

I don't suppose there is a direct answer to why this happens, but could someone provide any pointers on how to go about debugging and solving such issue?

So far I've tried various ways of running the get command - latest version, specific version, map + get latest, both inside VS IDE and via command line. Also many other TFS commands seem to be working well.

Edit:

After some trial and error, leaving the process going for an hour or so, I finally stumbled upon the error messages in the source control output window. These weren't visible initially, because when the process hanged, it made the whole IDE unresponsive. The messages are all the same:

[file path]: TF400307: The download operation timed out after waiting 599 seconds for a response from the server.

Answer 1

I was having the same issue with TFS where it would hang and become unresponsive.

I found a solution to this by updating the tf.exe.config or devenv.exe.config file with the following configuration values:

<system.net>
    <connectionManagement>
        <add address="*" maxconnection="1000"/>
    </connectionManagement>
</system.net>

I set the limit to 1000 on my side, as I carefully watched the value in Resource Monitor, though truthfully I never got higher than 600 concurrent connections.

Answer 2

So what happens is that TFS client in VS 2012 has a bug in it that causes it to start timeouting on all the files after some time into the process when running a get command for a bigger number of files.

As mentioned in the MS Connect ticket below, the workaround for now is to use the older TFS client to run the timeouting commands. I succesfully used the VS 2010 command line TFS client to do the get on the project.

• Microsoft Connect - Visual Studio: Get latest version fails with timeout