mrac

Hi, Marcos. But what with simultaneous use? I have 6.4 EAV on work and home computer. On both computers Outlook 2016 connected to Exchange 2016. And every incoming message creates duplicate in "Conflicts" and error message in "Sync Issues" with text: LPB:0x0000000009ABE67FA57DCD42B536B5AC462A47A00700C6410E8A10E3DD48B465F9AEA49076D80000000014B90000C6410E8A10E3DD48B465F9AEA49076D80002899B61FD0000} 17:10:54 Remote Message Entry ID: {CB:70, LPB:0x0000000009ABE67FA57DCD42B536B5AC462A47A00700C6410E8A10E3DD48B465F9AEA49076D80000000014B90000C6410E8A10E3DD48B465F9AEA49076D80002899B61FD0000} 17:10:54 Local Message ChgKey: {CB:20, LPB:0xE8687295E5A14640814B0C128A1EFA7B0002D4F7} 17:10:54 Remote Message ChgKey: {CB:22, LPB:0xC6410E8A10E3DD48B465F9AEA49076D8000289EC8742} 17:10:54 Local Message PCL: {CB:44, LPB:0x16C6410E8A10E3DD48B465F9AEA49076D8000289EC874114E8687295E5A14640814B0C128A1EFA7B0002D4F7} 17:10:54 Remote Message PCL: {CB:23, LPB:0x16C6410E8A10E3DD48B465F9AEA49076D8000289EC8742} 17:10:54 Checking local modifications 17:10:54 Ignore property: 0x3FFA001F 17:10:54 Compare named property: EsetMessageFlag 17:10:54 Getting remote properties 17:10:54 Checking remote modifications 17:10:54 Compare (conflict) named property: EsetMessageFlag 17:10:54 Local: {I4:0} 17:10:54 Remote: {I4:1} 17:10:54 Not equal (conflict) named property: EsetMessageFlag 17:10:54 Local modification: {14:10:49.0240 25/07/2016 [DD/MM/YYYY]} 17:10:54 Remote modification: {14:10:48.0545 25/07/2016 [DD/MM/YYYY]} 17:10:54 Conflict generated, local item is winner How to fix this? As I remember in older versions (4 or 5) there was an compatibility option in EAV, but now it absent.

We have the same issue. Exchange 2016 servers, migrated from Kaspersky to EAV 6.3 (about 300 computers). And on 3 of them new e-mails stopped coming (Updating Inbox). 1. On 1 PC: Outlook 2010 x86 installed (Windows 7 x64). I deleted Outlook profile, and re-download mail from server. New messages appeared. About 3 hours later, same computer, new messages stopped coming again. After installing Outlook 2013 x64 and updating, mail started working normally. 2. On two other PCs (Outlook 2013 x86, Windows 7 x64/Windows 10 x64) also stopped coming mail. Restart of computer didn't help. After disabling Outlook ESET add-in, new messages came. Yes, 3 PCs from 300 - is not a big percent, but unfortunately it was computers of top management (big mailboxes 10-15 GB) and we temporary disabled ESET Outlook add-in for all.