An existing connection was forcibly closed by the remote host

[Anonymous]

There are two CAD men working separately on one file.

Everything has been fine until today when one of the CAD guys noticed that the file was checked out to him.

The file had been updated by the 2nd guy and checked back in successfully and without issue but the 1st guy cannot check the file back in.

We save the file and try to check it in but it stops part way through the process and a pop up window appears saying "The Following files could not be checked in due to restrictions". The restriction is "£An existing connection was forcibly closed by the remote host".

Any ideas or a fix would be very welcome.

many thanks

Dave

[cbenner]

@Anonymous

Could possibly be related to >>this<<? 

[reidmatthew]

Hi @Anonymous thanks for posting to the Vault forums. This is a very frustrating message that I have seen several times with Vault users. If I remember correctly, the cause is usually a network issue between the Vault client and the Vault server machine. In some instances it has been firewall issues, antivirus issues, or proxy issues as the link @cbenner shared points out. Did that article help you out at all? Is this happening to all files in your Vault and with all users or just these particular CAD men and files?

I would recommend you try using something like Fiddler to monitor the web traffic and see if there are any extra details such as an HTTP error such as 500, 501, or 504 to give us more information.

You could also review this article about the remote host being forcibly closed in Vault.

Let me know if you have any questions.

[Anonymous]

It looks like both my PC and the Network have issues.

Both users are experiencing issues during "Checking in".

I'll update this as soon as IT have had a chance to track down any extraneous causes.

[reidmatthew]

@Anonymous  I am just following up to see if you have made progress on resolving this issue with your IT team. It would be good to share what you discovered with the community to help others who may see similar behavior. Let me know if you need anything else.

As always please hit the Accept as Solution button on the post(s) which provided a solution for your issue or question.

[Anonymous · Accepted solution]

It appears that my PC was under specified by the "experts" in IT. I've had numerous weird occurrances during the last 2 years and with a number of issues with CAD the situation came to a head. My PC has now had 2 new drives and although not perfect (I can still work faster than the CAD) the issues seem to have gone away. Its early days as far as I am concerned, but fingers cross all seems well at the moment. I now have a drive that manages the start up and a new hard drive for normal use.

[dany_rochefort]

I have figured out was this problem is and how to solve it even tho this is an old post i am replying to...

Turns out this problem happens when trying to check in older *.dwg formats into the vault. I'm talking like early 2000's dwg formats. 

I simply went into the dwg files, purged, audit and saved as a more recent dwg format and the problem was solved...