Sync issues in Outlook

My NOD32 4.0 is causing sync issues in Outlook with Cached Exchange mode. I have the latest build. The error is below. I implement the fix below, but this does not seem to be an acceptable solution. Has anyone else had issues with this? Eset support is now ignoring me for some reason.

Eset suggested this fix:

Please do the following and see if this makes a difference:
1. Open the main program window.
2. Press the F5 key to enter the Advanced Setup tree.
3. Go to Miscellaneous > Email client integration.
4. Disable the Integration with MS Outlook and save changes.

Let us know what you find.

Here is the error in the sync issues folder:

15:07:36 Mail Conflict Resolution
15:07:36 Subject: {SU:ESET Support Case Update: 292612 - Sync issues}
15:07:36 EntryID: {CB:70, LPB:000000004BF5454C52EACB428A4F46F066164BF107005941AFB9E573B24097C380FF
83062DC800000001BEDF000084F3D1E0D3B8F24A9132180FE4FD4F9C0000CAE75ECF0004}
15:07:36 Checking local modifications
15:07:36 Compare property: 0x007D001F
15:07:36 Compare named property: EsetMessageFlag
15:07:36 Compare named property: Emon Scanner Build
15:07:36 Getting remote properties
15:07:36 Checking remote modifications
15:07:36 Compare (conflict) property: 0x007D001F
15:07:36 Local{SU:Received: from nmail3.netsuite.com (167.216.129.171) by sbs2003.mydomain.com

(192.168.0.201) with Microsoft SMTP Server id 8.1.358.0; Fri, 1 May 2009

15:07:23 -0400

Date: Fri, 1 May 2009 12:07:24 -0700

From: ESET Customer Care <ccreply@eset.com>

Reply-To: ESET Customer Care

<cases.438708.345157_5269867_340407.9a184cb2e6@cases.netsuite.com>

To: <me@mydomain.com>

CC: <dstrome@eset.com>

Message-ID: <17675158.2264.1241204844509.JavaMail.root@acct-java077.svale.netledger.com>

Su
15:07:36 Remote{SU:Received: from nmail3.netsuite.com (167.216.129.171) by sbs2003.mydomain.com

(192.168.0.201) with Microsoft SMTP Server id 8.1.358.0; Fri, 1 May 2009

15:07:23 -0400

Date: Fri, 1 May 2009 12:07:24 -0700

From: ESET Customer Care <ccreply@eset.com>

Reply-To: ESET Customer Care

<cases.438708.345157_5269867_340407.9a184cb2e6@cases.netsuite.com>

To: <me@mydomain.com>

CC: <dstrome@eset.com>

Message-ID: <17675158.2264.1241204844509.JavaMail.root@acct-java077.svale.netledger.com>

S
15:07:36 Not equal (conflict) property: 0x007D001F
15:07:36 Local modification: {D:1, M:5, Y:2009 H:19, M:7, S:26, MS:189}
15:07:36 Remote modification: {D:1, M:5, Y:2009 H:19, M:7, S:27, MS:652}
15:07:36 Conflict generated, remote item is winner

 

Hello chrisf,

Does the problem still persist after disabling Outlook integration? This will give us a good idea of weather the ESET software is actually causing the problem.

 

Disabling Outlook integration resolves the issue.

 

Hello chrisf,

Try setting the compatibility mode inside the ESET software to Maximum Compatibility to see if this corrects the problem. The Knowledgebase article below shows where you can find this setting:

http://kb.eset.com/esetkb/index?page=content&id=SOLN527

 

Hi Wayne I'm having exactly the same problem as Chris some of my Outlook clients are recieving multiple messages like this. I will also try the solution you suggested when in the office tomorrow.

 

Good morning,

We are having the exact same issue. We're testing Nod32 on a couple of XP desktops and they are all experiencing the same issues now. We're running Exchange 2007 which has Symantec Anti-Virus ver. 10 installed to it, but it does not scan e-mail traffic. It is simply provides virus protection to that local machine.

Thanks.

 

Quick Update!

I believe I have resolved my particular situation as a result of suggestions from another forum. Here are those details:

Hope someone finds this useful.

 

The sync issues seem to be related to writing to message headers whilst Exchange 2007 seem too sensitive to such modifications. Our developers are investigating it and will try to find a workaround. These sync issues do not indicate any serious problems so you configure Exchange to flush the Sync issues folder on a regular basis.

 

Has there been any progress on resolving this issue? I am on a hosted Exchange solution and do not have direct access to Exchange configuration, so scheduled flushing of the Sync Issues folder is not an option.

Thanks.

 

Have you tried "Disable checking upon Inbox content change" to see if the issue goes away?

 

I have, and it does not resolve the issue.

 

From the "Modification Resolution" message found in the Sync Issues folder:

13:48:00 Mail Conflict Resolution
13:48:00 Subject: {SU:XXXXXXXXX Training Key }
13:48:00 EntryID: {CB:70, LPB:00000000A17CFB879C304C489546311284FBB4A5070087817B430D829445B17D5FB9C98147
D500000005ADC9000087817B430D829445B17D5FB9C98147D5001F992022320000}
13:48:00 Checking local modifications
13:48:00 Compare named property: EsetMessageFlag
13:48:00 Compare named property: Emon Scanner Build
13:48:00 Getting remote properties
13:48:00 Checking remote modifications
13:48:00 Compare (conflict) named property: EsetMessageFlag
13:48:00 Local{L:0}
13:48:00 Remote{Error (0x8004010F)}
13:48:00 Not equal (conflict) named property: EsetMessageFlag
13:48:00 Local modification: {D:13, M:8, Y:2009 H:17, M:47, S:48, MS:46}
13:48:00 Remote modification: {D:13, M:8, Y:2009 H:17, M:47, S:54, MS:491}
13:48:01 Conflict generated, remote item is winner

 

So I guess I'm going to have to assume the answer is either

1. no, or
   
2. we don't care

 

Any progress on this issue by ESET developers? I don't want to disable ESET from scanning my Outlook 2007 email, for example, when a new message arrives in my inbox.

 

We are trying to find a workaround. Ticking the "Disable checking upon inbox content change" in Miscellaneous -> Email client integration should do the trick, but this might cause some received emails not to be scanned for spam and threats.

 

Under what conditions does "but this might cause some received emails not to be scanned for spam and threats" apply? thanks, ym

 

I appreciate this will stop the sync issues but surely it rather negates the use of eset nod32?
We are suffering this issue with Exchange Server 2003 & Outlook 2007 clients. It's by no means every message, probably less than 5% but still annoying.

E.g.

Code:

07:50:14 Mail Conflict Resolution
07:50:14 Subject: {SU:FW: IMPORTANT: xxx.co.uk is due for renewal}
07:50:14 EntryID: {CB:70, LPB:00000000F4E07BE43504204EB6E06A9D256F6BC70700CB46E12763B70B4F9D66FFFA8025A19C0000000014880000805268CD1106374284495A1CC018D9DF00000057A4290000}
07:50:14 Checking local modifications
07:50:14 Compare named property: Emon Scanner Build
07:50:14 Getting remote properties
07:50:14 Checking remote modifications
07:50:14 Compare (conflict) named property: Emon Scanner Build
07:50:14 Local{L:5515}
07:50:14 Remote{L:5503}
07:50:14 Not equal (conflict) named property: Emon Scanner Build
07:50:14 Local modification: {D:24, M:8, Y:2009 H:6, M:50, S:12, MS:56}
07:50:14 Remote modification: {D:21, M:8, Y:2009 H:14, M:40, S:17, MS:194}
07:50:14 Conflict generated, local item is winner

NB Have edited domain name to protect the guilty.

ETA: ESET NOD32 4.0.424.0

 

Spoke to tech support about this.
To stop ESET adding the offending tags to emails change advanced settings:
Antivirus and antispyware>Email client protection>Alerts and notifications
Change Append tag messages... to Never

Can't confirm this works yet but seems reasonable.

 

This does not work for me. I continue to experience sync issue messages regardless of the state of this checkbox.

EDIT: I upgraded to NOD32 v4 yesterday, set the same security options as previously for Outlook, and the problem seems to have stopped. Prior to the upgrade I was running v3.

 

Belay that edit . . . the problem has not stopped. The sync error messages have changed, though:

Code:

11:42:55 Mail Conflict Resolution
11:42:55 Subject: {SU:*subject deleted for posting to Wilders*}
11:42:55 EntryID: {CB:70, LPB:00000000A17CFB879C304C489546311284FBB4A5070087817B430D829445B17D5FB9C98147D500000005ADC9000087817B430D829445B17D5FB9C98147D5001FEAFA7E0A0000}
11:42:55 Checking local modifications
11:42:55 Compare property: 0x007D001F
11:42:55 Critical stop property: 0x10090102
11:42:55 Local modification: {D:2, M:9, Y:2009 H:15, M:41, S:35, MS:578}
11:42:55 Remote modification: {D:2, M:9, Y:2009 H:15, M:41, S:45, MS:0}
11:42:55 Conflict generated, remote item is winner

 

One week on and no issues.

 

Have the same problem here. Tryed all the solutions but i still have the issue
Any Idea?

 

Here's my sync issue -

20:27:24 Compare (conflict) named property: Emon Scanner Build
20:27:24 Local{L:6003}
20:27:24 Remote{L:5783}
20:27:24 Not equal (conflict) named property: Emon Scanner Build
20:27:24 Local modification: {D:9, M:11, Y:2009 H:1, M:27, S:6, MS:104}
20:27:24 Remote modification: {D:9, M:11, Y:2009 H:1, M:27, S:19, MS:104}
20:27:24 Conflict generated, remote item is winner

So - i might stand a chance of things working if i keep all my AV apps as the exact same version, but this is nutty. I think this boils down to NOD32 should read but not change any of the fields in an Outlook item. At least give the option to do so. This is causing gigs of sync issues on my client's systems.

 

to bring it back to the top ... we have the same issue with version 3 and 4 ras/rac 2/3 ... exchange 2003 clients outlook 2003/2007

 

Yes, we are having the same issues also, but only on clients using cached Exchange mode. 4.0.474 didn't help any with this issue. I haven't tried the 4.2 beta yet to see if it's been fixed. The only fix we found on this issue was to uncheck the "Integrate into Microsoft Outlook" option.