Sync issues in Outlook

Setting the value to 51 will reduce writing to messages to the bare minimum to prevent most of sync issues. In particular, it will disable:
- writing a scan result to message headers (property PR_TRANSPORT_MESSAGE_HEADERS)
- tag messages (regardless of the program settings)
- writing antispam scan result to the property EsetAntispamMsgHeader
- writing a spam prefix to the message subject

Enabling this setting may not prevent sync issues from occurring (especially if messages are modified on the server by other software as well), it could reduce the number of occurrences, however. Maybe you could consider disabling email protection on clients and scan email on the server only.

 

Thank you. I'll probably go with your suggestion and create a policy for our Blackberry users and disable the Outlook integration just for them.

 

I'm new to this thread but am having the same problem: getting a lot of synchronization issues in my email. I'm running W7 64 bit, Outlook 2007 in an MS Exchange 2007 environment. I also sync my email onto a Palm Pre Plus smartphone.

I'm not a corporate user, but rather a home user, so:
A. I don't want to disable Outlook integration
B. I don't have the option to "Enable resolution of Microsoft synchronization issues" which is provided in ERA, noted here: https://www.wilderssecurity.com/showpost.php?p=1673198&postcount=47

Is there are resolution for home users?

 

I believe the answer to your question is no. Without removing one or the other your going to have sync issues. Both the Palm Pre syncing software and Outlook is touching message headers, hence the synchronization problems.

As a corporate user we have never had a resolution to this issue and have created a BlackBerry policy the disables Outlook Integration for users that use Blackberrys. We are counting on the real-time protection to block anything that could make it through e-mail.

 

If that's the case, I think I'll keep the OL Integration and just delete the Sync notifications and dupe messages once a week.

Too bad. Otherwise I've been quite happy with ESET (just subscribed a month ago). It's crazy that they can't come up with a solution to this.

 

It is possible to minimize modifications of scanned messages to the bare minimum by creating a special registry value that will ensure that:
- the antivirus scanner will not write the scan result to the Internet header
- the setting of appending notifications to scanned messages will be ignored and no notifications will be added
- the antispam scanner will not write the scan result to the Internet header
- the antispam prefix will not be written to the message subject

Remember that this may only minimize the number of syn issues occurrences. If messages are modified on the server or another client simultaneously, a sync issue will occur. To prevent sync issues from occurring completely, you might need to disable scanning of messages on the clients and have them scanned on the server only.

 

OK. Good information. Now it would be helpful to now where I can put my hands on this "special registry value."

 

Marcos, Did you see my question? Where can I put my hands on this "special registry value"?

 

Yes, check your PM

 

Has any more progress been made on this? We've recently moved to Exchange 2010 from 2003 and have noticed the same sync issues

 

You can mitigate the occurrences of sync issues by minimizing the amount of information written to scanned email on clients. Sync issues occur by design if email is modified on the server and client (ESET) concurrently. If email is scanned on the server I'd suggest disabling the scanning on clients to prevent sync issues from occurring.

 

Thanks for that Marcos, but we don't have any email virus scanning on our server. It's all done by a 3rd party before it reaches our server.

 

I'd suggest that you check your Sync Issues folder for "Modification resulution" logs. They contain a line with "Not equal (conflict) property:". Please provide the number that follows which will tell what property is in conflict.

 

Do you have a Blackberry server? That seems to be one of the reasons many of us are receiving the sync issues while running Eset on the client computer along with Outlook.

 

I give up. How do you get to the settings shown above by rockshox? I have NOD32 V4.2.64.12. The only way I could get to this was to export the settings to XML, edit the XML and then re-import the settings...

I need to test this value of "51". I have thousands of sync issues with Outlook 2010 connecting to Exchange 2007 with a BES Server. Unfortunately, we use a hosted exchange service so the only changes I can make are on our local machines...

 

Those settings are from the ESET Remote Administrator Server, not from the actual client. I don't think you can get to those settings from within the client.

 

This setting can only be set via an ERA config. task (xml) or by creating a special registry value.

 

Was there any official resolution to this?

My environment is Ex2010 SP1, ERAS 3.1.11, ESET NOD32 4.2.67, and this is issue is also affecting a user w/Outlook 2007 in Cached Exchange Mode and a Blackberry device from a BES.

Can you post the registry changes necessary for this fix?

 

Berserker,

In my case, I ended up disabling NOD32 for Outlook. There appears to be a problem when the Exchange account has a BES counterpart... Since I can't do anything about the BES side, I disabled the Outlook integration.

 

Marcos can I get a copy of the registry file mentioned in this thread? I'm a home user and don't have access to that setting. Thanks

 

This is starting to really affect some of our users, some have had 30MB of conflicts in the sync folders!

Looking at the internet headers of the two emails, it seems the x-esetid is the only thing that changes

"current email" according to Outlook 2010

Code:

Message-ID: <20111020071933.2907613F21@Nagios3.magni.local>
Date: Thu, 20 Oct 2011 08:19:33 +0100
From: <nagios@Nagios3.magni.local>
MIME-Version: 1.0
Content-Type: text/plain
Return-Path: nagios@Nagios3.magni.local
X-MS-Exchange-Organization-AuthSource: NMNICAS.magni.local
X-MS-Exchange-Organization-AuthAs: Anonymous
X-EXCLAIMER-MD-CONFIG: 874f6da0-2996-4e1f-b954-140efccdf8a7
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
X-EsetId: D1BE4722A46B3D3082FF17

Conflicting email according to Outlook

Code:

Message-ID: <20111020071933.2907613F21@Nagios3.magni.local>
Date: Thu, 20 Oct 2011 08:19:33 +0100
From: <nagios@Nagios3.magni.local>
MIME-Version: 1.0
Content-Type: text/plain
Return-Path: nagios@Nagios3.magni.local
X-MS-Exchange-Organization-AuthSource: NMNICAS.magni.local
X-MS-Exchange-Organization-AuthAs: Anonymous
X-EXCLAIMER-MD-CONFIG: 874f6da0-2996-4e1f-b954-140efccdf8a7
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
X-EsetId: 83C83A2268FC5230D0896A

and the corresponding log

Code:

08:20:07 Message class: {SU:IPM.Note}
08:20:07 Mail Conflict Resolution
08:20:07 Local subject: {SU:** PROBLEM Service Alert: nmnicitrix/C:\ Drive Space is WARNING **}
08:20:07 Remote subject: {SU:** PROBLEM Service Alert: nmnicitrix/C:\ Drive Space is WARNING **}
08:20:07 Local Message Entry ID: {CB:70, LPB:0x00000000AECFA526B09E6A42A4E046735D9D03EF07008024C1FDC139BC40A804E941F8939CCE00000108B7F100001A7DA143E6B73C44861BEA2C1C113D27004140FFC28F0000}
08:20:07 Remote Message Entry ID: {CB:70, LPB:0x00000000AECFA526B09E6A42A4E046735D9D03EF07008024C1FDC139BC40A804E941F8939CCE00000108B7F100001A7DA143E6B73C44861BEA2C1C113D27004140FFC28F0000}
08:20:07 Local Message ChgKey: {CB:20, LPB:0x76CC3FA67FA3034A8A6DBC4E4D895EE7002D2E69}
08:20:07 Remote Message ChgKey: {CB:22, LPB:0x2CFB00906E8236489DAFE172A547F9B9000041B3BD57}
08:20:07 Local Message PCL: {CB:44, LPB:0x162CFB00906E8236489DAFE172A547F9B9000041B3BD4E1476CC3FA67FA3034A8A6DBC4E4D895EE7002D2E69}
08:20:07 Remote Message PCL: {CB:23, LPB:0x162CFB00906E8236489DAFE172A547F9B9000041B3BD57}
08:20:07 Checking local modifications
08:20:07 Compare property: 0x007D001F
08:20:07 Ignore property: 0x3FFA001F
08:20:07 Compare named property: EsetMessageFlag
08:20:07 Compare named property: Emon Scanner Build
08:20:07 Getting remote properties
08:20:07 Checking remote modifications
08:20:07 Compare (conflict) property: 0x007D001F
08:20:07 Local: {SU:Received: from Nagios3.magni.local by NMNICAS.magni.local

08:20:07 Not equal (conflict) property: 0x007D001F
08:20:07 Local modification: {07:19:48.0671  20/10/2011 [DD/MM/YYYY]}
08:20:07 Remote modification: {07:20:07.0265  20/10/2011 [DD/MM/YYYY]}
08:20:07 Conflict generated, remote item is winner

Running Outlook 2010, Exchange 2010 SP1, Eset 4.2.72.1

 

Are you running a BlackBerry Enterprise Server? Most of people I have seen who have this issue are running BlackBerry's. The BES servers interaction with exchange modifies the mail headers and so does ESET at the local machine. There's not actually anything wrong besides the fact that multiple things are touching the mail headers. To solve the problem on our end we removed Outlook Integration from ESET and no longer have the Sync Issues.

 

We do have a BES Express server, but only a handful of users are on it.

The example above was my own email and I do not have BES enabled for my account

 

Try disabling Outlook Integration to confirm it's actually being caused by ESET.

Advanced Setup > Miscellaneous > Email client integration > Integrate into Microsoft Outlook.

 

For the BES users out there, I found a solution.

At least, it works for me. For now.

I was also experiencing the sync issues for Blackberry users. Some had over 700 megs in their sync folder. So I started looking at the BES side and came across this link: http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB00139&sliceId=SAL_Public&dialogID=97424588&stateId=1%200%2097426457.

As explained in the post I added a registry entry "ProcessMailDelay" with a dword value of 60. After restarting the neccessary BES services, no more sync messages appeared.

In EAV, Outlook integration is ON, adding tags to scanned mails is set to NEVER, the rest of the settings are just the defaults.
We're using Exchange 2007, BES 5, Win 7, Office 2010, EAV4. All latest versions.

Hope this works for you as well.