If the methods listed in the "Resolution" section do not resolve this issue, try one or more of the following steps:
- Reregister Msxml.dll and Msxml3.dll. To do this, type the following commands in a command prompt on your Exchange computer:
regsvr32 c:\winnt\system32\msxml.dll
regsvr32 c:\winnt\system32\msxml3.dll
- Use one of the following methods to re-create the Exchange-related virtual directories in Internet Services Manager, depending on your situation.
Exchange 2000
- Start Internet Services Manager, and then click the Computer icon under Internet Information Services.
- On the Action menu, click Backup/Restore Configuration.
- Click Create backup, type a name for your backup file, and then click OK.
Note By default, the backup file is saved to the %SystemRoot%\system32\inetsrv\MetaBack folder. If you want to save your backup file to another location, you can copy the file from this default location to another location. Keep a copy of the backup file in the default location to permit easy restoration. This backup method permits you to restore only your Microsoft Internet Information Services (IIS) settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000. - Click Close.
- Right-click Default Web Site, and then click Stop.
- Delete the following virtual directories:
- Exadmin
- Exchange
- Public
- Exchweb
- Open a command prompt on the Exchange computer, type cd c:\inetpub\adminscripts, and then press ENTER.
Note The Adsutil.vbs script uses CScript. If you register Cscript.exe as your default scripting host, you do not have to type Cscript.exe in front of the scripts to run them. If you do not want to register Cscript.exe, or if you have already registered CScript as your default scripting host, go to step k. - To register CScript as your default scripting host, type adsutil, and then press ENTER.
If CScript is not the default scripting host on this computer, you receive the following message: This script does not work with WScript.
If CScript is already the default scripting host, text that describes how to use the Adsutil.vbs tool appears. - Click OK.
- Click Yes to register CScript, click OK, and then click OK again.
- Type the following command:
adsutil delete ds2mb
- Restart the Microsoft Exchange System Attendant service. This re-creates the Exadmin, Exchange, and Public virtual directories in IIS.
- In Internet Services Manager, right-click Default Web Site, and then click Start.
Exchange 2003
Method 1: Reset the HighWaterMarks
- Download and install the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource Kit Tools, visit the following Microsoft Web site: If you do not want to install all the IIS 6.0 Resource Kit Tools, click the Custom installation option to install only Metabase Explorer 1.6.
- Start IIS Manager.
- Back up the metabase. To do this, right-click Default Web Site, click All Tasks, and then click Save Configuration to a File. Type a filename for the file and click OK.
- Expand Default Web Site, and then delete the following virtual directories:
- Microsoft-Server-ActiveSync
- OMA
- Exadmin
- Exchange
- Public
- ExchWeb
- Start Metabase Explorer. To do this, click Start, point to All Programs, point to IIS Resources, point to Metabase Explorer, and then click Metabase Explorer.
- Expand the LM key, right-click the DS2MB key, and then click Delete.
- Close Metabase Explorer.
- Restart the Microsoft Exchange System Attendant service to re-create the virtual directories in IIS.
Note If the virtual directories are not re-created after 15 minutes, restart the server. - In IIS Manager, expand Default Web Site, right-click Exchweb, and then click Properties.
- Click the Directory Security tab, and then click Edit under Authentication and access control.
- Verify that only the Enable anonymous access check box is selected.
- Right-click Default Web Site, and then click Stop.
- Right-click Default Web Site, and then click Start.
Method 2: Use ADSUtil to delete the DS2MB key
- Follow steps a through c of the "Method 1: Reset the HighWaterMarks" section to back up the metabase.
- Expand Default Web Site, and then delete the following virtual directories:
- Microsoft-Server-ActiveSync
- OMA
- Exadmin
- Exchange
- Public
- ExchWeb
- Open a command prompt, type c:\inetpub\adminscripts, and then press ENTER.
- Type adsutil, and then press ENTER.
If CScript is not the default scripting host on this computer, you receive the following message: This script does not work with WScript.
Click OK, click Yes to register CScript, click OK, and then click OK again.
Note If CScript is already the default scripting host, text that describes how to use the Adsutil.vbs tool appears. - Type adsutil delete ds2mb, and then press ENTER.
- Restart the Microsoft Exchange System Attendant service to re-create the virtual directories in IIS.
Note If the virtual directories are not re-created after 15 minutes, restart the server. - In IIS Manager, expand Default Web Site, right-click Exchweb, and then click Properties.
- Click the Directory Security tab, and then click Edit under Authentication and access control.
- Verify that only the Enable anonymous access check box is selected.
- Right-click Default Web Site, and then click Stop.
- Right-click Default Web Site, and then click Start.
For more information if the "Loading" also includes the "Unable to display folder. An internal server error occurred" error message, click the following article number to view the article in the Microsoft Knowledge Base:
267911
Error message "Internal server error" occurs when using OWA
For more information about the IIS Virtual Directories, click the following article number to view the article in the Microsoft Knowledge Base:
262181
Virtual Internet Information Server directories used by Outlook Web Access
The following products have been known to cause this issue:
- Microsoft Proxy Server 2.0
- Symantec Raptor 6.5
- Netscape Proxy Server
- Network Associates Gauntlet
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.