An existing connection was forcibly closed...

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
TonyKInTexas
Posts: 17
Joined: Mon Jul 11, 2005 9:01 am

An existing connection was forcibly closed...

Post by TonyKInTexas » Wed Aug 24, 2005 7:26 am

Morning,

We are seeing a log entries between multiple instances of SOS, on different servers of course, where SOS is forcibly closing client connections.

What are the culprits for this type of behavior?

In doing a search of the forums, it seems to be a common issue.

Thank you kindly,

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Aug 24, 2005 8:14 am

Is the message something like "An existing connection was forcibly closed by the remote host" ?

The remote host refers to the client, so it is the client closing the connection. The SOS Server does not close connections, unless it crashes or hangs for some reason. Some common causes of this error:

-- the user closes the client during an operation
-- a third party device like a firewall closes the connection after a certain amount of time or data has passed
-- the client crashes (not common)
-- there's a problem with the VSS database (like database corruption) that causes instability in the communication between client and server.

Is there a pattern to these error messages on you SOS installation?
Linda Bauer
SourceGear
Technical Support Manager

Guest

Post by Guest » Wed Aug 24, 2005 9:10 am

I do not see a pattern and none of our users are telling me anything. A review of the logs is where I find the information.

There is another group who just established their own SOS server and it is causing them no end of problems.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Aug 24, 2005 11:06 am

They've contacted us via phone/email and we're working with them on this.
Linda Bauer
SourceGear
Technical Support Manager

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Aug 29, 2005 8:55 am

Update: This issue was resolved by setting "timeout idle connections" in the Server Manager back to its default of "off."
Linda Bauer
SourceGear
Technical Support Manager

Post Reply