That one (accessibility) was from me. It would dump you straight into OWA Light with no option for premium. Premium didn't give any errors though when it worked.
On the .net FW, I have 2.0 SP1 and 3.0 SP1 on our E2k7 SP1 server. Prior to 2.0SP1, I had both the x86 and x64 of 2.0, but after some digging, it looks like they combined them (if you have x64) in 2.0SP1. In other words, they are still both on there, whereas 3.0 is x64. Never had to go back and add 1.0 or 1.1 and I've not tried 3.5 yet. You also need to look at this for x64 on 2.0 if you're running both (http://support.microsoft.com/kb/894435). Like Michael said, does it happen on a brand new mailbox? Also, does it happen for an admin mailbox (permissions)? -Bonnie -----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 5:17 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and Rich OWA This sounds vaguely familiar...by some chance have you checked on whether your user objects have the accessibility flag set? (If you create a brand new user, brand new mailbox, direct from the EMC, does this happen?) Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Steve Szabo [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 10:45 PM To: MS-Exchange Admin Issues Subject: Exchange 2007 and Rich OWA We have a relatively new install of Exchange 2007 SP1 and have been playing around with it a bit until late last week when we had a problem with the box housing Exchange 2003. We had a few mailboxes already on 2007, and moved the rest of them over. Everything seemed to be working well until someone tried to use the rick client of OWA. It does not work. The Inbox will come up, but if you try to go to the next page of e-mail, you get a 404 error. I did not have a chance to check this, but it was reported that a message could not be deleted. Also both the rich and basic versions give me a 404 when logging out. I have not been able to determine anything from the event logs, and found some other instances of similar problems when Googling with a changing variety of terms, but I have not found anything that would lead me to a resolution of the problem. Prior to hearing about this, I found I had to install the 64 bit version of .NET 2.0, and I had a world of hurt until I removed .NRT 1.1, 2.5, and 3.0 and ran the cleanup tool available from a blog by one of you gurus here. Right now I have only the 64 bit version of 2.0 running, which appears to be necessary for OWA. I have yet to take a look at the web logs to see if I can get a hint from them, but I am not sure I would be able to determine anything that will help me there. I'm pretty well booked this week (got home after 9 PM tonight), so I am not sure when I will be able to put any real work into this for the next few days (we can live with the basic OWA). Does anyone have anything I should take a look at to resolve this issue? \\Steve// ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
