Jump to content

Outlook - this is the most recent version, but you made changes to another copy


Recommended Posts

We've been having issues with outlook & conflicting for a while. While i've only been informed of our users having issues, it has been ongoing for over a month. My outlook confirms there is an issue.

the symptoms do appear to be different as some users are reporting "this is the most recent version, but you made changes to another copy" which i have not seen on my local Outlook when replying to emails, however i do see it on emails in the Sync Issues\conflicts folder. Users appear to see it on their new emails (outside of sync issues folder)

Local installs: EES v8.0.2028, Office 2019 x86 & Windows 10 x64

RDS: Server 2019, office 2019 x86, EFS 7.1.12006.0

Our users mailboxes are currently onprem Exchange 2019, with my mailbox in o365 as we are planning to migrate soon - this doesnt appear to have a bearing on whos affected though.

The following quote is an Outlook Sync Issues message on my local Outlook which only occurs when the Eset outlook addin is enabled and appears on every new email. Disabling the addin and sending a test email does not generate a conflict message or the "this is the most recent version, but you made changes to another copy" message.

Quote

11:00:16 Message class: {SU:IPM.Note}

11:00:16 Mail Conflict Resolution

11:00:16 Local subject: {SU:New Message Alert}

11:00:16 Remote subject: {SU:New Message Alert}

11:00:16 Local Message Entry ID: {CB:70, LPB:0x00000000B6993DABF913C948BB4F9669AC6EF50D07006DA5DEA77CB8334D80D6D8411B4CBFF7000000219E01000049DF2898AA5C4E468ABA70543B8FF12100009965808B0000}

11:00:16 Remote Message Entry ID: {CB:70, LPB:0x00000000B6993DABF913C948BB4F9669AC6EF50D07006DA5DEA77CB8334D80D6D8411B4CBFF7000000219E01000049DF2898AA5C4E468ABA70543B8FF12100009965808B0000}

11:00:16 Local Message ChgKey: {CB:20, LPB:0x113D6DEAD0CF2340900903F6CE53B1090035B8B5}

11:00:16 Remote Message ChgKey: {CB:22, LPB:0x49DF2898AA5C4E468ABA70543B8FF12100009943B564}

11:00:16 Local Message PCL: {CB:44, LPB:0x14113D6DEAD0CF2340900903F6CE53B1090035B8B51649DF2898AA5C4E468ABA70543B8FF12100009943B562}

11:00:16 Remote Message PCL: {CB:23, LPB:0x1649DF2898AA5C4E468ABA70543B8FF12100009943B564}

11:00:16 Checking local modifications

11:00:16 Compare property: 0x007D001F

11:00:16 Ignore property: 0x3FFA001F

11:00:16 Compare named property: Emon Scanner Build

11:00:16 Compare named property: EsetMessageFlag

11:00:16 Compare named property: EsetAntispamMsgHeader

11:00:16 Getting remote properties

11:00:16 Checking remote modifications

11:00:16 Compare (conflict) property: 0x007D001F

11:00:16

11:00:16

11:00:16 Not equal (conflict) property: 0x007D001F

11:00:16 Local modification: {10:00:09.0510  30/04/2021 [DD/MM/YYYY]}

11:00:16 Remote modification: {10:00:10.0091  30/04/2021 [DD/MM/YYYY]}

11:00:16 Conflict generated, remote item is winner

 

Edited by veehexx
Link to comment
Share on other sites

8 minutes ago, veehexx said:

the symptoms do appear to be different as some users are reporting "this is the most recent version, but you made changes to another copy" which i have not seen on my local Outlook when replying to emails, however i do see it on emails in the Sync Issues\conflicts folder. Users appear to see it on their new emails (outside of sync issues folder)

ok, turns out i DO have the info message on normal emails "this is the most recent version, but you made changes to another copy". subtle enough that i've just not noticed!

Link to comment
Share on other sites

  • Administrators

You can disable writing to email messages as follows:

- save the following to an xml file:

Quote

<?xml version="1.0" encoding="utf-8"?>
<ESET>
 <PRODUCT NAME="endpoint" MAJOR="60002" MINOR="7E50000">
  <ITEM NAME="plugins">
   <ITEM NAME="01000800">
    <ITEM NAME="settings">
     <NODE NAME="OutlookSyncIssuesFix" TYPE="number" VALUE="33" />
    </ITEM>
   </ITEM>
  </ITEM>
 </PRODUCT>
</ESET>

- import the xml

Link to comment
Share on other sites

looks to have worked on my outlook. will push it out via Protect to all devices now and confirm with users. Thanks!

what exactly are the implications of this fix - anything reduced functionality that i need to be aware of?

Link to comment
Share on other sites

Ok, i've looked into adding it to our Protect policies but it's not obvious (or xml importable) to what i need to actually set.

How would i either manually replicate the correct policy option changes of the xml, or how do i import that xml into a new policy?

 

based on a client-side export, and using your fix it appears to set the following under 01000800 which are not entirely clear what Protect policies i need to define to our userbase:

...
<ITEM NAME="01000800">
    <ITEM NAME="settings">
     <NODE NAME="OutlookIntegrationEnabled" TYPE="number" VALUE="1" />
     <NODE NAME="OEIntegrationEnabled" TYPE="number" VALUE="1" />
     <NODE NAME="WLMIntegrationEnabled" TYPE="number" VALUE="1" />
     <NODE NAME="DisableInboxChangesChecking" TYPE="number" VALUE="0" />
     <NODE NAME="OutlookIntegrationChangeCounter" TYPE="number" VALUE="0" />
     <NODE NAME="
	 
	 
	 " TYPE="number" VALUE="33" />
     <NODE NAME="OutlookCOMAddinForced" TYPE="number" VALUE="0" />
     <NODE NAME="DeliveryByEESessionEventsEnabled" TYPE="number" VALUE="0" />
     <NODE NAME="ExportToMsg" TYPE="number" VALUE="0" />
     <NODE NAME="OEAlwaysUseEplgHooks" TYPE="number" VALUE="0" />
     <NODE NAME="ExportToEmlEnabled" TYPE="number" VALUE="0" />
    </ITEM>
   </ITEM>
...

 

Link to comment
Share on other sites

think i got too excited with the first fix.

we're still seeing the message conflict although with a slightly different error in Outlook Sync Issues.

Quote

15:27:17 Message class: {SU:IPM.Note}

15:27:17 Mail Conflict Resolution

15:27:17 Local subject: {SU:FW: Emails}

15:27:17 Remote subject: {SU:FW: Emails}

15:27:17 Local Message Entry ID: {CB:70, LPB:0x00000000B6993DABF913C948BB4F9669AC6EF50D07006DA5DEA77CB8334D80D6D8411B4CBFF7000000219E01000049DF2898AA5C4E468ABA70543B8FF1210000996580970000}

15:27:17 Remote Message Entry ID: {CB:70, LPB:0x00000000B6993DABF913C948BB4F9669AC6EF50D07006DA5DEA77CB8334D80D6D8411B4CBFF7000000219E01000049DF2898AA5C4E468ABA70543B8FF1210000996580970000}

15:27:17 Local Message ChgKey: {CB:20, LPB:0x113D6DEAD0CF2340900903F6CE53B1090035F1F6}

15:27:17 Remote Message ChgKey: {CB:22, LPB:0x49DF2898AA5C4E468ABA70543B8FF12100009943BE5D}

15:27:17 Local Message PCL: {CB:44, LPB:0x14113D6DEAD0CF2340900903F6CE53B1090035F1F61649DF2898AA5C4E468ABA70543B8FF12100009943BE59}

15:27:17 Remote Message PCL: {CB:23, LPB:0x1649DF2898AA5C4E468ABA70543B8FF12100009943BE5D}

15:27:17 Checking local modifications

15:27:17 Ignore property: 0x3FFA001F

15:27:17 Compare named property: EsetMessageFlag

15:27:17 Getting remote properties

15:27:17 Checking remote modifications

15:27:17 Compare (conflict) named property: EsetMessageFlag

15:27:17 Local: {I4:1}

15:27:17 Remote: {Error (0x8004010F)}

15:27:17 Not equal (conflict) named property: EsetMessageFlag

15:27:17 Local modification: {14:27:06.0523  30/04/2021 [DD/MM/YYYY]}

15:27:17 Remote modification: {14:27:06.0710  30/04/2021 [DD/MM/YYYY]}

15:27:17 Conflict generated, remote item is winner

 

Link to comment
Share on other sites

  • Administrators

Unfortunately the setting cannot be applied via a policy. However, if you have email scanned on the mail server you can disable integration with MS Outlook to prevent sync conflicts from occurring.

Link to comment
Share on other sites

unfortunately we dont have the exchange scanner on our licence.

while not native via Protect, it looks like we could script this via other tools (SCCM maybe) using ecmd.exe - https://support.eset.com/en/kb7277-use-eset-command-line-ecmdexe-to-importexport-security-product-configurations-in-eset-endpoint-products-7x

Probably wont get time to test this today but should find the time by the end of the week.

Link to comment
Share on other sites

  • 2 weeks later...

Have a user with the same issue, results in duplicated messages in deleted items folder, one read the other unread.
Importing the xml didn't correct it, disabling outlook integration fixed.
Marcus - you made mention of a reworked add-in coming with 8.1 - is there an ETA for this?
https://forum.eset.com/topic/26323-sync-issues-in-outlook-for-microsoft-365/

 

Link to comment
Share on other sites

  • Administrators
2 hours ago, Marchmussels said:

you made mention of a reworked add-in coming with 8.1 - is there an ETA for this?

Unfortunately there is no ETA yet.

Link to comment
Share on other sites

  • 1 month later...
  • Administrators
2 minutes ago, RD_AGA said:

I have installed 8.1, but the problem did not get fixed.

The new Outlook plug-in was not supposed to be in v8.1. It's pending for an in-depth review before it's added to Endpoint.

Link to comment
Share on other sites

Hi @Marcos, you say above it was not supposed to be in 8.1, but you did say "it will be included in 7.0" three years ago, I am curious what the delay is?

 

 

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...