OWA not working after /disaster recovery on Exchange 2003 Ent

A little bit of history before the problem.   On Wednesday morning, our Exchange 2003 Ent server locked up causing one of the information stores to become corrupt.   We contacted Microsoft for assistance and we were able to restore functionality to the Exchange server, but because the server locked up again on us we decided to move to new hardware.  Microsoft was able to do the /disaster recovery option to move the Exchange data to the new hardware.   The Exchange site now resides on new hardware and we are up and running again.

The problem:  For some unknown reason, OWA is not working on the new server.   When I attempt to goto http://localhost/exchange, I receive a 404 - File or directory not found.   I need some assistance from the community to start troubleshooting this issue.  

When I look under the Exchsrvr directory, I do see the Exchweb and OMA folders.  In IIS, under the default website I do see the Exchange, exchange-oma, ExchWeb, Microsoft-Server-ActiveSync, OMA and Public sites.   It seems the perhaps the local path to BackOfficeStorage isn't getting resolved (I am guessing)?    I can open up a webpage to http://localhost/oma.   The difference being that the OMA website has an actual directory in the "local path" field instead of0 \\.\BackOfficeStorage\....

The server is Exchange Server 2003 Enterprise SP2.   It is not a domain controller.   All other functionality seems ok with the server such as emails, calendar, public folders.    There is only one Exchange server in the site and OWA is accessed from the outside world via ISA 2006.

I appreciate any help given.   Thanks in advance.  

Edit:  Its 1:22am here central time.   I'm going to bed now but I will check on this in the morning.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Maybe you can run this script, it recreates you'r IIS virtual dirs

cscript %windir%\system32\iisvdir.vbs /delete w3svc/1/root/Exadmin
cscript %windir%\system32\iisvdir.vbs /delete w3svc/1/root/Exchange
cscript %windir%\system32\iisvdir.vbs /delete w3svc/1/root/ExchWeb
cscript %windir%\system32\iisvdir.vbs /delete w3svc/1/root/Microsoft-Server-ActiveSync
cscript %windir%\system32\iisvdir.vbs /delete w3svc/1/root/OMA
cscript %windir%\system32\iisvdir.vbs /delete w3svc/1/root/Public
cscript %systemdrive%\inetpub\adminscripts\adsutil.vbs delete ds2mb
net stop "microsoft exchange information store"
net stop "microsoft exchange system attendant"
net start "microsoft exchange system attendant"
net start "microsoft exchange information store"

Open in new window

You may need to re run the Exchange install or especially all the service packs you had on the other server.

You can also recreate your HTTP virtual server from within the System Manager under protocols - HTTP.

Here's a good tutorial on fixing a broken OWA: http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html.

In my experience you get this kind of problem most frequently when you have incorrect versions of system files or when your IIS metabase doesn't contain the same information that your Exchange install thinks it should.
Does the Default Web Site have a Host Header name configured?  Using the server name 'localhost' in your URL may be preventing your request from reaching the Default Web Site.  Also, if you have FBA enabled, but also have the Web Service Extension for Active Server Pages not set to Allowed, this will produce a confusing 404 error.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WarehouseOneAuthor Commented:
vsalyan:  We tried fixing as per your instructions but made no difference.  Thanks for your suggestion.

LeeDerbyshire:  You were correct.   For some reason the localhost URL wasn't working properly.  Pulling up an IP address instead of localhost did work which pointed us in the correct direction for a solution.    To the default website, we added the local host IP address under the web site identification and everything worked afterwards.

Thanks to everyone for their suggestions.  Cheers!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.