Chat now with support
Chat with Support

Coexistence Manager for Notes 3.8.2 - FBC Scenarios Guide

About the CMN Documentation Introduction On-premises Exchange or hybrid O365 using shared (single) namespace On-premises Exchange or hybrid O365 using separate namespaces Non-hybrid O365 using shared (single) namespace Non-hybrid O365 using separate namespaces Appendix: FBC Planning Worksheet Appendix: Troubleshooting the FBC

Exchange Public Folder Writer | Active Directory Contacts

| Active Directory Contacts

AD Access Credentials:

Active Directory Domain: Name of domain where Active Directory resides (e.g., mydomain).
User Name: Name of a user account who has access rights to Active Directory.

AD Extension Attribute:

Active Directory Extension Attribute Number: The number of an AD extensionAttribute that can be used to filter the list of F/B users. (The number here specifies a particular extensionAttribute[#] in AD.)
NOTE: A corresponding DC connector must be configured with an attribute assignment that matches the AD Extension Attribute Number and Value you designate here for this purpose. This is configured by the Attribute Mapping / Add Rule feature in the Directory Connector’s Advanced Settings, as described in the Directory Connector chapter of the User Guide.
Active Directory Extension Attribute Value: The value of the AD extensionAttribute to use to filter AD contacts for this public folders F/B feature.

 

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:

Review the component log file(s). You can find valuable information about component errors and warnings in the components’ respective log files. If you call Quest Support and a support engineer can't immediately identify the problem, typically he/she will ask for copies of your log files.
Verify system requirements. CMN problems are often traced back to inconsistences between the product’s system requirements and the host network’s hardware or software specifications. You may therefore save yourself some time and trouble by simply comparing your local system to the CMN system requirements. System requirements are documented in the Release Notes that accompany every CMN RTM release.
Is this a known limitation or known issue? Check the Known Limitations appendix of the CMN User Guide, and the Known Issues section of the current CMN Release Notes, to see whether the problem might simply be a known limitation of the process.
What has changed since the last server restart? Configuration values are normally updated only when a service is restarted. This can hide a pending problem for weeks or longer until an administrator restarts the services and the changes are applied.

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 2007 or 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.

When a CMN Public Folder Writer Service F/B query to Domino fails, a likely cause is simply an invalid user in Domino. For example, a user exists in the Notes database but his/her mailfile has been moved or corrupted, or a user has been deleted, but was left in \mail. In this case, a corresponding contact is created in AD, making the user seem eligible for a F/B query. To solve this problem, simply remove invalid users from Domino, or set an AD attribute to identify valid users.

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.

Ensure the Foreign Domain document has been created. The procedure to do this is in the respective scenario chapters, step 5-1 (Synchronize Exchange and Domino directories), under the heading To synchronize Exchange mail users to Domino contacts. After making changes to the Foreign Domain Document, restart the Domino server.
Set the service logon credentials for the Quest CMN Exchange Free/Busy Connector service (see the Exchange Free/Busy screen notes for the Exchange F/B Connector in CMN’s Management Console, CMN User Guide chapter 4).
Set the Exchange credentials using the Set-CmnExchangeFreeBusyConfig cmdlet.
Ensure the EwsUrl is properly configured to the Exchange Web Services URL for your Exchange server. If you are using a hosted Exchange or do not know what the Exchange Web Services URL is, use the Get-CmnExchangeWebServicesUrl cmdlet (see PowerShell to configure the F/B Connector).
After verifying the EwsUrl is correct, navigate to the URL using a Web Browser such as Internet Explorer. Verify that you can access the URL using the same credentials used by the Exchange service without any additional credential prompts and without any certificate errors.
b
Type get-CmnExchangeFreeBusyConfig.
c
Ensure the URL specified by the EwsUrl property resolves properly in Internet Explorer with no certificate errors. If a certificate error is found, add the Exchange certificate to the Trusted Root Certification Authorities folder.

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:

Add the maxReceivedMessageSize property to the file and set it to a large value:

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:

1
Increase the maxReceivedMessageSize property to a larger value:

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:

Increase the value of the SendTimeout property:

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:

1
Increase the value of the sendTimeout property:
Verify that Add-AvailabilityAddressSpace has been executed on the Exchange server (for example, Add-AvailabilityAddressSpace -ForestName <smtpdomain> -AccessMethod OrgWideFB -UseServiceAccount $true). To verify that the cmdlet has run, type (on the Exchange Management Console): Get-AvailabilityAddressSpace
Ensure you can ping <smtpdomain> or autodiscover.<smtpdomain> and that it resolves to the computer running the CMN F/B connector.
Open a web browser such as Internet Explorer and type https://<host>/autodiscover/autodiscover.xml (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>, and ensure an .xml file appears and that you do not have any certificate errors.
If the .xml file displayed has the text "this is a placeholder file", then IIS is not properly configured with an XML Handler.

To configure IIS 6.0 with an xml extension handler:

2
Right-click Autodiscover and click Properties.
3
On the Virtual Directory tab, click Configuration.
4
On the Mappings tab, click Add.
5
• For 32-bit IIS: %windir%\Microsoft.Net\Framework\v2.0.50727\aspnet_isapi.dll
• For 64-bit IIS: %windir%\Microsoft.Net\Framework64\v2.0.50727\aspnet_isapi.dll
6
Enter .xml for the extension.
7
Click OK on all dialog boxes.

To configure IIS 7.0 with Integrated Application pools:

2
Ensure the Managed Pipeline mode for CMxAutodiscoverAppPool and CMxEWSAppPool are both set to Integrated.
3
Access https://<host>/autodiscover/autodiscover.xml, and ensure you do not see the error message “this is a placeholder file.”
4
From the Exchange server, open a web browser and type https://<host>/EWS/Service.asmx (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>), and ensure an .xml file appears and that you do not have any certificate errors.
Ensure that the appropriate DNS entries have been made to route <smtpdomain> or autodiscover.<smtpdomain> to the computer running the CMN Free/Busy Connector.
On the computer running CMN F/B Connector web services, run the Get-CmnAutodiscoverConfig cmdlet, and verify that the CmnAvailabilityUrl is set to https://<host>/EWS/Service.asmx (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>).
On the computer running CMN free/busy connector web services, ensure that Get-CmnEwsConfig is configured to communicate to the correct host and port for the computer running the CMN Domino Free/Busy connector service.
If you see the following error in your event log: NAMELookups are limited on this server to a size smaller than what would be returned. See your Domino Administrator for more information.
a
Open the Notes.ini file on your Domino server and add or modify the following entry: NAMELOOKUP_MAX_MB =<number>.

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:

The foreign domain is created in Domino, and the Calendar System property matches the CalendarDomain property set for the Person Documents representing the users in Exchange and the ForeignDomainName setting for the QCalCon server task.

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:

1
At the Domino Server Console, enter: Set conf debug_sched_all=1
Add Debug_sched_all=1 to your notes.ini file for the Domino server.
3
Look for messages in the Domino Server Log such as: <SchMsgQHandles_New> Opening queues for <FOREIGN DOMAIN>
4
Try setting the ForeignDomainName in QCalCon to the value of <FOREIGN DOMAIN> found on the server console output.

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

Get-CmnFreeBusyQCalCon [-WebServerName] <String> [-UserEmailAddress] <String>
WebServerName: Name of server where FreeBusyBridge Web Service resides.
UserEmailAddress: Email address for whom to get F/B info from Exchange.

To get the URL of the Exchange EWS:

Get-CmnExchangeWebServicesUrl [-EmailAddress] <String> [-Credentials <PSCredential>]
EmailAddress: Email address of an Exchange user.
Credentials: To access the Exchange Service. Use Get-Credential to get the credentials.
Related Documents