Connector for Microsoft Exchange - Troubleshooting

1. MediaGateway configuration

1.1 No access to Intrexx MediaGateway

If errors occur when testing the connection to the Administrator account, please check the following points. To successfully log in, the following login information needs to be entered correctly:

1.2 No access to Exchange account

If errors occur when testing the connection to the Exchange account, please check the following points.

1.2.1. Exchange 2003/2007

1.2.2. Exchange 2010 / 2016

2. Kerberos - Exchange 2010 / 2016

2.1 Modify EWSFindCountLimit

For security reasons, there is a limit on the maximum number of objects that can be taken into account during a request from Exchange Server 2010. If a request exceeds this limit, then no results will be returned. The maximum amount is determiend in the property EWSFindCountLimit of the ThrottlingPolicy. From Exchange 2010 SP1, EWSFindCountLimit in the DefaultThrottlingPolicy is set to 1000 by default. If, for example, the folder Inbox contains 5000 messages and EWSFindCountLimit is limited to 1000, a request to this folder will not return any results. Only when the limit is set to at least 5000 can objects in the Inbox be requested. The value for EWSFindCountLimit can either be defined globally or for individual mailboxes. With the following commands, which need to be performed in the Exchange Management Shell, the limit can be modified.

2.2. Calendar

Recurring appointments

You can only access recurring appointments if a date and time period is specified during the request to the Appointment table. To do that, you need to filter by the fields StartDate and EndDate.

Sorting appointments

If the Appointment table is sorted by start and end date, the appointments from the Exchange 2010 / 2016 Server are always returned in ascending order from the start data. Custom sortings in the applications or in the browser are not supported in this case.

3. Kerberos - Exchange 2003 / 2007

Kerberos identifies the login information based on the current Windows user and logs in to the Exchange mailbox automatically. When using the Kerberos authentication, you have a real Single-Sign On (SSO) for your users' access to the Exchange Server and use the integrated Windows authentication. When accessing an Exchange application via Kerberos for the first time, the user will be requested to specify, or rather confirm, their mailbox; this is only required once. All future accesses take place via SSO. If a user is asked to log in to the Exchange Server with username/password despite a defined Kerberos authentication, then this indicates problems during authentication. In this case, Intrexx automatically activates the session-based login and shows the entire login form with username and password. If you have problems with the authentication, please check the following basic requirements for successful Kerberos authentication.

3.1. Configuration in Intrexx

3.2. Configuration of the infrastructure

3.3. Browser settings

3.4 Test Kerberos authentication

If all of the measures described here are checked, the correct functionality of the Kerberos authentication can be checked as follows: Copy the directory support from bin/windows in the installation directory to external/htmlroot in the portal directory. Load the page http://<intrexx-server-hostname>/<portal_name>/support/krbdebug.asp in the browser. In the following, you can see different results that may occur when making the request.

Situation

Integrated Windows log-on not activated in the IIS:

Situation

Integrated Windows log-on activated in the IIS, but Kerberos Ticket is not available:

Situation

Integrated Windows log-on activated in the IIS and Kerberos Ticket is available:

4. IIS Server

If you implement an IIS for your Intrexx portal, the following configurations may be required for using the Intrexx MediaGateway.

4.1 File up- and downloads

To upload and/or download Exchange file attachments, e.g. in emails, the file size limits may need to be adjusted. To do that, open the Information Information Services (IIS) Manager and adjust the ASP limit properties:

4.2 Maximum query string

In the application Exchange – Resource, it may be necessary to extend the length of the query string when requesting multiple overlapping resources. You can recognize this when the error Http Error 404: Not Found is shown in the browser when trying to edit overlapping resources. In this case, proceed as follows: