XCCC: Public Folders Are Not Accessible in OWA If You Change the Default Port; Fix Requires Exchange 2000 SP1

This article was previously published under Q313905
This article has been archived. It is offered "as is" and will no longer be updated.
If you change the port on the default Web server for Internet Information Services (IIS), and then try to use Microsoft Outlook Web Access (OWA) to gain access to public folders or certain pieces of the Calendar, you may receive an error message that varies depending on the version of Microsoft Internet Explorer that you use. The error messages include the phrases "Error 16389" and "Access Denied 70." This problem only occurs if you use a fully qualified domain name (FQDN) to gain access to the server.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix should have the following file attributes or later:

Component: OWA

File nameVersion

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Article ID: 313905 - Last Review: 10/24/2013 08:52:21 - Revision: 1.7

Microsoft Exchange 2000 Server Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix KB313905