Re: OWA problem for one user   

I've gotten creative, and just decided to remove the entire mailbox an
all it's settings. Made a PST file backup, then removed the Exchange
mailbox from the ADUC. Ran the cleanup agent in Exchange, purged the
mailbox to completely remove it, and then waited 15 minutes. Recreated
the mailbox, configured it, then let it sync during 15 minutes. Went
to the users PC, started up Outllook 2002 and set things straight,
reimported the mail, and found that the mailbox got filled properly.
So the user has a recreated mailbox now, with his own data contained
therein.

Unfortunatly for OWA this does not change anything. User is still
unable to login. As a test, I removed the access rights to OWA on both
his account and mine. Waited 15 minutes for that change to sync
through, then tried it. On the working account the error 403 appears,
showing me that the page was not able to display. For the problem user
this changes nothing. So the error occurs before the actual
verification of the Exchange Features configured for the user.

About the only thing I can imagine I could try now that excludes
anything that affects multiple users (that being re-applying the
Service Pack for Exchange to the FrontEnd), is to remove the entire
user account, purge all profile settings, purge the mailbox, and
essentially wipe the slate clean, then re-create the user. This would
however entail quite a bit of work to get the whole profile filled
again, during which time the user has no means of being productive.
Not something I'd look forward to doing actually.

The suggestion on using the backend-server for OWA access kinda
slipped past my sight up to now. Fact is, the backend-server doesn't
actually run the OWA properly. I've provided it to be the same as for
the FrontEnd server, but for some reason it dumps me to a white
screen, depicting inbox and the like on the left, the textbar with the
'New email' at the top, commenting that it's loading the file list.
There are no graphics on the screen, and the pictures are reffered to
as being 'unavailable' (with the nice red X in 'm).

If anyone else has further suggestions on what we could try, I look
forward to hearing them.

date: Fri, 4 Jul 2008 03:20:59 -0700 (PDT)   author:   Neko-