# Installation and Upgrade Guide

# Troubleshooting Exchange Portlets

This section provides solutions for problems you might encounter when you install, register, and set up your portlet suite.

Question: A portlet user is unable to make a connection to the backend Outlook Web Access (OWA) server. How can the user gain access?

Solution: The user must have an account on the OWA server before accessing it through the portlet.

Question: In the 5.0.x portal, the gateway prefix configured by the portlet package is wrong. How can I fix it?

Solution: To modify the Gateway URL Prefixes settings:

1. To display the Admin Objects page, log in to the portal as an administrator and click Administration.
2. To display a list of Exchange Portlet Suite objects, browse through the folders to open the folder that was created for the suite when you migrated the portlet suite package into the portal.
3. To display a list of Remote Server objects, click Web Service.
4. To display the Web Service editor for the calendar portlet, click its name, for example MS Exchange Calendar Web Service.
5. To display the Gateway URL Prefixes settings, in the menu column, click HTTP Configuration.
6. In the HTTP Configuration page, replace the comma (,) with the following string in the Prefix test box: calendar/

Note: | Perform this procedure for both individual and community calendar Web services

Question: After running the Installation Wizard and test page, the test returns a notConnected error. How can I troubleshoot this?

Solution: Run a network trace tool to test the communication from the Remote Server to the Exchange server. If Exchange Server replies with a 404, the Exchange Server has disabled WebDAV verbs.

The Remote Server uses the following Microsoft extensions to WebDAV standard verbs to communicate with external servers:

- "PROPFIND"
- "BPROPFIND"
- "SEARCH"
- "X-MS-ENUMATTS"
- "COPY"
- "MOVE"
- "DELETE"
- "MKCOL"
- "GET"
- "PROPPATCH"
- "GALFIND"

Troubleshoot the Exchange Server instance to see what is responsible for turning off WebDAV verbs. You might have to enable verbs using one of the following options:

- If the IIS Lockdown tool or the URLScan utility has turned off verbs, re-run these programs with parameters that allow requests from the Remote Server.
- Edit the registry settings for WebDAV to enable verbs.
- Set the %systemroot%\system32\inetsrv\httpext.dll library so that it is not readable; this turns off the gating settings.