What is the easiest EWS call to test connectivity?

Among all, "Operations with Exchange Web Services"). I am looking for the simplest option that I can initially use to check if my connection with the EWS endpoint is connected.
The low-level code that I use to create and execute SOAP calls expects valid results, so any operation that I use should not return an error message.

I reviewed a few, but did not find them satisfactory:

  • GetServerTimeZones is only supported with Exchange 2010, and I need 2007+

  • ResolveNames requires a (partial) username, but I want it to be independent of the user. In addition, it may return errors (do not match) or maybe hundreds of matches (match with "e").

  • GetUserConfiguration works for the current user, but is only supported since 2010.

Any other ideas?

+4
source share
1 answer

I decided to use ResolveNames - I need a user for further processing.

This gives me the opportunity to perform several checks at once: general connectivity, user exists, version of Exchange server, etc.

EDITED Aug 2 2013

I switched to using FindFolder , this simplified my code even more.
This changes the "user exists" check to the "default calendar folder exists" check, which the application assumes.

There is another assumption in the code, namely that there is a time zone of W. Europe Standard Time , but, as my original question pointed out, I can only verify that for Exchange 2010 and later.

+2
source

Source: https://habr.com/ru/post/1480955/


All Articles