Sync issues in Outlook

... to uncheck the "Integrate into Microsoft Outlook" option ... which isn't a solution ... shaun

 

We can make a special dll for you to test. The dll would have writing of all added message properties to messages on the server enabled. Currently they are added only on the client because of synchronization performance.

 

So that's why everyone has been complaining about receiving countless sync issues for the last few days! We have Outlook 2007 clients with an Exchange 2007 server. I have just pushed out a config change using the "Disable checking upon Inbox content change" policy item. Hopefully that will fix the issue for now.

Any update on this?

 

Outlook is crap and so is Exchange. Lock in for corps because of dumb IS Managers and support companies. Does anyone use Open Xchange?

 

That means ESET will not scan for viruses in the INBOX. Not good.

 

Maybe it would be better to post in another forum if you want to discuss Open Xchange or express you personal opinion about outlook/exchange. This thread is about sync issues in outlook.

 

Yet this is the advice of ESET support in this very thread: https://www.wilderssecurity.com/showpost.php?p=1527951&postcount=15 !

 

gmiest - Changing the "Disable on in-box change" will not fix the issue. I've tried every combination of settings in ESET to fix this issue with Cached Exchange Mode. The only thing that fixes it completely is to uncheck the options "Integrate into Microsoft Outlook".

Marcos mentioned a DLL that changes the way message headers are written that sounds like it could be a possible fix. Unfortunately I cannot test on my live Exchange server. Has anyone else tested this DLL?

 

Is there any update on this?

 

PM sent. Please let me know about the result.

 

As opposed to comprimising the scan of the mail VIA

I have found the following solution to work without comprimising the scans of incoming and outgoing mail. I have found this to be effective on 74 workstations over 4 Subnets (locations).

Advanced Setup>Email client protection

Append tag messages to recieved email:
To Infected Email Only
Append tag messages to sent email:
To Infected Email Only

This will still scan all the mail and it will only append ESET tags to the infected emails... Ideally I think people like seeing the mail was scanned when they recieve it as it makes them feel all fuzzy but I believe this is the next best soloution.

Running
Exchange 2007
SBS 2008
Eset Smart Security Business Edition V4 4.0.474.0
Outlook 2007
WinXP Pro SP 3
Vista Business SP 2


I also wanted to point out that fact that this seems to be an when using Outlook in Cached mode.
In fact I have tested on several workstations randomly around the office.
I can confirm that if you take Outlook out of cached mode this also resolves the problem and all email is still scanned.

I believe that the scan engine and tagging process is delaying the response back to the server and from the server back to the OST / Outlook client. While it is only in the milisecond range it is enough time to throw off the time between the server and the client. This will generate the error we are seeing and in fact I have seen this using other tools and addins as well. It happens becasue the OST reports a different time than what the server is actually seeing... Literrally in Milliseconds. And this is becasue those milliseconds are being taken and used as ESET does its job. The packet is then sent back to the server and the error is then generated, usually this will come with conflict notifications as well as sync errors.

Be forewarned that if you remove cached mode from the client computer you are relying soley on the WAN connection each and every time the person opens outlook unless they are on the LAN.
I can speak from experience that users will complain about "speeds" and they will be referring to the time it takes them to open outlook and start cruising their mail. It is not necessarily the Bandwidth speeds that will affect the slow open times of outlook but instead depends more on the size of the users mailbox and number of emails and folders etc because outlook needs to process all of these items each time it is opened. The bandwidth plays a small role but I have noticed that anything above 2mbps suffices for the data transfer between outlook and exchange, of course higher bandwidth is always better.

Hope this helps.

 

Hello,

we have the same Problem. But for me its EVERY mail which produces sync-problems - thats really annoying.

the modification resolution is:

14:57:51 Mail Conflict Resolution
14:57:51 Subject: {SU:}
14:57:51 EntryID: {CB:70, LPB:0000000069598EB1CB89F54B8DBF3F671241B05707007967CFA52EE6DF43A9896F44CF8038080000B11C4F3200007A20ADD6307AE040874CFFD06102C53E00400A2423DC0000}
14:57:51 Checking local modifications
14:57:51 Compare property: 0x007D001F
14:57:51 Compare named property: Emon Scanner Build
14:57:51 Compare named property: EsetMessageFlag
14:57:51 Getting remote properties
14:57:51 Checking remote modifications
14:57:51 Compare (conflict) property: 0x007D001F
14:57:51 Local{SU:Received: from server ([xxx.xxx.xxx.xxx]) by

server ([xxx.xxx.xxx.xxx]) with mapi; Thu, 25 Feb 2010

14:57:18 +0100

we tried this version 3 an 4 of nod32. its running on windows 7 64 bit

is there a (new) solution ?

regards, thomas

update:
after disabling the cache mode, the problem is gone, but this is no resolution for our notebook users.
so again: is there another solution ?

 

It appears the problem is caused between a conflict with ESET and our Blackberry Enterprise Server both manipulating message headers. The only mailboxes receiving sync issues are users with Blackberry's (in our environment).

- If I turn the blackberry off completely, the sync issues go away.

- If I leave Outlook off and send/receive e-mails from the Blackberry everything is fine. No sync issues when Outlook is restarted (until a new e-mail comes in).

- If Outlook is left open (while a user might be in a meeting, or another building) and e-mails are received/read on the Blackberry device simultaneously, then the sync issues happen every time.

Is anyone else with these Outlook Sync issues using Blackberry's on the same mailbox?

 

I have narrowed the issue down for my issues ..

Anyone who is using a blackberry with Blackberry Enterprise or Professional server is probably having this issue.

I can telll you that it is in fact an issue between the Blackberry and NOD32.

The problem is that Exchange Gets the mail and routes it to the Mail client.
BES also fwd its copy to the users blackberry..
I believe the sync and conflict occur immediately after the Message hits the blackberry.
Somewhere there is a header issue between NOD32 Exchange and BES or BPS and the OST.
Its probably becasue theres no NOD32 headers attached to the Blackberry copy and the sync reports a change not seen server side being submitted back. the Copy of the message that BES and BPS recieve are never sent to the Mailbox itself. They are routed to the blackberry prior to being sent to the mailbox in Exchange.
Exchange is probaly giving the errors to outlook as a warning of possible Header spoofing etc...


If youd like to test this for yourself
Turn off the blackberry of the user you are testing.
Send a test email and there will be no Sync or conflict issue.

Anyway this is the point I am at.
I can confirm at this point if the user that is having this issue also has a Blackberry attached to the BES or BPS and Exchange that Turning of the Blackberry will cease all Sync and Conflict issues.

After powering the blackberry back on the Sync and conflict issue did not show up for the test message. However after sending another test message the Sync and conflict errors returned.

I can confirm that with the blackberry Disabled or Powered off that the sync issues do not return.


This is not a fix simply an observation of trial and error.

Hope this helps and thoughts would be appreciated as I am working on this error in my own networks and would like to resolve the issue as soon as possible.

-PfrancoIT

**Edit - I realize rock posted the same. This message was started about 45 minutes prior to hitting submit as I was working on this at work. He must have posted while I had the reply screen up. Had I seen it I wouldnt have posted and would not have crazy lol.

 

hello again,

i can confirm, that users which are also blackberry-users have this problem.

is there a solution?

regards

 

Try the following:
- disable adding signatures to clean emails
- disable scanning of read emails and leave only scanning of received emails enabled

 

I tried this and it does not work for me. I as well believe the issue is in relation to the BES server and Exchange fighting over the modified conflicting headers.

If I turn off the blackberry device the issue goes away. When I turn the device back on, the issue is back. If I turn off BES services I no longer have the issue. As soon as BES is back up, the issue is present again.

This is creating a ton of duplicate emails that end up in "conflicts and sync issues" which is tying up our user inboxes pretty badly.

 

Does not work for me either. I've tried all sorts of combinations of settings for appending tag messages to messages/subjects. Tried turning on the setting "Disable checking upon inbox content change" with the same results. The only things that seem to fix this issue are:

- Disable ESET's Outlook integration
- Turn off the Blackberry
- Uninstall ESET completely
- Leave Outlook closed at all times

 

Is there any further word on this? Is it even a confirmed issue or is it being worked on?

I am going to call and create a case about this as it is affecting all of our users, I just find it strange that there isn't any further information on how to resolve the issue.

Right now the way it stands our users inboxes are getting filled up if they have a blackberry and disabling email protection isn't the most proactive thing we should have as a recourse.

 

With v. 4.2.35 installed, you can try importing this configuration file that will make email protection write as little information to scanned email as possible. Note that a minimum amount of information must be written to scanned emails so the sync issues may persist and the only way to get rid of them will be disabling email protection.

 

Marco's is this on the radar already to be fixed then or should I submit a ticket to ESET about the issue?

I already have nearly everything turned off without actually turning off the scanner for Outlook at this point. Do I at this point need to go through the channels to get this resolved or is ESET aware of the issue and will be actively working on a fix?

 

It looks like ERA v4.0.122.0 added a new setting into the Email Client > Setup. I noticed there is now a section labled "Enable resolution of Microsoft Outlook syncronization issues". The default value is 0 which is OFF, and 51 - All On. Does anyone know if this variable is for this issue and how it works?

 

Has anyone got any updates on this... I to would like to join this group in trying to resolve these annoying sync messages within outlook...

 

If messages are accessed from multiple devices it's normal that sync issues occur. When a message has been scanned, certain information about the scan must be written to the message which causes a sync issue when the message is opened from another device.

 

Marcos - Can you answer my question regarding the ERA setting I mentioned here?

Thanks!