In our test lab, we installed Microsoft SharePoint Services beta 2 on a Microsoft Exchange Server 2003 front-end server. As soon as the installation was finished, we noticed that Microsoft Outlook Web Access (OWA) on the front-end server no longer worked. Is this a known conflict?

SharePoint Services will try to use its built-in rendering mechanism to render URLs requested on servers on which it's installed. This action is poison for OWA, which wants to render its own content. The remedy is straightforward: Use the SharePoint Services exclusions list to tell SharePoint Services not to attempt to render the /exchange, /public, or /exchadmin virtual directories.

—Paul Robichaux

End of Article


You must log on before posting a comment.

If you don't have a username & password, please register now.

Reader Comments

This article was very helpful - I have struggled getting SharePoint and Exchange to work on the same box. However, you do need to include one more path in the exclusion - it's the "/Exchweb" directory. If that is not excluded, there will be errors trying to load the pages for OWA.

Ryan Malecki- November 15, 2003

Hello:

I had the same problem, after installing SharePoint Services, i was not able to access Exchange Server. I tried the steps given in the Microsoft KB and also the steps in this article, it still didn't work.

Is there any thing i can do so that Exchange starts working properly?

Thanks,

Krish Irajaram- February 29, 2004

You also have to exclude the /Exchweb and /OMA folders as well.

Hammond- March 17, 2004

the information is free on http://support.microsoft.com/?kbid=823265

Anonymous User- January 18, 2005

Thanks Hammoond, you just saved me 10gallons of sweat!

Anonymous User- April 12, 2005

Article Rating 5 out of 5