"HTTP 403 (Forbidden)" error message when Exchange 2003 users try to use Outlook Web Access to access a freedoc that is located in a public folder (834743)
The information in this article applies to:
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSWhen a Microsoft Exchange Server 2003 user tries to use Microsoft Outlook Web Access (OWA) to access a freedoc that is located in a public folder, the user may receive the following error message: HTTP 403 (Forbidden) You are not authorized to view this page. CAUSEThis behavior occurs because Exchange 2003 does not permit you to use OWA to directly access freedocs that are stored in public folders. By default, Exchange Server 2003 prevents direct access to freedocs that are stored in public folders. When you are permitted to open freedocs that are stored in public folders, you may receive unexpected results. Freedocs might contain executable script that runs on the user's computer.
When a user tries to access freedocs in public folders, the user receives the error message that is described in the "Symptoms" section. Although freedocs that are stored in public folders cannot be accessed, freedocs that are stored in mailbox folders can be accessed if the user has the proper permission to the freedoc.
Microsoft recommends that you use these folders when access to freedocs is required.
Alternatively, if you determine that freedoc access in an uncontrolled public folder is an acceptable risk, you can enable access to freedocs in public folders. You enable access to freedocs in public folders by modifying the registry of the Exchange Server 2003 back-end server where the public folders are located.RESOLUTIONWarning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To change the default behavior to permit an OWA user to access freedocs in public folders, follow these steps on both front-end and back-end servers: - Start Registry Editor.
To do this, click Start, click Run, type regedit in the Open box, and then click OK. - Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeWeb\OWA - On the Edit menu, point to New, click DWORD Value, and then type EnableFreedocs.
- Double-click EnableFreedocs, and then set the value to one of the following:
0 = Freedocs are inaccessible in OWA. This value is the default value. 1 = Freedocs are accessible in OWA, but only when the freedocs are accessed from the back-end server. 2 = Freedocs are accessible in OWA, but only when the freedocs are accessed from the back-end server or
the front-end server by using a host header that matches an entry in the AcceptedAttachmentFrontEnds registry value. 3 = Freedocs are accessible everywhere.
STATUS
This behavior is by design.MORE INFORMATIONA freedoc is any document in the Exchange mailbox store that has a message class that starts with IPM.Document. For example, a Microsoft Word document that has been saved directly in the mailbox or the public store is a freedoc. Such a document generally has a message class of IPM.Document.*doc.
Modification Type: | Minor | Last Reviewed: | 11/8/2005 |
---|
Keywords: | kbExchangeOWA kberrmsg kbprb KB834743 kbAudITPRO |
---|
|