Team Foundation Server source control upload files fails - by jmatthewsr

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 549034 Comments
Status Resolved Workarounds
Type Bug Repros 1
Opened 4/6/2010 7:51:12 AM
Access Restriction Public


Initially I posted this to the msdn forums, but want to make sure it is tracked as an issue here (see link below to forum).

Trying to add a large project (3000 files) to TFS 2010 RC using Visual Studio 2010 Ultimate RC.  After the first few items the "Add Progress" dialog appears to be stalled on a file and does not go on to the next file.  If I try again it will stall at a different file, but always within the first few files sent. 

No TCP data is being sent to the server and eventually Visual Studio shows an error dialog: "The underyling connection was closed. A connection that was expected to be kept alive was closed by the server."

Some additional information: 

* The problem occurs on a Windows 7 64-bit computer running Visual Studio 2010 RC Ultimate

* Running Team Explorer 2010 RC on a Windows XP x86 system (connecting to the same server setup), the same source control operation succeeds without errors (uploading/adding 3,000+ files). 

* Both client test machines (Windows XP x86 and Windows 7 x64) are on the same gigabit switch as the Hyper-V server that has the Win2k8 R2 x64 Guest OS 

*A "Get All" from the Windows 7 x64 client appears to be working as the file progress dialog is updating the files retrieved, but it is much slower than the Windows XP client.  The Windows XP client finishes an initial get all in < 1 minute, where the Windows 7 x64 client takes over 5 min, at which point I cancelled it. 

Windows Server 2008 x64 Hyper-V
    - Windows Server 2008 R2 x64 (Guest OS)
              * TFS 2010 RC x64
              * SQL Server 2008 standard sp1 x64
              * IIS

Sign in to post a comment.
Posted by jmatthewsr on 4/13/2010 at 4:33 PM
It appears that this was due Nod32 antivirus software's "Web Access Protection" feature. Using nod32 version 4. Disabling the "Web Access Protection" or excluding the IP's and FQDN's that point to the TFS solved this issue.
Posted by Microsoft on 4/6/2010 at 11:00 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you