This article describes the error and its resolution, which occurs when the File Archive Assistant synchronizes, and the mailbox contains a high amount of files for the use.
Error: 'Synchronization failed (An error occurred while communicating with the GFI MailArchiver server.). Check the configuration.'
You can identify the issue by checking the debug logging on the FAA side and the server side. You will find that the client and server logs match each other and that the value of [newMessages] in the given line of the debug log file
Store\Debuglogs\EmailMessageRetrieval.log shows a very high number (Note that it is not clear how large this number must be to trigger this issue, but probably anything over 1000)
FAA 2014-09-22,10:31:35,921,1,"#00002620","#00000006","info ","SynchronizationManager","Sync - updating files from archive store '2014 Aug' (317f1536-1fc7-4ceb-aaa8-526742f5f68e)" 2014-09-22,10:31:37,416,1,"#00002620","#00000006","error ","SynchronizationManager","error: Synchronization failed: MArc.FAA.Agent.Core.FAAAgentException: An error occurred while communicating with the GFI MailArchiver server.
System.ServiceModel.CommunicationException: An error occurred while receiving the HTTP response to http://server11:81/MailArchiver_Services/FileArchiveAssistant.svc/Windows.
The server logs contain more details.
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
System.IO.IOException: Unable to read data from 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 STORE 2014-09-22,10:31:36,013,1,"#00011390","#00000013","info ","EmailMessageRetrieval",">>GetFileUpdatesBulk db: 317f1536-1fc7-4ceb-aaa8-526742f5f68e; cookie: [-9223372036854775808, -9223372036854775808]; startDate: ; endDate: ; maxCount: 1000; userId: 17483c07cbb28049893257bc49078333" 2014-09-22,10:31:36,884,1,"#00011390","#00000013","info ","EmailMessageRetrieval","
GFI Archiver Build 20140616
- This could be due to the service endpoint binding not using the HTTP protocol.
- This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down).
Upgrade to MARC2015 build 20141117 (including FAA).