Article ID: 841560 - Last Review: October 25, 2007 - Revision: 3.3 A user receives a "500 - Internal server error" error message when the user tries to access a clustered Exchange Server 2003 back-end server by using Outlook Web AccessOn This PageSYMPTOMSConsider the following scenario. You install Microsoft Windows Server 2003 Service Pack 1 (SP1) on a server cluster. The server cluster is running a clustered Microsoft Exchange Server 2003 back-end server. You experience the following symptoms:
CAUSEThis problem is caused by some of the security enhancements that are included with Windows Server 2003 SP1. In this scenario, when a user tries to access a mailbox by using Outlook Web Access, HTTP requests into the clustering API by impersonating the logged-on user. However, there have been security changes in Windows Server 2003 SP1. The security restrictions for the APIs that perform remote registry access have been changed. Therefore, the logon attempt is not successful. RESOLUTIONTo resolve this problem, we recommend that you direct customers to do the following things, in the order that they are presented:
Hotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesNo prerequisites are required.Restart requirementYou do not have to restart your computer after you install this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name -------------------------------------------------------- 03-Jun-2004 18:45 6.5.6980.91 1,069,056 Davex.dll 03-Jun-2004 18:49 6.5.6980.91 3,618,816 Excdo.dll 03-Jun-2004 18:45 6.5.6980.91 2,539,008 Exoledb.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information about terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
817903
(http://support.microsoft.com/kb/817903/
)
New naming schema for Exchange Server software update packages
| Article Translations
|
Back to the top
