none
EWS crashes on Windows Server 2012 RRS feed

  • Question

  • Hi,

    As we are migrating to Exchange server 2013, we are converting existing VB script agents on Exchange Server 2003 public folders.  We are using EWS managed API 2.0, C# for development. It works fine on the development machine. I can access the public folders and do the desired functionality. When I move the executable to Windows Server 2012, where the Exchange Server 2013 is, it crashes with the following error message:

    Problem Event Name: CLR20r3

      Problem Signature 01: test.exe

      Problem Signature 02: 1.0.0.0

      Problem Signature 03: 52b0e980

      Problem Signature 04: TestAgents

      Problem Signature 05: 1.0.0.0

      Problem Signature 06: 52b0e980

      Problem Signature 07: d

      Problem Signature 08: 10

      Problem Signature 09: System.IO.FileNotFoundException

      OS Version: 6.2.9200.2.0.0.272.7

      Locale ID: 1033

      Additional Information 1: ab8c

      Additional Information 2: ab8c7f0d4887f334a1aa9f1cb12f1875

      Additional Information 3: 3123

      Additional Information 4: 3123444efd1f0f58a96f5fa5f54a8618

    .NET framework version is 4.5 on both the machines and EWS managed API is installed on both the machine

    Would like to know, how to fix this.

    Thanks for your help in advance!


    Wednesday, December 18, 2013 7:42 PM

Answers

  • Its looks like your application is crashing rather then EWS, eg the exception is

    System.IO.FileNotFoundException

    Is your code looking try to load or save a file to a particular location ?

    It could be your code can't load the EWS Managed API assemblies (eg permission errors or bitness issue eg you have compiled a 32 bit application and you installed the 64 bit version of the Managed API.) You can use something like process monitor to look at what files it's try to access. You may want to try just copying the Managed API dll to the same directory as your exe is.

      As a general rule if you can you would be better not to run the code on the Exchange Server directly. With EWS there will be no performance benefit and if your application leaks memory or has any other issue (eg high CPU usage) then not running it directly on a Exchange server will avoid your application causing poor Email performance (or an outage).

    Cheers
    Glen

    • Marked as answer by ysku Monday, July 21, 2014 4:58 PM
    Thursday, December 19, 2013 4:52 AM