Microsoft KB Archive/829167

= &quot;HTTP 500 - Internal Server Error&quot; Error Message When You Use Outlook Web Access to Connect to Your Microsoft Exchange Server 2003 Mailbox =

Article ID: 829167

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Standard Edition, when used with:
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-





SYMPTOMS
When you try to use Microsoft Outlook Web Access 2003 to connect to your Microsoft Exchange Server 2003 mailbox, you may receive the following error message:

HTTP 500 - Internal Server error.

Additionally, an event that is similar to the following event is logged in the application event log on your Exchange 2003 computer: Event Type: Error

Event Source: MSExchangeDSAccess

Event Category: General

Event ID: 2050

Date:

Time:

User: N/A

Computer:

Description: Process  (PID= ). The shared memory heap could not be created.



CAUSE
This issue may occur when the Exchange virtual directory is either not running in the correct application pool, or when the ExchangeApplicationPool property has the incorrect identity.



RESOLUTION
To resolve this issue, make sure that the Exadmin, the Exchange, the Exchweb, the Exchweb\Bin, the Exchweb\Bin\Auth, the Microsoft-Server-ActiveSync, and the Public virtual directories are running in the Exchange Application Pool and not in the Default Application Pool. To do this, follow these steps:  Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager. Expand  , and then expand Web Sites and Default Web Site. Right-click Exadmin, and then click Properties. In the Exadmin Properties box, on the Virtual Directory tab, make sure that the text in the Application pool list is ExchangeApplicationPool in the Application settings area. If the text is not ExchangeApplicationPool, follow these steps:  Click Create, and then click ExchangeApplicationPool in the Application pool list. Click Apply, and then click OK.</li></ol> </li> Repeat steps 3 through 4 for the Exchange, the Exchweb, the Exchweb\Bin, the Exchweb\Bin\Auth, the Microsoft-Server-ActiveSync, and the Public virtual directories.</li></ol>

If ExchangeApplicationPool is in each Application pool list, this issue may be caused by an incorrect Identity setting for the ExchangeApplicationPool property. To resolve this problem, follow these steps:
 * 1) In Internet Information Services (IIS) Manager, expand Application Pools.
 * 2) Right-click ExchangeApplicationPool, and then click Properties.
 * 3) Click the Identity tab, and then in the Select a security account for this application pool list, click Local System.
 * 4) Click Apply, and then click OK.

You may find that Microsoft Server ActiveSync and remote procedure call (RPC) over Hypertext Transfer Protocol (HTTP) by using Microsoft Office Outlook 2003 still do not function. This problem occurs because Microsoft Web Storage System (WSS) sets the value of the NTAuthenticationProviders property for the default Web site to NTLM. This NTLM value must be removed from the NTAuthenticationProviders property. To remove the NTLM value, follow these steps: <ol> At the command line, change to the \Inetpub\Adminscripts folder that contains the Adsutil.vbs file.</li> Run the following command to list the items for the default Web site:

cscript adsutil.vbs enum w3svc/1

The value for the NTAuthenticationProviders property is set to NTLM.</li> To remove NTLM as the value, run the following command:

cscript adsutil.vbs set w3svc/1/NTAuthenticationProviders &quot;&quot;

</li> To confirm that the value is empty, run the following command:

cscript adsutil.vbs enum w3svc/1

</li> Now test Server ActiveSync and Outlook 2003 by using RPC over HTTP.</li></ol>

Additional query words: XCCC

Keywords: kbprb KB829167

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.