Exchange 2003 SP2 with the following KB's 950159, 916783, 914148 plus others which are also on a server that is working. .Net 1, 2 and 3 are loaded. Virtual directories are using .Net 1 as normal. If I go to http:\\servername\exchange I am getting a 404 page not found error. IIS log has it as a 404 0 2 error which apparently is file not found. If I go to http:\\servername I get the usual under construction page I have tried doing the reset of the virtual directories with no result. NB Virtual directories have not been put directly under Default Website for some reason but are on another tier below. ASP, Webdav etc. are all enabled. OWA has never worked on this server, at least while I've been here, but hasn't been a requirement up to now. Any thoughts / hints? Thanks Neill

So, you have reset the default virtual directories with the method 1 on KB 883380? Do you have a working exchange server in the environment or a lab? Then you can cross check the settings and files between them Is there any error event in the application log after reproduce the issue? Resources: How system administrators can troubleshoot an "HTTP 404 - File not found" error message on a server that is running IIS How to remove and to reinstall IIS on a computer that is running Exchange ServerJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Thank James. Yes indeed I have used 883380. I do have another server in a different office built much the same way. I noted the hotfix differences above. I have gone through the BIN folders on each and have only noticed differences for the hotfixes above. I haven't had a chance to fully review the sub-folders yet but nothing looks untoward at first glance. Permissions are all the same, in NTFS and virtual directories. Nothing in event log and the virtual directories recreate without problems. Looked at first article. I can get to default web site no problem but going to http:\\server\exchange throws up the problem. What files is it actually trying to connect to, i.e. I see the top-level virtual directory for exchange is pointing to davex.dll but where does it go after that? 2nd article is a big step even with a cluster. I am trying to stop the requirement for the OWA on 2003 since we are moving to Exchange 2010 ASAP anyway. Only problem is that it is the CEO that is wanting it. Cheers Neill