Known issues that cause the �HTTP 500 internal server error� error message in Exchange 2000 Outlook Web Access

• You try to view or to open a message or an item in your mailbox.
• You try to view free and busy availability.
• You try to access your mailbox or the public folders.
• You try to rename a public folder.
• You try to log off Outlook Web Access or to download the Unified Messaging controls.

This article discusses known issues that cause the following error message in Microsoft Exchange 2000 Server Outlook Web Access:This article describes the majority of known issues that cause this error and the actions that you can take to resolve the issues.

You try to view or to open a message or an item in your mailbox

• You may receive the HTTP 500 error message when you open a new message or a new item in your mailbox, and the domain controller is turned off.
  
  Quit the Web browser, and then reconnect to Outlook Web Access after the domain controller is restarted.
• You may receive this error message when you use Microsoft Internet Explorer 4 or earlier to view a message that has an embedded appointment or meeting.
  
  To resolve this issue, use Outlook Web Access with Internet Explorer 5 or later.

You try to view free and busy availability

You may receive the HTTP 500 error message if the following conditions are true:

• You log on to Outlook Web Access through a front-end server by using Microsoft Internet Explorer 4 or earlier.
• You are viewing free and busy availability.

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

You try to access your mailbox or the public folders

• You may receive the HTTP 500 error message when you are browsing through the public folder tree in Outlook Web Access. Also, when you view a page that contains frames, one or more frames may display correctly, but the remainder of the panes may not.
  
  This problem occurs because the time on the client computer is more than five minutes out of synchronization with the server. Because the times are not synchronized, Kerberos authentication does not work between the Web browser and the server that hosts the public folder tree. To resolve this problem, synchronize the time on the client computer with the time on the server computer.
• You may receive the HTTP 500 error message when you use Outlook Web Access to access a public folder. This problem occurs when the public folder is on a server where the public folder hierarchy has been replicated to that server, but the contents have not been replicated.
  
  To resolve this problem, replicate the full contents of the public folder.
• You may receive the HTTP 500 error message when you use Outlook Web Access to try to access your mailbox or the public folders. Alternatively, if you cleared the Show friendly HTTP error messages check box in the Internet Explorer advanced settings, you may receive one of the following error messages:
  2147467259 (0x80004005)
  -2146893052 (0x80090304)
  Note To access the advanced settings for Internet Explorer, click Internet Options on the Tools menu, and then click the Advanced tab.
  
  If security auditing is enabled, you may also receive the following event message in the Security log:

  Event ID: 681
  Source: Account Logon
  Error: 3221225584

  This problem may occur if the following conditions are true:
  • Integrated Windows Authentication is enabled on the Exchange virtual directory.
  • The computers that the account can log on to are restricted.
  • The times of day that the account can log on are restricted.
  Integrated Windows Authentication passes information about the machine account that the browser is connecting from. The information is checked against logon restrictions. If the account is restricted, the account is denied access to the resource.
  
  To determine if account restriction is causing this problem, follow these steps:
  1. Start the Active Directory Users and Computers snap-in, and then open the properties of the account.
  2. Click the Account tab.
  3. Click Logon Hours to view the hours when a user can log on to the account. Or, click Log On To to view the computers that the account can log on to.
  To resolve this problem, disable Integrated Windows Authentication. Use Basic authentication only on the Exchange virtual directory and on the other virtual directories that you want to access. When you use Basic authentication, the remote computer account information is not passed to the server. The Internet Information Services (IIS) is used for proxy authentication. Because Outlook Web Access is listed as the only computer for which the user has access, the user is logged on successfully.
• Important Because Basic authentication passes credentials in clear text, it is best to implement Secure Sockets Layer (SSL) when you use Basic authentication. You should enable SSL on the Exchange server. Additionally, you should require SSL on the virtual directory or on any other directory that you want to access.
  
  For more information about how to resolve this problem when you cannot do so by using Basic authentication, click the following article number to view the article in the Microsoft Knowledge Base:
  316349 "HTTP 500 - Internal Server Error" error message when you use Outlook Web Access to access a front-end server
  You can also manually add the NetBIOS names of all the computers from which the user can log on. You can do this by using the Log On To option on the Account tab of the user account. For this method to work, you must also add the NetBIOS names of the computers that are not part of the domain.
• You may receive the following error message instead of the HTTP 500 error message when you try to access your mailbox or the public folders by using Outlook Web Access:
  The remote procedure call failed.
  The handle is invalid.
  You receive this error message after you clear the Show friendly HTTP error messages check box in the Internet Explorer advanced settings.
  Additionally, the following entries appear in the application log:

  Event Type: Error
  Event Source: MSExchangeDSAccess
  Event Category: General
  Event ID: 2050
  Date: Date
  Time: Time
  User: N/A
  Computer: Server name
  Description: Process DLLHOST.EXE /PROCESSID:{3D14228D-FBE1-11D0-995D-00C04FD919C1} (PID=3124). The shared memory heap could not be created.

  Event Type: Information
  Event Source: DAVEX
  Event Category: None
  Event ID: 101
  Date: Date
  Time: Time
  User: N/A
  Computer: Server name
  Description: DAVEX to be shutdown. Version: 6.0.6249.0

  
  
  The following entry appears in the system log:

  Event Type: Warning
  Event Source: W3SVC
  Event Category: None
  Event ID: 37
  Date: Date
  Time: Time
  User: N/A
  Computer: Server name
  Description: Out of process application '/LM/W3SVC/1/ROOT' terminated unexpectedly. For additional information specific to this message please visit the Microsoft Online Support site located at: http://search.support.microsoft.com/search/?adv=1.

  
  
  This problem occurs when Davex.dll and Exprox.dll are not running in the Inetinfo process. During Exchange startup, Davex.dll and Exprox.dll are added to the InProcessIsapiApps key in the metabase. This entry is a global entry that makes Davex.dll and Exprox.dll run in process with the Inetinfo process. If Davex.dll and Exprox.dll are missing from this key, Outlook Web Access only functions when the Exchange virtual directory and the Public virtual directory are also run in process.
  
  To resolve this problem, follow these steps:
  1. Download and install the MetaEdit 2.2 tool.
     
     For more information about how to obtain and how to use the MetaEdit 2.2 tool, click the following article number to view the article in the Microsoft Knowledge Base:
     301386 How to install MetaEdit 2.2 on Windows NT 4.0 or Windows 2000
  2. Start Internet Services Manager.
  3. Right-click the server object, and then click Backup/Restore Configuration.
  4. Start MetaEdit 2.2.
  5. Expand LM.
  6. Select W3SVC.
  7. In the right pane, click the Name column to sort by name.
  8. In the right pane, double-click InProcessIsapiApps.
  9. Click Add.
  10. In the Data field, type the path of Davex.dll. The default path is C:\Program Files\Exchsrvr\Bin\Davex.dll.
  11. In the right pane, double-click InProcessIsapiApps.
  12. Click Add.
  13. In the Data field, type the path of Exprox.dll. The default path is C:\Program Files\Exchsrvr\Bin\Exprox.dll.
  14. In Internet Services Manager, right-click the default Web site, and then click Stop.
  15. Right-click the default Web site, and then click Start.

You try to rename a public folder

You may receive the HTTP 500 error message when you rename a public folder by using Netscape Navigator or by using Internet Explorer 4 or earlier. You receive this error message when you double-click Rename or when you press ENTER two times while the Rename Folder dialog box is open.

To work around this problem, use Microsoft Internet Explorer 5.0 or later.

You try to log off Outlook Web Access or to download the Unified Messaging controls

You may receive the HTTP 500 error message when you click Log Off in Outlook Web Access. You may also receive the error message when you try to download the Unified Messaging controls in Outlook Web Access.

This problem may occur if the settings are incorrect on the Exchweb\Bin virtual directory. To resolve this problem, follow these steps:

1. Start Internet Services Manager.
2. Locate the Exchweb\Bin virtual directory.
3. Right-click the Bin virtual directory, and then click Properties.
4. On the Virtual Directory tab, click Create, and then click OK.

This information is included in the release notes for Microsoft Exchange 2000 Server Service Pack 2 (SP2). The release notes are on the Exchange 2000 SP2 CD.