Getting a 401 with EWS? Read this before opening a support case!

If your getting a 401 with an API going against Exchange or basically anything then the issue is most likely with your credentials and NOT your code. Instead of jumping to the step of opening a support case do the following: Recheck your login information. Check the user id used, password and domain information. Logins…

0

EWS ServerBusyException – The server is too busy – for you

So… you got an ServerBusyException, eh? You might have seen it thrown as this in your code: Microsoft.Exchange.WebServices.Data.ServerBusyException: The server cannot service this request right now. Try again later. The server is not overloaded overall and the call is reaching EWS and EWS is responding with a throttling error. When you see ServerBusyException in the…

0

Updating Visual Studio generated proxy classes for EWS development.

Something I would like to highlight are issues with generated proxy classes for EWS development. We support Visual Studio generated proxy classes for EWS development – no other proxy generated classes are supported for EWS development.  I’m going to provide some basic information so that you have a starting point for cases involving EWS proxy…

0

About: Exchange service XSD and WSDL

Some developers use tools which work against XSD and WSDL.  Below is some information on the subject. Note that support is provided for proxy class generation only with Visual Studio – this means third party generators are not supported. The XSD is updated per EWS version: EWS schema versions in Exchange https://msdn.microsoft.com/en-us/library/office/dn741586(v=exchg.150).aspx It’s best to…

0

Sample: C# code to have EWS Managed API code go through Fiddler on the same machine.

Having calls done with the EWS Managed API go through Fiddler is very easy. Below is an example. public static void SetProxyToFiddler(ref ExchangeService oService) { System.Net.WebProxy oWebProxy = null; oWebProxy = new System.Net.WebProxy(“127.0.0.1”, 8888); oService.WebProxy = oWebProxy; } Here is how you might call it: ExchangeService oService = new ExchangeService(); oService.Credentials = new WebCredentials(“test@contoso.com”, “test”);…

0

When a certain time zone does not work with the EWS Managed API…

When using EWS with some time zones you might run into issues with getting to work.  As an example, you might run into issues with Russian Standard Time or calling GetUserAvailabilty.  You might even see the “The specified time zone isn’t valid” error. There are usually work-arounds for such issues. The need to keep Windows…

0

EWSEditor 1.18 Released

This new release has a lot of new features which have been needed and requested countless times.  Now you can pull in lists of properties you want to see, search calendars, export data for items into CSV files or as binary files. These lists of properties you can pull in are ones you can define…

0

EWSEditor 1.17 Released

1.17 – 6/30/2016 – 10/20/2016 Added setting of Post Address Index to the Contacts window. Development check-in: In the Services window, I changed the default the Auth Authority for oAuth with Exchange Online. Fixed spelling issues in the Session window. In the notification sample windows, I added a note that subscriptions did not support delegate…

0

Subscriptions with EWS and EAS don’t get notifications when read status is changed.

This is known behavior. If another activity happens which triggers a notification, then you would likely get a notification for the update on the read status change at that time.  Read receipt is the only ping that tells you ‘message has been read’.   Read state changes are pushed with sync, but don’t trigger a sync …

0

EWSEditor 1.16 Released

I’ve done a lot of clean-up in EWSEditor and added a few needed features for this release. I would like to highlight one major change with EWSEditor in this release: Prior all versions of EWSEditor did not use COM objects. This version uses CDOSYS in order to provide a new feature – the ability to…

0