I'm developing an interface between Exchange (2007) and our application. Everything works fine, but i noticed a problem, when Exchange reboots. Everytime after a reboot my interface needs much time to connect to exchange. Sometimes so long, that i get a timeout. When i try to connect again, the connection is very fast. So only the frist time after a reboot it takes more time. So i tried it with OWA also, to test, if the problem is in my interface or in exchange. And OWA have the same behavior like my interface. So i started to locate the problem. I figure out, that the exchange-websites or services, witch are hosted by the IIS are the problem. Wenn i restart this websites/services my interface and OWA needs much time to connect for the first time. After the first time i goes very fast. So in need to know, if there are some options in exchange, or IIS oder the websites/services itself, witch can solve my problem, because i don't know IIS very well.

Hi, This is normal. When rebooting IIS service, it droped all cached connection information between the EWS programs and EWS service. So after rebooting, the program needs to take some time to perform the authentication and load the features from EWS service. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Very pitty. Ok, i have to deal with it.

Now i have a "solution". I made a powershell-script, witch uses the dll's from the EWS Managed API and retrieve the inbox of any mailbox, so that EWS can "wake up". This isn't elegant, but it works somehow.