Errors: "A non-fatal exception occured during replication ...The operation has timed out" during a replication cycle

Products

• IT Management Suite

Issue/Introduction

During a replication cycle, the following message was seen on the Destination server:

Process: AeXSvc (1556)
Thread ID: 53
Module: AeXSVC.exe
Source: ReplicationJobThread
Description: A non-fatal exception occured during replication. The replication job will be restarted from the last check point. (JobID: 998ab0b8-80f0-4fbb-a58e-1be27fa3555a, Exception: System.Net.WebException: The operation has timed out
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Altiris.NS.Replication.ItemReplicationWebServiceProxy.FinishGetItemHashes(String jobId, String operationId, ItemHashData[] hashes, ReplicationResult[] results, ReplicationDataState state)
   at Altiris.NS.Replication.DestinationReplicationSynchronizationProvider.HashObjects(Object proxy, String jobId, String operationId, String type, Object[] hashes, ReplicationResult[] results, ReplicationDataState state)
   at Altiris.NS.Replication.DestinationReplicationSynchronizationProvider.HashItems(ReplicationJob jobItem, String jobId, String operationId, ReplicationManifest manifest)
   at Altiris.NS.Replication.DestinationReplicationSynchronizationProvider.ProcessItemManifest(ReplicationJob jobItem, String jobId)
   at Altiris.NS.Replication.DestinationReplicationSynchronizationProvider.ProcessManifest(ReplicationJob jobItem, String jobId)
   at Altiris.NS.Replication.DestinationReplicationJobWorker.ProcessManifest(ReplicationJob jobItem, String jobId)
   at Altiris.NS.Replication.DestinationReplicationJobWorker.ProcessJob(ReplicationJob jobItem)
   at Altiris.NS.Replication.ReplicationJobThread.ProcessJob())

Environment

ITMS 8.x

Cause

All Notification Server timeouts were checked and found to be set well past the interval that the timeout was noticed in. In this case, a proxy server was configured in the environment with a low timeout value and this was the cause the replication failure and errors.

Resolution

Disable the configured proxy server and once this was removed from the test environment the replication completed successfully.