An existing connection was forcibly closed by the remote host - Replication (4034264)

Replication from one Core to another fails with the following exception:

IOException
Exception chain:
An existing connection was forcibly closed by the remote host
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
One or more errors occurred.

System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---

Please follow the steps below on both Source and Target Cores for sustained replication errors:

1. Stop Core service
2. Increase the next timeouts on the master and target cores to 30 minutes and restart both (Master and Target services):
   1. HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService\RemoteReplicationSyncJobTimeout
   2. HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService\VolumeImageSessionTimeout
3. Increase the following Core timeout settings via registry editor:
   1. KEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ConnectionTimeout
      1.  from 00:05:00 to 00:15:00  
   2. KEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ReadWriteTimeout
      1.  from 00:05:00 to 00:15:00  
   3. HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ConnectionUITimeout
      1.  from 00:05:00 to 00:15:00  
   4. HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ReadWriteUITimeout
      1. from  00:05:00 to 00:15:00 
4. Start Core service
5. Please collect new AAInfo logs from Source and Target Cores if issue still persists after that.

If the issue persists, a WireShark analysis will need to be conducted to determine why the network streams are being closed.

Windows Registry Disclaimer:

Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.