Coexistence Manager for Notes 3.9.2 - FBC Scenarios Guide

Exchange Server Location: How should CMN’s F/B Connector route free/busy queries to the coexisting Exchange environment? Mark (or circle) one of these, and collect the information associated with that option:

NOTE: All queries for Exchange users' F/B information must pass through an Exchange EWS, which facilitates communications between Exchange and the CMN Exchange FBC service. In an Exchange environment with a single EWS at a known fixed location (URL), you can point the FBC service directly to the E‘WS by specifying the EWS URL and host name. If there is no single Exchange EWS with a known fixed location, the FBC service can query the Exchange Autodiscover service, which tracks and reports the current location of an available EWS. If you will coexist with an Exchange environment where you don't know the location of either the EWS or the Autodiscover endpoint, CMN service will have to search the network for the connection.

NOTE: If coexisting with Microsoft’s Office 365: Select the Autodiscover Endpoint option and set the Exchange Autodiscover URL to Microsoft’s Autodiscover URL: https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc Note, however, that this is a Microsoft URL subject to change, in which case this connection and the Free/Busy Connector would fail. Remember this if you set the Exchange Autodiscover URL to the Microsoft URL, and CMN’s F/B Connector works fine for a time but then suddenly and consistently fails. The most likely cause is a change in Microsoft’s Autodiscover URL. Contact Microsoft to get the new URL, or select Autodiscover Only (below) instead.

Exchange Username: Admin account the F/B Connector should use to access data and features in Office 365. Leave this field empty unless you are connecting to Office 365, or to a local on-premises Exchange that isn't in the same domain as the CMN admin server. In those cases an entry here is mandatory.

Appendix: Troubleshooting the FBC

This Appendix describes the most common problems encountered when installing and using CMN’s FBC, and provides suggestions and procedures that are most likely to resolve them. Many issues can be resolved quickly by reviewing this short list of preliminary checks before calling Quest Support:

Free/Busy Connector Issues

A likely cause is insufficient IIS Virtual Memory. Try increasing IIS Virtual Memory to 768MB and perform an IIS Reset for the change to take effect.

If an Outlook client repeatedly crashes during F/B lookups, and you are running an Exchange 2013 or 2010 Client Access Server, the cause may be a known issue in the combination of .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2. For more information, see Microsoft’s KnowledgeBase article, and Microsoft Support can point you to a HotFix to resolve this problem.

If you are coexisting with Office 365, and CMN’s F/B Connector works fine for a time but then suddenly and consistently fails, the most likely cause is a change in Microsoft’s Autodiscover URL.

Our configuration instructions for the F/B Connector (see the Exchange Free/Busy screen notes for the Exchange F/B Connector in CMN’s Management Console, CMN User Guide chapter 4) suggest that, for Office 365, you select the Autodiscover Endpoint connection method, and set the Exchange Autodiscover URL field to this Microsoft URL: https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc

But this is a Microsoft URL that is subject to change, in which case the connection would fail and the F/B Connector would fail. In that case, contact Microsoft to get the new URL, or select the Autodiscover Only method instead.

If Outlook users get certificate errors when logging into Outlook, after CMN's Free/Busy Connector has been configured, the cause likely is a name mismatch in the certificate. Verify that the certificate in use on the Exchange server for port 443 is accepting all required named domains. If the error shows a name mismatch, the certificate may not have the required domain.

Error message: The maximum message size quota for incoming messages (65536) has been exceeded, you must increase the quota by using the MaxReceivedMessageSize property on the appropriate binding element.

If you are using OWA or Outlook and querying free/busy information for a Domino user, edit the Web.Config file in the EWS folder on the CMN Web Server:

Error message: The maximum message size quota for incoming messages (65536) has been exceeded.

This means you must increase the quota by using the MaxReceivedMessageSize property on the appropriate binding element.

If you are using Lotus Notes and querying Free/Busy information for an Exchange user, edit the QCalCon.exe.Config file on the Domino server:

Error message: 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.

If you are using OWA or Outlook and querying free/busy information for a Domino user, edit the Web.Config file in the EWS folder on the CMN Web Server:

If you are using Lotus Notes and querying Free/Busy information for an Exchange user, edit the QCalCon.exe.Config file on the Domino server:

To configure IIS 6.0 with an xml extension handler:

To configure IIS 7.0 with Integrated Application pools:

An Exchange-to-Notes F/B query may generate this error:

... if the IIS_IUSRS user does not have List folder / read data permission. To resolve this, grant the user that List folder / read data permission.

Check the Foreign Domain by ensuring the following:

In some installations, the Domino server does not properly route free/busy requests to the registered Foreign Domain. You can determine where the free/busy requests are being routed by temporarily enabling debug messages for the Domino Schedule Manager.

To enable debug messages:

To get F/B info for an Exchange user via the FreeBusyBridge Web Service:

To get the URL of the Exchange EWS: