none
Issues with EWS API 2.2 RRS feed

  • Question

  • Hello Community,

    this is my first entry, so if i do not give all necessary informations, please let me know!

    I have 2 issues after installing the actual EWS API on my Exchange 2016 CU8 Server:

    - it is no longer possible to use the out of office assistant (Abwesenheits-Assistent in german)

    - connecting via Outlook 2016 for Mac is nearly impossible: permanent crashes, extrem latency, completely unusable

    After deinstalling EWS API everything went back fine, no issues at all.

    What can i do?

    At the end i need the API for my new scripts i want to use?!

    Thanks for every hint!

    Kind regards

    Joe

    Sunday, April 29, 2018 8:15 AM

All replies

  • I had terrible performance issues when installing the EWS API directly on an Exchange 2016 mailbox server as well.

    What I did was install the EWS API on my DAG witness server, which has the Exchange Management Tools on it. Works perfectly!

    Here's my blog entry for reference:

    https://exchangeitup.blogspot.com/2017/02/exchange-2016-100-cpu-and-event-id-5011.html


    My Blog: http://exchangeitup.blogspot.com My Twitter: http://twitter.com/ExchangeITup

    Sunday, April 29, 2018 4:03 PM
  • The version your installing is probably overwriting a later version that is installed by Exchange or one of the pre-reqs just check the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Web Services registry entry. 

    I would suggest you search for the Microsoft.Exchange.WebServices.dll and load that assembly from wherever its installed . Another option is if you just copy the Dll's from another machine rather then using  the installer (which just creates a couple of registry entries)  and then load them directly from that will work without clashing with anything else (eg it loads in its own app domain so shouldn't affect anything else)

    That all said running scripts directly on any Exchange server is a bad idea because EWS is a web services your not going to get any performance benefits over running then from a machine next door while a poorly performing script is more likely to reduce the performance of the server to the end user's

    Cheers
    Glen

    Monday, April 30, 2018 12:25 AM