1
MS Outlook MAPI: Exception RopResponseBuffer CachedPayloadBytes.Count is greater than Int16 [134212]
Problem reported by Gabriele Maoret - SERSIS - 9/4/2024 at 7:13 AM
Submitted
I have a lot of exception lik ethis from some users with MS Outlook MAPI (variuos versions) :

[2024.09.04] 09:04:14.617 Exception: xxx@yyy.it RopResponseBuffer CachedPayloadBytes.Count is greater than Int16 [134212]
[2024.09.04]    at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.Invoke(HttpContext context)
[2024.09.04] 09:04:14.617 [{874DD5A6-A326-476E-947E-71B2D18EEE2C}:19] [xxx@yyy.it] Exception: System.OverflowException: Value was either too large or too small for a UInt16.
[2024.09.04]    at System.Convert.ThrowUInt16OverflowException()


Theese Outlook sync don't work well...



Do you have any suggestions?
Gabriele Maoret - Head of SysAdmins at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)

4 Replies

Reply to Thread
0
Jorel Haggard Replied
Employee Post
Hello Gabriele,

I'm going to start you a support ticket so we can begin looking into this issue for you. We'd like to get more information on the sync errors with a Fiddler trace, if you're able to provide one. 

Best,
Jorel Haggard System/Network Administrator SmarterTools Inc. www.smartertools.com
0
Brian Bjerring-Jensen Replied
Thats an integer16 handling numbers between -32768 to 32767 and somewhere there is a wrong number plugged in in the code trying to push a number greater than integer16 can handle

We see it sometimes on custom SQL plugins during dev.
2
Gabriele Maoret - SERSIS Replied
unfortunately this problem occurred to a senior executive of an important client of mine...

So I couldn't wait and had to try to solve the problem as quickly as possible.

SUMMARY:

I was on build 8930 and everything worked (apart from the small bugs already known about this version) --> I switched to the "new" 9008 and after a few days the problem appeared --> I then updated to 9014, but the problem persists.

In the end I went back to the "old" (pre Linux, so to speak) 8930 and now everything works fine (the small bugs of this version are, all in all, bearable...)
Gabriele Maoret - Head of SysAdmins at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
0
Brian Bjerring-Jensen Replied
I aint updating until its proven reliable in production and handling MAPI/EAS flawlessly.

Reply to Thread