You receive a "Page not found" error message when you use Outlook Web Access (OWA) to browse the Exchange Server 2003 client after you install Windows SharePoint Services
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to use Microsoft Outlook Web Access to browse the Microsoft Exchange Server 2003 client, you may receive the following error message:
Page not found
This problem may occur after you install Microsoft Windows SharePoint Services on a server that is running Microsoft Exchange Server. The Windows SharePoint Services ISAPI filter handles all incoming URLs. When you browse one of the Exchange Server 2003 virtual directories, the ISAPI filter does not locate the URL path of the folder.
To resolve this problem, and to have Windows SharePoint Services and Exchange Server 2003 both function correctly, you must enable Kerberos authentication and exclude the folders (directories) that Microsoft Exchange Server 2003 uses. To do so, follow these steps:
- Configure the virtual server that is running Windows SharePoint Services and Exchange Server 2003 programs to use Kerberos authentication.
When a virtual server is extended with Windows SharePoint Services, Kerberos authentication is disabled Integrated Windows authentication is enabled. For Exchange Server 2003 to work correctly, you must configure the virtual server to use Kerberos authentication. For more information about how to configure Windows SharePoint Services to Use Kerberos authentication, click the following article number to view the article in the Microsoft Knowledge Base:832769 How to configure a Windows SharePoint Services virtual server to use Kerberos authentication and how to switch from Kerberos authentication back to NTLM authentication
- Exclude the following folders (directories) that Microsoft Exchange Server 2003 uses:
- On the server that is running Exchange Server 2003 and Windows SharePoint Services, click Start, click Administrative Tools, and then click SharePoint Central Administration.
- In the Virtual Server Configuration area, click Configure virtual server settings.
- On the Virtual Server List tab, click the virtual server that you have to add the excluded paths to.
- Under Virtual Server Management, click Define Managed Paths.
- In the Add a New Path section, type the path to exclude in the Path box.
- Click Excluded Path, and then click OK.
- Repeat steps 4 through 6 for each folder that you want to exclude.
\Program Files\Exchsrvr\OMA\browse\web.configand add the following directives in the Web.config between <system.web></system.web>. Add these directives immediately after <system.web> to keep it as simple as possible:
After you add the directives to the Web.config, save the file.
<!-- Clear out the WSS ASP.Net handler and specify the default ASP.Net handler for all pages --> <httpHandlers> <clear /> <add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory" /> </httpHandlers> <!-- Set the trust back to Full. WSS configures a very restrictive trust policy that does not allow OMA to run correctly. --> <trust level="Full" originUrl="" /> <!-- Enable the session module. This can also be enabled on the WSS Web.config, but is not enabled by default. If you receive the following message: Parser Error Message: The module 'Session' is already in the application and cannot be added again You can remove the following <httpModules></httpModules> section as session is already enabled on the virtual server --> <httpModules> <add name="Session" type="System.Web.SessionState.SessionStateModule"/> </httpModules> <!-- Enable Session for the pages in the OMA application --> <pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" />
Article ID: 823265 - Last Review: 12/08/2015 03:20:23 - Revision: 5.3
Microsoft Windows SharePoint Services 2.0
- kbnosurvey kbarchive kbtshoot kberrmsg kbprb KB823265