2
Problem with Mapi sync with outlook
Problem reported by Mario Songia - 7/7/2022 at 4:33 AM
Submitted
SmarterMail Enterprise
Versione: 8125 (mar 31, 2022)

 
[2022.07.07] 11:42:51.276 Exception: direzione.sanitaria@valduce.it RopResponseBuffer CachedPayloadBytes.Count is greater than Int16 [65564]
[2022.07.07]    in System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
[2022.07.07]    in System.Environment.get_StackTrace()
[2022.07.07]    in MailService.Protocols.MAPI.Models.RopResponseBuffer.ToBinary(PulFlags flags, MapiProcessorState mapiProcessorState)
[2022.07.07]    in MailService.Protocols.MAPI.RequestTypes.ExecuteResponse.ToBinary()
[2022.07.07]    in MailService.Protocols.MAPI.RequestTypes.ExecuteRequest.Process()
[2022.07.07]    in MailService.Protocols.MAPI.MapiProcessor.Process()
[2022.07.07]    in MailService.WCF.MAPI.MapiService.GetResponse(Guid ticketGuid)
[2022.07.07]    in SyncInvokeGetResponse(Object , Object[] , Object[] )
[2022.07.07]    in System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
[2022.07.07]    in System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
[2022.07.07]    in System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
[2022.07.07]    in System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
[2022.07.07]    in System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
[2022.07.07]    in System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)
[2022.07.07]    in System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
[2022.07.07]    in System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
[2022.07.07]    in System.ServiceModel.Dispatcher.ChannelHandler.OnAsyncReceiveComplete(IAsyncResult result)
[2022.07.07]    in System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
[2022.07.07]    in System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
[2022.07.07]    in System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)
[2022.07.07]    in System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
[2022.07.07]    in System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
[2022.07.07]    in System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)
[2022.07.07]    in System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)
[2022.07.07]    in System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
[2022.07.07]    in System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32 error, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
[2022.07.07]    in System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)
[2022.07.07]    in System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

7 Replies

Reply to Thread
0
Kyle Kerst Replied
Employee Post
Hi Mario! Has this Outlook client successfully synchronized this account previously, or is this a fresh sync attempt you're seeing these errors on? Also, what version of Outlook is this user leveraging on their PC?
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Mario Songia Replied
Hi Kyle,
this client has successfully synchronized until today 11.42 a.m.. the outlook version is 365.
if I can always take advantage of today we have another problem: some users no longer see their mail on Android devices (via EAS): we tried to remove the account from Android and recreate it: at the first synchronization you can see the emails correctly but from the second in then we no longer see anything. we checked that for these users in the server's EAS logs. which error is reported: [2022.07.07] 21: 01: 24.795 [645062897] SYNC KEY MISMATCH (PerformSync) (2650002): Device = [20220707.180250.6600] Server = [20220707.180252.6601] User = [rclerici @ valduce. it] any idea?
0
Kyle Kerst Replied
Employee Post
Thanks for your followup on this Mario. Both of these sync issues sound like the clients involved have gotten out of sync with the server, and require a clean resync. In our latest versions you can do that for those users by selecting the account in the account list and then clicking ...>Resync User Protocols. Can you give this a try and let me know how it works for you?
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Mario Songia Replied
Kyle, the issue still remain after the Resync User Protocol command.
Thanks.
0
Jonathan Martin Replied
Has there been any resolution on this? We have users on Outlook 365 connecting via MAPI and everything was syncing properly until yesterday evening. Now, only their main inbox syncs with SmarterMail. No subfolders and not the sent folder. Performed a Resync User per above but same issue. We can force a sync of an individual sub folder by manually clicking on Update Folder in Outlook. Just no automatic syncing of subfolders.
0
Kyle Kerst Replied
Employee Post
Hey there! Sorry for the delay as I was out of the office for a bit and am still working on getting caught up. If the resync user protocols doesn't help there is likely something in the account that is causing us trouble (some folder, message, bad contact data, etc) so I recommend submitting a ticket so we can help you track this down further. 
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Jonathan Martin Replied
Thanks, Kyle. I think we have narrowed it down to a possible corrupt data file due to a power outage causing an unexpected shutdown of Outlook. We deleted the Outlook profiles and started over and things look good at this point.

Reply to Thread