Trouble with OWA on upgrade to Exchange 2003

Yesterday I had Exchange 2000 running fine (including
OWA) on Win2K server. I then installed Exchange 2000 on
another Windows 2000 server, moved all the mailboxes from
the previous server to the new server, upgraded the new
email server to Exchange 2003, and finally upgraded the
OS on the new server to Win2003. From there I upgraded
the old Exchange 2000 server to an Exchange 2003 server
and made it a Front-End server.

Now Outlook still works fine. In fact all the old email
clients that were still pointed to the original server
transparently get redirected to the new email server.

The problem is, I can't get OWA to work on either server
now. If I browse to the original Exchange server where
OWA was working fine, I'm prompted for my username and
password - but even after entering them I get prompted
over and over until I've run out of retries and then I
get an "Access denied" screen.

On the new server, OWA actually appears, but without the
fancy formatting and without any data. The shell with
the "Inbox," "Contacts," and "Calendar" menu appears in
the frame on the left and the "Loading..." message
appears below the top menu in the frame on the right, but
that's it. The formatting looks like the server can't
find a CSS file. Clicking on the Inbox or anything else
just gives a javascript error. None of my emails,
contacts, or anything else ever appears.

Any help is greatly appreciated.

Mike

Mike
Fri Jan 02 08:17:46 CST 2004

I am now able to log in to the front-end server and see
all the folders in my mailbox. However, I can't see any
of the actual mail messages. The server will even show
the number of new messages. I just can't see actual data
like contacts, tasks, or emails.

Mike

m
Mon Jan 05 11:56:18 CST 2004

Called Microsoft Tech Support. The following helped resolve the issue:

1) Deleted Exchange and Public virtual folders on both backend and frontend.
2) Ran MetaEdit22.exe on both machines and deleted key 61472 under both domain controller folders under LM\DS2MB\HighWaterMarks.
3) Restarted the Microsoft Exchange System Attendant service and all dependent services on both servers. This will recreate the Exchange and Public virtual folders and reset them to default values.
4) In IIS on backend server, enabled Webdav (under Web Server Extensions) that was disabled while running IIS Lockdown Wizard.
5) On backend server, changed the system32\inetsrv\urlscan\urlscan.ini file to reflect the configuration shown under the OWA section of MS Knowledge Base Article 309508. Restarted WWW Publishing Service.