Article ID: 282230 - View products that this article applies to.
This article was previously published under Q282230
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.
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:
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:
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.
Article ID: 282230 - Last Review: February 20, 2007 - Revision: 1.3