In some environments, there may be intermittent issues with free busy requests from Exchange to Domino direction and you may see "There server was busy" and the following error in EWS.log file on CMN server:
ERROR QuestEWSService - GetUserAvailability() System.TimeoutException: This request operation sent to net.tcp://localhost:8960/FreeBusyService did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
1- Go to C:\Program Files (x86)\Quest Software\Quest Coexistence Manager for Notes\Free Busy Connector\EWS
2- Open web.config
3- Look for <binding name="FreeBusyClientSettings" openTimeout="00:01:00" receiveTimeout="00:01:00" sendTimeout="00:01:00" closeTimeout="00:01:00">
Change the timeouts to 5:00
4- You should have the following: <binding name="FreeBusyClientSettings" openTimeout="00:05:00" receiveTimeout="00:05:00" sendTimeout="00:05:00" closeTimeout="00:05:00" >
5- Save and close
6- Restart CMN FreeBusy Services
The number you use will depend on the environment. This will only allow the slow requests to take longer and not slow down normal Free/Busy requests. Requests with a large number of users/resources and or over Wan links are the ones that will be considered slow requests.