XGEN: Error Message "HTTP/1.1 503 Service Unavailable" on Multiple Web Sites on Single Server

Article translations Article translations
Article ID: 282230 - View products that this article applies to.
This article was previously published under Q282230
Expand all | Collapse all

SYMPTOMS

When a Hypertext Transfer Protocol (HTTP) virtual server that is running Exchange 2000 Server hosts both Exchange content and file system content from the same virtual server (for example, both http://server/exchange/blah for mailboxes and http://server/myapp/ for a program running out of the file system), requests to file system content do not work and the following error message is generated:
HTTP/1.1 503 Service Unavailable.

CAUSE

This issue can occur because when you use the Microsoft Internet Information Service (IIS) administrator to create the new virtual directory, the Davex.dll script map value is copied from the Exchange 2000-created virtual server to the new virtual directory. With this configuration, Davex.dll is processing requests to the virtual directory, even though the v-root points to the file system. Therefore, the requests do not work.

A sample configuration is as follows:
  • Additional virtual server under administrative groups\Servers\server_name\Protocols\HTTP\Exchange virtual server on Exchange 2000 Exchange System Manager.
  • The virtual server Web site on IIS holds mailboxes, public folders, and Web contents in the virtual directory.
  • It is possible to browse mailbox and public folders by using Microsoft Outlook Web Access (OWA). However, Web content from the virtual directory of the Exchange 2000 Web site is not visible.

RESOLUTION

To resolve this issue, remove Davex.dll from the virtual directory so that IIS processes the request.

When a new virtual directory is created, the Davex.dll script map value is copied from Exchange 2000 Exchange System Manager to the IIS. The requests to the virtual directory do not work because IIS processes the requests by Davex.dll.

To remove Davex.dll:
  1. Go to the Web site on IIS.
  2. Click to expand the folder (Web site).
  3. Right-click the virtual directory of the Web site.
  4. On the shortcut menu, click Properties.
  5. Click the Virtual Directory tab.
  6. Click Configuration.
  7. Click the Apps Mappings tab.
  8. Click the application mappings that looks like the following:
    *      C:\Program Files\Exchsrvr\bin\davex.dll      (All)
    					
  9. Click Remove.
  10. When you are prompted to Remove selected script mapping, click Yes.
  11. Click OK.
  12. Click OK.
This will remove the script value for the Davex.dll file. Browse through the Web contents by right-clicking on the virtual directory, and then clicking Browse. You should be able to browse through the Web contents.

MORE INFORMATION

During the installation of IIS, default values are assigned to the various properties on the property sheets. You can use the default settings in IIS, or you can customize these settings to suit your Web publishing needs. You may be able to provide additional value, better performance, and improved security by making adjustments to the default settings.

Properties can be set on the site level, directory level, or on the file level. Settings on higher levels (such as the site level) are automatically used, or inherited, by the lower levels (such as the directory level), but can still be edited individually at the lower level as well. After a property has been changed on an individual site, directory, or file, later changes to the master defaults do not automatically override the individual setting. Instead, you receive a warning message that asks whether you want to change the individual site, directory, or file setting to match the new defaults.

Properties

Article ID: 282230 - Last Review: February 20, 2007 - Revision: 1.3
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kberrmsg kbprb KB282230

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com