Red Gate forums :: View topic - Commit problem with TFS
Return to RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Source Control 2
SQL Source Control 2 forum

Commit problem with TFS

Search in SQL Source Control 2 forum
Post new topic   Reply to topic
Jump to:  
Author Message

Joined: 06 Dec 2011
Posts: 4

PostPosted: Tue Dec 06, 2011 10:32 pm    Post subject: Commit problem with TFS Reply with quote

I'm having a problem setting up Source Control v2.2 with Team Foundation Server 2010. After linking a database, when I try to commit the changes for the first time, I get an error that the underlying connection was closed. If I try to commit a small number of changes (3 - 5 files), it works fine.

Here is the Event Viewer output:
Event Type: Error
Event Source: SQL Source Control 2
Event Category: None
Event ID: 32
Date: 12/6/2011
Time: 9:28:41 AM
User: N/A
ProgressTask:Not reporting error
Microsoft.TeamFoundation.VersionControl.Client.VersionControlException: C:\Documents and Settings\user\Local Settings\Application Data\Red Gate\SQL Source Control 2\WorkingBases\rapm2klt.pyq\Functions\contacts.ufn_Implode_PrimaryAddress.sql: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.TeamFoundation.VersionControl.Client.FileUploader.UploadChunk(FileStream fileContentStream, Int64 end)
--- End of inner exception stack trace ---
at Microsoft.TeamFoundation.VersionControl.Client.Workspace.UploadChanges(IEnumerable`1 changes, OnProcessingChangeDelegate onPendingMethod)
at Microsoft.TeamFoundation.VersionControl.Client.Workspace.CheckInInternal(WorkspaceCheckInParameters parameters)
at Microsoft.TeamFoundation.VersionControl.Client.Workspace.CheckIn(WorkspaceCheckInParameters checkinParameters)
at Microsoft.TeamFoundation.VersionControl.Client.Workspace.CheckIn(PendingChange[] changes, String comment, CheckinNote checkinNote, WorkItemCheckinInfo[] workItemChanges, PolicyOverrideInfo policyOverride)
at #oLi.#L8x.#t.#EMd.#t.#O3c.#bQv()
at #oLi.#fqi.#GHi(Action , VersionControlServer )
at #oLi.#fqi.#t.#A2.#gqi()
at #oLi.#uRi.#LBf(#ovB , Action )
at #oLi.#uRi.#LBf(VersionControlServer , Action )
at #oLi.#fqi.#Ipg(ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , Action , TfsLocation , ICredentialsStore , #Fqi , VersionControlServer , Object )
at #oLi.#L8x.#Ipg(ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , Action )
at #oLi.#L8x.#t.#EMd.#aQv(ICancellableOperationStatus )
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.#i5f()
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperationBase.InvokeWithTracker(Action action)
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.Invoke()
at RedGate.SQLSourceControl.Engine.SmartAssembly.ExceptionReporting.ErrorReporterBase.Do(Action , Predicate`1 , Boolean )

For more information, see Help and Support Center at
Back to top
View user's profile Send private message

Joined: 16 Jun 2010
Posts: 1144
Location: My desk.

PostPosted: Thu Dec 08, 2011 8:53 pm    Post subject: Reply with quote

Hi, thanks for posting, and sorry you're having trouble.

This error is coming from the underlying TFS layer rather than SQL Source Control itself, however a quick google led me to this. Do you use Norton? If so, one user got around this type of error by disabling it by the looks of it.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB © 2001, 2005 phpBB Group