How it looks in log without debug on

Feb 07 21:10:24 sogod [80680]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=a.kish%40domain&DeviceId=androidc911274876&DeviceType=Android HTTP/1.0" 200 0/102 0.025 - - 0 - 17
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.020 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.016 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.016 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 598/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 15
Feb 07 21:10:24 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.017 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.016 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.017 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.016 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.016 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.015 - - 0 - 16
Feb 07 21:10:25 sogod [80708]: localhost "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=FolderSync&User=s.grachev@domain&DeviceId=25D4B6EF97DD46508AE6FF363656F59A&DeviceType=WindowsOutlook15 HTTP/1.0" 200 599/13 0.016 - - 0 - 16

Same operation with Outlook 2019

It seems that the key differense is c_version values:
for Outlook 2021
c_version = 662867 (and always the same)

for Outlook 2019
c_version =1 ... 3xx (and various)

Hello,
I'm having the same problems on Office 2019, on Office 2023 it hasn't manifested itself yet.

Regards
Lukáš Gallina

Sorry, Office 2023 = Office 2021 :-)

Hello
I have the same Problem with "Outlook 365 MSO (Version 2401 Build 16.0.17231.20194) 64 Bit "
It seems to work for "in sync" Outlook (probably small amount of sync data) but fails for full sync.
regards Peter

I sitched for Mails as a workaround to IMAP config

Additional information to this case:
Im running SOGo: 5.9.1 on ubuntu VERSION="22.04.3 LTS (Jammy Jellyfish)" with mysql-database. An update to latest development version (sogo and sope) did not help. It just removed the depricated message of mysql when using "sogo-tool manage-eas resetdevice"

Normally when synchronisation via EAS fails, "sogo-tool manage-eas resetfolder" or "sogo-tool manage-eas resetdevice" helped in this cases. After resetdevice even folders are not rebuilt. Outlook stays completly empty. (no mail, no calendar, no contacts). I also played with sogo tuning parameters which are actually okay since years - it did not help.

The sogo-logfile is similar to the one of "AndreyEver" already posted in this case - I don't see any specific problem or error.

I noticed the same problem after updating outlook 2016(click-to-run) to Version 2401 (Build 17231.20194). A rollback to Version 2312 (Build 17126.20132) avoids the problem for now.

Unfortunately, rollback Outlook is not an option at all.
Any comments from SoGo team?

Hi there,

We will analyze this. No timeline for now

Sebastien

Hello Sébastien,

we noticed the same problem after updating to SOGo 5.9.1 for our Outlook fixed users from partner companies who are working for us. Unfortunately they used managed computers where we cannot influence their Outlook version nor configuration.

Even we know that you're working hard on all the issues and improvements we would be very happy if the error can be fixed soon.

Thanks a lot.

The Bahnkonzept team from Dresden/Germany

https://support.microsoft.com/en-us/office/outlook-desktop-exchange-activesync-connections-stopped-working-in-version-2401-da2dc0dd-297e-48ba-b6d9-ab18f5d522fc

Hello tfu
Thank you for the link to the problem originator - The rollback of outlook to version 2312 solves definitly the problem temporary for me .
Still - with the experiences of the last days - I will switch to IMAP configuration wherever possible. It seems to be much faster and more stable for big mailboxes.

Hello,
I've tested it with the last outlook version and it was a bit broken. If my account was already up to date with only 1/2 mails missing, the sync was ok. But for new account, nothing happens.

I've rollback outlook and all works perfectly fine.

I will follow this issue on microsoft to see what they'll do and if we need to do something on SOGo.

For now, either rollback outlook or use imap/caldav synchronizer for the accounts.

Seems fixed by Microsoft

I've tested it and it seems to work fine

I testet it with Sogo 5.10.0 before and after upgrade to Office 365 Version 2402 Build 16.0.17328.20124 (64 Bit)

• before Office update: sync of new account did not work at all (as reported in this thread)
• after Office update: sync of new account worked as usual. It works again with full sync of big mailboxes (>3G) and sync of small amount of delta's

Good!
I will close this ticket.

Sorry i reopened the ticket because with the outlook last version, event created from webmail sogo are correctly sync with outlook. But events create from outlook are not sync with sogo. Can someone test it too ?

I just testet it (calender entry) with sogo 5.10.0 and the new Outlook Version 2402 - This works perfect in all directions sogo <-> Outlook , Outlook <-> sogo, (even from different windows hosts). You probably have to do a full resync with "sogo-tool manage-eas resetdevice".

@qhivert

Confirmed. Works with Outlook 2019 but DOES NOT with Outlook 2021 (no sync Outlook -> Sogo)

just to be clear: with the latest Sogo and fully updated Outlook 2021 (EAS connection) when creating a new event in the calendar, it is not synchronized (nothing in Sogo). If event has been created in Sogo sync to Outlook 2021 works perfectly well.

With Outlook 2019 sync in both directions works

"sogo-tool manage-eas resetdevice ..." does not help

Any new on this?

I retested Outlook sync with Office 365 - abo version, which should according MS still be the same as Office 2021 - in both directions (EAS connection) with Office february patch (2402) and the latest march patch (2403) - exact reported Version: "Microsoft® Outlook® Version 2403 Build 16.0.17425.20124 " (32 and 64Bit) connected to SOGo 5.10.0 server. It still works perfect in both directions. At least my initial sync problem (EAS-connection) has been caused purely on client side by the MS Office 365 january patch (2401) and has been solved with the february patch (2402) of Outlook - and still works after latest march patch of Outlook. It was in my case not a SOGo issue.

Hello,
I've investigated it a bit more and to me, it's still a problem on outlook side. In fact, outlook will never made a request to sogo with the new event.
When enabling outlook log, I can see errors like this

<Error>
<Hr>80020012</Hr>
<Message>Arithmetic overflow.</Message>
<File>src\outlook\pstprx\storeas\eascontentuploader.cpp</File>
<Line>182</Line>
</Error>

Whem comparing to an older outlook version where it works, all the requests from outlook and answers from sogo are the same, except the sync request with the new event. I get this outlook error instead.

Hello,
I've reported this bug
here -> https://answers.microsoft.com/en-us/outlook_com/forum/all/activesync-dont-sync-events-created-with-outlook/1ff33063-3f84-47d7-8781-ea55402f30b4
Then here -> https://feedbackportal.microsoft.com/feedback/idea/ff7a6d0a-ccf8-ee11-a73d-6045bd7e894e

On the second link you can vote and comments if you want this issue to get more attention.