Emet 4.1 crashes outlook (gsyncit plug-in) RRS feed

  • Question

  • I have a plugin to sync contacts and calendar data (outlook <-> google). Running outlook 2010 64 bit.


    EMET 4.1 is crashing outlook, with no log source data from EMET. Instead, I get a error about a .NET assembly failing and outlook crashes. (I had to complete disable all EMET checking on Outlook to get it to work again). I thought that just ROP and SEHOP would be enough, but that was not true.

    Here is the event log item:

    Log Name:      Application

    Source:        Application Error

    Date:          3/28/2014 12:35:56 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      ysg4206.draper.com


    Faulting application name: OUTLOOK.EXE, version: 14.0.4760.1000, time stamp: 0x4ba8ff82

    Faulting module name: mscorwks.dll, version: 2.0.50727.5477, time stamp: 0x5265c8ee

    Exception code: 0xc0000005

    Fault offset: 0x0000000000501cc0

    Faulting process id: 0x4e0

    Faulting application start time: 0x01cf4aa0bb7afc5e

    Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE

    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll

    Report Id: 090acbee-b697-11e3-9993-a4badb036ef9

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


        <Provider Name="Application Error" />

        <EventID Qualifiers="0">1000</EventID>




        <TimeCreated SystemTime="2014-03-28T16:35:56.000000000Z" />




        <Security />













        <Data>C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE</Data>






    Dr. YSG

    Wednesday, April 9, 2014 7:20 PM

All replies

  • This is an old thread but I wanted to post my solution in case someone runs into the same problem. The issue seems to be the interaction between Outlook 64-bit, the gSyncit 64-bit plugin and EMET. I tried EMET 4 and 5 with the same results. However, switching to Office 32-bit and gSyncit 32-bit fixed the problem for me. Switching to 32-bit is not a solution for everyone, but after reading the Technet articles for Office 2010 (http://technet.microsoft.com/en-us/library/ee681792%28v=office.14%29.aspx) and Office 2013 (http://technet.microsoft.com/en-us/library/ee681792%28v=office.15%29.aspx), I did not see a specific need for 64-bit in my case.

    I hope this helps you Dr YSG, and anyone else running into the same issue.


    Tuesday, November 11, 2014 12:37 AM