Jump to content

Sync Issues in Outlook for Microsoft 365


rpremuz
 Share

Recommended Posts

Hello!

Our users on MS Windows 10 Pro. 2004 64-bit machines with ESET Endpoint Antivirus 7.3.2036 use current Outlook for Microsoft 365 clients with email accounts on Exchange Online.

Clipboard01.png.e2011b16c9e8ffebf24405b71c590eb1.png

The ESET toolbar in Outlook is enabled.

A dozen of times every day Outlook records sync issues that include description as the following and the corresponding email message is saved to the Conflicts subfolder (which consumes mailbox space):

15:01:29 OCN: {I8:0x00000000-01E9D201}
15:01:29 Checking local modifications
15:01:29 Compare property: 0x007D001F
15:01:29 Ignore property: 0x3FFA001F
15:01:29 Compare named property: EsetMessageFlag
15:01:29 Compare named property: Emon Scanner Build
15:01:29 Getting remote properties
15:01:29 Checking remote modifications
15:01:29 Compare (conflict) property: 0x007D001F
15:01:29 
15:01:29 
15:01:29 Not equal (conflict) property: 0x007D001F
15:01:29 Local modification: {14:01:24.0006  16/11/2020 [DD/MM/YYYY]}
15:01:29 Remote modification: {14:01:23.0113  16/11/2020 [DD/MM/YYYY]}
15:01:29 Conflict generated, local item is winner

14:54:08 OCN: {I8:0x00000000-01E9C1CF}
14:54:08 Checking local modifications
14:54:08 Ignore property: 0x3FFA001F
14:54:08 Compare named property: Emon Scanner Build
14:54:08 Getting remote properties
14:54:08 Checking remote modifications
14:54:08 Compare (conflict) named property: Emon Scanner Build
14:54:08 Local: {I4:47480}
14:54:08 Remote: {Error (0x8004010F)}
14:54:08 Not equal (conflict) named property: Emon Scanner Build
14:54:08 Local modification: {13:54:03.0373  16/11/2020 [DD/MM/YYYY]}
14:54:08 Remote modification: {13:54:08.0523  16/11/2020 [DD/MM/YYYY]}
14:54:09 Conflict generated, remote item is winner

According to some threads on this forum, the issue exists for a long time and I wonder why it has not been fixed yet.
Any suggestions?

-- rpr.

Link to comment
Share on other sites

  • Administrators

Please import the configuration file OutlookSyncIssuesFix_enable.xml downloadable from https://forum.eset.com/files/file/29-outlook-sync-fix-for-endpoint-6-and-newer/.

An ultimate solution to sync issues will be a completely reworked Outlook plug-in which is preliminary planned with Endpoint 8.1.

Link to comment
Share on other sites

On a PC I imported OutlookSyncIssuesFix_enable.xml to ESET Endpoint Antivirus (Setup > Import/Export settings) and then restarted Outlook but after that it is still recording new sync issues (and conflict emails).

-- rpr.

Link to comment
Share on other sites

  • Administrators
21 minutes ago, rpremuz said:

On a PC I imported OutlookSyncIssuesFix_enable.xml to ESET Endpoint Antivirus (Setup > Import/Export settings) and then restarted Outlook but after that it is still recording new sync issues (and conflict emails).

Probably the conflicting property is now different. Please provide the sync log with the error. Not all sync issues can be resolved without disabling the add-on completely. If mails are scanned by ESET on MS Exchange, it should be safe to disable integration with Outlook.

Link to comment
Share on other sites

Marcos, I quoted two sync logs in the first post. Here are two more from today:

11:01:26 OCN: {I8:0x00000000-01EAFF29}
11:01:26 Checking local modifications
11:01:26 Ignore property: 0x3FFA001F
11:01:26 Compare named property: EsetMessageFlag
11:01:26 Getting remote properties
11:01:26 Checking remote modifications
11:01:26 Compare (conflict) named property: EsetMessageFlag
11:01:26 Local: {I4:1}
11:01:26 Remote: {Error (0x8004010F)}
11:01:26 Not equal (conflict) named property: EsetMessageFlag
11:01:26 Local modification: {10:01:17.0072  17/11/2020 [DD/MM/YYYY]}
11:01:26 Remote modification: {10:01:15.0591  17/11/2020 [DD/MM/YYYY]}
11:01:26 Conflict generated, local item is winner
10:58:16 OCN: {I8:0x00000000-01EAF9ED}
10:58:16 Checking local modifications
10:58:16 Ignore property: 0x3FFA001F
10:58:16 Compare named property: EsetMessageFlag
10:58:16 Getting remote properties
10:58:16 Checking remote modifications
10:58:16 Compare (conflict) named property: EsetMessageFlag
10:58:16 Local: {I4:1}
10:58:16 Remote: {Error (0x8004010F)}
10:58:16 Not equal (conflict) named property: EsetMessageFlag
10:58:16 Local modification: {09:58:08.0357  17/11/2020 [DD/MM/YYYY]}
10:58:16 Remote modification: {09:58:08.0954  17/11/2020 [DD/MM/YYYY]}
10:58:17 Conflict generated, remote item is winner

We do not use ESET on MS Exchange Online.

-- rpr.

Link to comment
Share on other sites

  • Administrators

Conflicts on property 0x3FFA001F cannot be avoided without disabling integration with Outlook. The ultimate solution will be a reworked add-on which is preliminary planned for Endpoint 8.1.

Link to comment
Share on other sites

Can someone from ESET Product Team comment on this?

I see this has been an on going issue since 2009:

https://www.wilderssecurity.com/threads/sync-issues-in-outlook.242803/

11 years on, and still the issue remains.

I recall this was supposed to be fixed in 6.x, then 7.3, but still seeing issue with 7.3

I have logged a case with ESET UK.

Causing pain to our users, we had one with 22GB sync issues caused by ESET.

Link to comment
Share on other sites

  • Administrators
27 minutes ago, CraigC said:

Can someone from ESET Product Team comment on this?

The ultimate solution will be a reworked add-on which is planned for Endpoint 8.1. It's basically ready, there are just some minor bugs that need to be sorted out.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...