Problem with multiple simultaneous downloads from TFS 2005 Version Control
-
Tuesday, November 01, 2011 11:05 PM
We are using TFS 2005 on a server with SQL Server V2005.
Our clients are generally using VS 2010 without significant problems.
We have multiple build machines that use Cruise Control to pull the source from TFS and perform the builds. This happens when Cruise Control detects that appropriate changes have been checked in.
When one of these builds fires off, it virtually alwasy succeeds in getting the source code from TFS and performing the build. However, when two of our builds start simultaineously, there is a good chance that they will both fail to get the source from TFS without errors (they are extracting the same source tree.
On the client side, we see one or more errors like this:
--------------------------------
c:\TestSuiteRoot\src\Source\Common\UI\Views\VariableGroupEditor\VariableEditFlagsEditor.cs.resx: TF30063: You are not authorized to access Microsoft-IIS/6.0.
-------------------------------
There are a handful of these errors, referencing a random set of files (out of the hundreds or thousands of files in our source). Both builds have errors, but they reference different source files.
On the server side, the system event log has errors of this form:
--------------------------
TransmitFile failed. File Name: C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControl\Data\841c4190-df68-4524-95ab-1f54fe15c01a\5E\0BFE5E, HRESULT: 0x80070020
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------
I have found some issues in various forums that pointed to problems like this if the TFS server cache is too small. We freed up space and adjusted the server cache configuration. Currently the cache size is about 6 Gb, the free disk space is 10 Gb, and the cache is told to cap itself at 50% of the free disk space. So, this shouldn't be a problem.
(The two build machines are actually virtual machines on the same VMWare server. I'm not sure if that is important or not.)
Dave Tillman
