A non-fatal exception occured during replication. The remote server does not appear to be responding

Products

• IT Management Suite

Issue/Introduction

During replication, The following warning message is seen in the Destination NS's logs:

Process: AeXSvc (13556)
Thread ID: 83
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: 84abf88c-0808-4a08-96a4-37eca26faf35, Exception: Altiris.NS.Exceptions.AeXException: The remote server does not appear to be responding (Server: SourceNS) ---> System.Net.WebException: The remote name could not be resolved: 'SourceNS'
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Altiris.NS.Replication.SystemInformation.SystemInformationWebServiceProxy.GetMaxAspNetRequestSize()
   at Altiris.NS.Replication.ReplicationJobHelper.GetRemoteServerMaxAspNetRequestSize(ReplicationJob jobItem)
   at Altiris.NS.Replication.ReplicationJobHelper.PingRemoteServer(ReplicationJob jobItem)
   --- End of inner exception stack trace ---
   at Altiris.NS.Replication.ReplicationJobHelper.PingRemoteServer(ReplicationJob jobItem)
   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

DNS is improperly configured

Resolution

In this case, the Destination Server was unable to contact the Source Server (It was trying to use the FQDN). The DNS Server was improperly configured.

To work around this:

• Add a hosts file entry for the FQDN of the Source server

To resolve this:

• Take the appropriate steps within your organization to ensure that there is a correct DNS entry for the servers Fully Qualified Domain Name.