Currently we are facing problems when the connection during sync is lost in an UploadOnly scenario
The problem is: Sometimes when the connection is gone the sync "thinks" that all rows were all processed - but that's not true. They changes were not successfully processed at the server.
Somehow the "client" thinks that the rows were processed correctly and thats why the client is not sending the rows again with the next sync. It looks like that the service dies somehow or get a timeout - but how can it happen that the client thinks
that everything was processed?
System.ServiceModel.CommunicationException: The underlying connection was closed: The connection was closed unexpectedly. ---> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---