Microsoft Exchange for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
Troubleshooting Exchange calendar integrations
Download this chapter
Troubleshooting Exchange calendar integrationsTroubleshooting Exchange calendar integrations
Download the complete book
Microsoft Exchange for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)Microsoft Exchange for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1) (PDF - 1 MB)
 Feedback

Troubleshooting Exchange calendar integrations

Troubleshooting Exchange server connection status

Exchange Server connection status displays in Cisco Unified CM IM and Presence Administration after you configure the Exchange Presence Gateway for either a WebDAV or EWS calendaring integration (select Presence > Gateways). The Troubleshooter on the Presence Gateway configuration window reports the status on the connection between IM and Presence and the Exchange server.


Note

You can add, update or delete one or more EWS servers with no maximum limit. However, the Troubleshooter on the Presence Gateway window is designed to only verify and report status of the first 10 EWS servers that you configure.

.

Test

Status Description and Recommended Action

Exchange Reachability (pingable)

IM and Presence successfully reached (pinged) the Exchange server.

Exchange Reachability (unreachable)

IM and Presence failed to ping the Exchange server. The server may not be reachable due to an incorrect field value or a possible issue with the customer's network, for example, cabling.

To resolve this, ensure that the Presence Gateway field contains the correct value (FQDN or IP address) to reach the Exchange server over the network. Note that the UI does not require the Presence Gateway field value to be the Subject CN value.

If you have connection problems with the Exchange server, also see the System Troubleshooter in Cisco Unified CM IM and Presence Administration and implement the recommended solution. Select Diagnostics > System Troubleshooter.

Troubleshooting SSL connection/certificate status

SSL Connection/Certificate Verification status displays in Cisco Unified CM IM and Presence Administration when you configure the Exchange Presence Gateway for a either a WebDAV or EWS calendaring integration (select Presence > Gateways). The Troubleshooter on the Presence Gateway configuration window will indicate if there is a certificate Subject CN mismatch or a SAN mismatch.


Note

You can add, update or delete one or more EWS servers with no maximum limit. However, the Troubleshooter on the Presence Gateway window is designed to only verify and report status of the first 10 EWS servers that you configure.

Test

Status Description and Recommended Action

SSL Connection/Certificate Verification - Verified

IM and Presence verified the SSL connection with the Exchange server. Select View for the certificate details.

SSL Connection/Certificate Verification Failed - Certificate Missing From Chain

Note   

These instructions describe the view of the customized Certificate Import Tool. If you are simply verifying connection status, the tool indicates the verified status but you do not have the option to Save.

One or more certificates that IM and Presence requires to establish a secure connection to the Exchange server are missing. The Certificate Viewer can provide details of the missing certificates.

Complete these steps in the Certificate Viewer to display any missing certificates:

  1. Select Configure to open the Certificate Viewer.
  2. Check Accept Certificate Chain.
  3. Select Save. The certificate chain details display. Note any certificates with a status of Missing.
  4. Close the Certificate Viewer.
  5. To complete the certificate chain, you must:
    • Download the missing certificates files from the Exchange server.
    • Copy or FTP the missing certificate files to the computer that you use to administer IM and Presence.
    • Use the Cisco Unified IM and Presence OS Administration to upload any of the required missing certificates.

Troubleshooting Tips

  • If the certificates are not available in the Certificate Viewer, you may need to manually download and install the missing certificates from the Exchange server, and upload these certificates in Cisco Unified IM and Presence OS Administration as follows:
    • If required, go to Cisco Unified IM and Presence OS Administration and upload certificates to complete the certificate chain.
    • Return to the Presence Gateway Configuration window in Cisco Unified CM IM and Presence Administration, reopen the Certificate Viewer, and verify in the Certificate Viewer that all certificates in the certificate chain now have a status of Verified.
  • You must restart the Cisco Presence Engine after you upload Exchange trust certificates. Select Cisco Unified IM and Presence Serviceability > Tools > Service Activation. Note that this can affect Calendaring connectivity.
  • Select either Configure or View to launch the Certificate Chain Viewer where you can view the details of the certificate chain. The Configure button will display if there are any issues with the certificate chain that IM and Presence downloads from the Exchange server - for example, the missing certificates scenario described above. Once you successfully import and verify the certificate chain, the SSL Connection / Certificate Verification status will update to Verified and the View button will replace Configure.

SSL Connection/Certificate Verification Failed- Subject CN Mismatch

The Presence Gateway field value must match the Subject CN value of the leaf certificate in the Certificate Chain. You can resolve this by entering the correct value in the Presence Gateway field.

Verify that your entry in the Presence Gateway field is correct as follows:

  1. Re-enter the correct Subject CN value in the Presence Gateway field. IM and Presence uses the Presence Gateway field value to ping the server. The host (FQDN or IP address) that you enter must exactly match the IIS certificate Subject Common Name.
  2. Select Save.

Troubleshooting Tips

Select either Configure or View to launch the Certificate Chain Viewer where you can view the details of the certificate chain. The Configure button will display if there are any issues with the certificate chain downloaded from the Exchange server - for example, the missing certificates scenario described above. Once you successfully import and verify the certificate chain, the SSL Connection / Certificate Verification status will update to Verified and the View button will replace Configure.

SSL Connection/Certificate Verification Failed - SAN Mismatch

The Presence Gateway field value must match one of the Subject Alternative Name (SAN) values of the leaf certificate in the Certificate Chain. You can resolve this by entering the correct value in the Presence Gateway field.

Verify that your entry in the Presence Gateway field is correct as follows:

  1. Re-enter the correct SAN value in the Presence Gateway field. IM and Presence uses the Presence Gateway field value to ping the server. The host (FQDN or IP address) that you enter must exactly match one of the entries in the certificate Subject Alternative Name.
  2. Select Save.

Troubleshooting Tips

Select either Configure or View to launch the Certificate Chain Viewer where you can view the details of the certificate chain. The Configure button will display if there are any issues with the certificate chain downloaded from the Exchange server - for example, the missing certificates scenario described above. Once you successfully import and verify the certificate chain, the SSL Connection / Certificate Verification status will update to Verified and the View button will replace Configure.

SSL Connection/Certificate Verification Failed - Bad Certificates

Information in the certificate is incorrect, which renders it invalid.

Typically, this occurs if the certificate matches the required Subject CN but not the public key. This could happen if the Exchange server regenerates the certificate but the IM and Presence server still maintains the old certificate.

To resolve this, complete these actions:

  • Select the logs to determine the cause of the error.
  • If the error is due to a bad signature, you need to remove the outdated certificate from IM and Presence in Cisco Unified IM and Presence OS Administration, and then upload a new certificate in Cisco Unified IM and Presence OS Administration.
  • If the error is due to an unsupported algorithm, you need to upload a new certificate that contains the supported algorithm in Cisco Unified IM and Presence OS Administration.

SSL Connection / Certificate Verification Failed - Network Error

Due to network issues, for example, a no-response timeout, IM and Presence cannot verify the SSL connection.

We recommend that you verify the network connectivity to the Exchange server, and ensure that the Exchange server is accepting connections using the correct IP address and port number.

SSL Connection/Certificate Verification Failed

Verification failed for a non-specific reason or because IM and Presence cannot perform the reachability test.

We recommend that you review the debug log files for more information.

Issues known to impact Microsoft Exchange integrations

Scale limitations for calendar integrations

IM and Presence and Exchange calendaring integrations have been validated with up to X% of the users subscribing to calendar presence and with up to Y% of the users doing simultaneous calendar transitions (for example, joining or leaving meetings simultaneously). See Table 1 for percentage values pertaining to specific releases of IM and Presence Release.

Table 1 Scale Limitations for Specific IM and Presence Releases

Software Release

% of Users Subscribing to Calendar Presence

% of Users Performing Sumultaneous Calendar Transitions

8.5(1)

50

30

8.5(2) and later

100

50

Note

Calendaring values for MCS-7825 platforms should not exceed the values specified for release 8.5(1).

Calendar state does not update if a user moves between Exchange servers

Problem

If an Exchange administrator moves a user from one Exchange server to another in an Exchange integration, the calendaring state change will not update for that user.

Cause

The condition occurs because the Exchange server does not signal when a user is moved from one server to another.

Solution

The IM and Presence administrator or user must disable and then reenable calendar integration for that user after the Exchange administrator has moved the user from one Exchange server to another.

LDAP user removal takes at least 24 hours to replicate on IM and Presence

Problem

If a user is deleted from LDAP, the user state changes to Inactive on Cisco Unified Communications Manager and user authentication on client applications will subsequently fail. However, it has been observed during testing that once Cisco Unified Communications Manager synchronizes the change from LDAP, the user will not be removed for 24 hours after the synchronization occured (either by the Administrator forcing the sync or scheduling it to occur at a specific time).

The Cisco Sync Agent on IM and Presence will not synchronize any user state change until the user is removed. In the interim period, that user still exists on Cisco Unified Communications Manager and all IM and Presence capabilities (including Exchange calendaring subscriptions) remain licensed for that user for 24 hours. This delay means that users who were signed into Cisco Jabber before the user was removed from LDAP are not signed out automatically. The user’s pre-exisitng calendar state (Available, Busy) will persist for that user on IM and Presence until the user signs out of the client.

Cause

The condition occurs when Cisco Unified Communications Manager is set up and LDAP authentication is used. When a user is deleted from LDAP, calendaring subscriptions continue to be established and updated for that user on IM and Presence for a period of at least 24 hours.

Solution

If a user is removed from LDAP, you can manually remove the license for that user so that IM and Presence ends the Exchange calendaring subscriptions with immediate effect and signs the user out of the client application. Otherwise, be aware that there may be a 24 hour time delay.

Localization caveat with WebDAV calendar integrations

Problem

If you set the default language (English) on the user's Exchange Mailbox when a different language/locale is installed on Cisco Unified Communications Manager, the Exchange server maintains the default calendar name (in English) and you cannot change the language/locale for that user. A 404 error returns for calendaring subscriptions.

Cause

This condition only occurs in localized Exchange 2003/2007 integrations over WebDAV. The issue does not affect EWS integrations.

Solution

  • To prevent this issue occurring, we recommend that you set languages correctly during the Exchange setup. Install the appropriate language/locale on Cisco Unified Communications Manager and select the appropriate language/locale on the Exchange server the first time the user signs in.
  • If the language on the user's Exchange Mailbox is set to English when a different language/locale is installed on Cisco Unified Communications Manager, you must switch the language/locale on Cisco Unified Communications Manager back to English for that user. To do this, see Set user locales for multilingual calendar integration.

Verify that Exchange server URL contains localized word for “Calendar”

If you are localizing your Calendaring integration, verify that the Exchange server URL contains the localized word for "Calendar".

Procedure
    Step 1   Install the same language locales (load the locale installer) on both IM and Presence and the Cisco Unified Communications Manager. For more information about installing locales on IM and Presence, see [Optional] Configuration of multilingual support for calendar integration.
    Step 2   Restart the IM and Presence server, and sign into Cisco Unified CM IM and Presence Administration.
    Step 3   Find and delete the existing Exchange Presence Gateway that supports a different locale for calendaring (select Presence > Gateways).
    Step 4   Add a new Exchange Presence (Outlook) gateway. Select Add New.
    Step 5   Verify in the database (pebackendgateway table) that the 'localecalendarname' attribute is in whichever language locale you have installed.
    Step 6   Ensure the user locale is set after the locale is installed on both the IM and Presence and Cisco Unified Communications Manager, toggling the user locale on the Cisco Unified Communications Manager, if necessary.

    Apply Microsoft HotFix KB841561

    Note that this issue is specific to Microsoft Exchange 2003 only. Apply Microsoft HotFix KB841561 if you encounter problems with the Exchange 2003 server and it returns a "500 Internal Server Error”.

    Procedure
      Step 1   Uninstall SP2 for Windows Server 2003 and for Microsoft Exchange 2003.
      Step 2   Install SP1 for Windows Server 2003 and Exchange 2003.
      Step 3   Download and install KB841561 from the following URL: http://www.microsoft.com/downloads/details.aspx?familyid=050be883-11fc-4045-b988-c737e79c65d0&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=050be883-11fc-4045-b988-c737e79c65d0&displaylang=en
      Step 4   Install SP2 for Windows Server 2003 and for Microsoft Exchange 2003.

      Fix “HTTP 503 Service Unavailable” error from Exchange 2007

      Note that this issue is specific to Microsoft Exchange 2007 only.

      Problem

      Since Exchange 2007, Microsoft changed the Outlook Web Access URL from /exchange to /owa, which is the virtual directory that OWA uses to access mailboxes on Exchange 2007 mailbox servers. IM and Presence, however, always sends SUSCRIBE requests to the /exchange virtual directory, which is the URL that is still used for WebDAV integration with Exchange 2007. During testing with Exchange Server 2007 (SP1), it has been observed that if you change the http://<server>/exchange URL to redirect to http://<server>/owa URL, an error (HTTP 503 Service Unavailable) displays on the Internet Information Services (IIS) Manager console in Exchange 2007.

      Cause

      The condition occurs when Exchange 2007 SP1 is in use, and the Exchange virtual directory target address is modified to redirect to the default OWA directory for webmail.

      Solution

      If the “503 Service Unavailable" error message displays, perform the steps in this procedure:

      Procedure
        Step 1   From Administrative Tools, open Internet Information Services.
        Step 2   Delete the Microsoft Exchange virtual directory in IIS.
        Step 3   Review the warning that displays, and run the recommended cmdlet in the Exchange Management Shell (EMS) :
        Step 4   Run this cmdlet in the EMS to ensure that the Exchange virtual directory is set up correctly and to add the directory again in IIS. 
        SyntaxNew-OwaVirtualDirectory -name exchange -OWAVersion Exchange2003or2000 -VirtualDirectoryType mailboxes
        Step 5   Wait for the Exchange server to populate the virtual directory into IIS.
        Step 6   Restart the IIS.
        Step 7   Test your http://<server>/exchange/<user email address>/calendar URL, using the full target address for example, http://mail.contoso.com/exchange/user@contoso.com/calendar
        Step 8   Ensure that you are prompted for a username and password. This indicates that WebDAV is enabled and configured correctly on the virtual directory. Enter your Active Directory credentials.
        Step 9   Check the IIS logs that display for IM and Presence.
        Step 10   If the logs indicate that there is a 401 authentication issue, add the domain to authenticate access.
        Step 11   Restart the IIS.
        Step 12   Select Cisco Unified IM and Presence Serviceability > Tools > Service Activation and restart the Cisco Presence Engine.
        Step 13   Check the IIS logs again and verify that the SUBSCRIBE messages are present and correct for your calendar.

        Troubleshooting Tips

        This procedure also applies to Apple MAC users who require WebDAV to view their emails using Microsoft Entourage 2008.

        Support for meeting notifications

        Note that the Meeting Notification feature will only work if your network integration is over WebDAV. Therefore, this issue is specific to Microsoft Exchange 2003 or 2007 only. These features are not supported with EWS integrations.