Replication failures are occurring on the base image where it had been completing successfully on all other incremental snapshots.
APPLICABLE UI ERRORS:
An unexpected error occurred
An argument was unexpectedly null in code located in or called by ‘HttpContent.ReadAsString’
StackTrace:
System.AggregateException: One or more errors occurred. —> System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.Take[TSource](IEnumerable`1 source, Int32 count)
at Microsoft.Http.HttpContent.ReadAsString()
at WCFClientBase.ClientBase.LogResponseError(Uri uri, String method, HttpResponseMessage response)
at WCFClientBase.ClientBase.GetResponseContract[T](Uri uri, String method, HttpResponseMessage response)
at WCFClientBase.ClientBase.ExecuteServiceCall[TReturnType,TRequestType](Uri uri, TRequestType request, String method, String knownETag)
at WCFClientBase.ClientBase.ExecuteServiceCall[TReturnType,TRequestType](Uri uri, TRequestType request, String method)
at Replay.Core.Client.ReplicationCommunicationCoreClient.SyncRemoteReplicationJob(RemoteSyncReplicationJobRequest requestSync)
at Replay.Core.Implementation.Replication.Jobs.ReplicationJob.SyncRemoteReplicationJob(TimeSpan syncTimeout, CancellationToken cancellationToken)
at Replay.Core.Implementation.Replication.Jobs.ReplicationJob.DoJob(CancellationToken cancellationToken)
at Replay.Core.Implementation.Replication.Jobs.ReplicationJob.at System.Threading.Tasks.Task.Execute()
To resolve this issue, we recommend making the following changes in the registry to increase the timeouts and decrease the parallel streams on both the source and target cores:
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center