-
Title
Error 1647 1647 - Fatal - An existing connection was forcibly closed by the remote host -
Description
Error 1647 1647 - Fatal - An existing connection was forcibly closed by the remote host
-
Cause
In this particular case and even there are two articles in the KB:
https://support.quest.com/SolutionDetail.aspx?ID=105940
https://support.quest.com/SolutionDetail.aspx?id=SOL102242&pr=vRanger&st=Published
After checking the two articles mentioned above, the reason for the fail is the existence of two different backup software in the the smae virtual machine, in this case is vRanger and Appassure. The connection and the network resouces during backup operations tokes all the network resources promoting that vRanger's backup "time out" due to not enough throughput during the backup operation., promoting that vRanger backup operation fails to communicate with the Remote Host, this error is logged as Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. - SocketException: An existing connection was forcibly closed by the remote host. The reason for this error 1647 is a IOException that promotes that the system thinks that the error is related with 1647 which is a System Error Code used in Windows Server the problem resides in the fact that the Windows System Error Codes are very broad. Each one can occur in one of many hundreds of locations in the system. Consequently the descriptions of these codes cannot be very specific.
-
Resolution
Dissable Appasure and run a backup job from the vRanger, if error in not loaded and the backup finnish with no problems, keep the application off during the normal backup operations if the system can do the programmed back up jobs. Remove the appasure software and install the software in another VM and let the softwares to run its own jobs but from two different VM's.
Note: The AppAssure 5 Core is not supported on Windows Server 2008 Core edition, 2008 R2 Core edition, or 2012 Core edition. In addition, it does not support Hyper-V Server 2008, 2008 R2, or 2012.
Solution install both software in different servers to avoid issues during the back up operations