I'm currently experiencing an error with my OWA 2007 after any of my users attempt to log in. The OWA start page loads fine upon prompting to log in, but after a login is attempted this error message is received:
Microsoft Exchange issued an unexpected response (500).
Exception Exception type: System.Web.HttpCompileException Exception message: c:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\forms\premium\startpage.aspx(33): error CS0117: 'Microsoft.Exchange.Clients.Owa.Core.Configuration' does not contain a definition for 'AllLegacyPublicFolders'
I've already recreated the entire OWA directory through the Exchange Management Shell with this KB Article: http://support.microsoft.com/kb/941201 and have attempt to resolve this issue directly with a Microsoft Exchange Specialist. If there's anyone with useful hints or fixes it would be deeply appreciated.
This old KB had a hint which might point you in the direction of checking your sites and services config: http://support.microsoft.com/kb/316349 . "This problem can have several causes, one of which is if an administrator adds an additional site but does not define subnets."
Do you have a public cas in one site and non-public cas in your mailbox site? It could be an authentication issue... public cas should use form-based authentication, and "backend" (ie, CAS in another site accessed via CAS2CAS proxying) should not use forms based authentication.
*edit* I fixed the link. The period at the end of my sentence was causing the link to become invalid. Try it now.
< Message edited by Ytsejamer1 -- 11.Aug.2011 2:44:10 PM >
I currently have 3 roles installed on one box, Mailbox, CAS, and Transport all on the Exchange 2007 box. We have an older server that have the same roles installed on an Exchange 2003 box. That box is currently on the 'backend' routing mail for our Blackberry clients. The Exchange 2007 CAS is the Public domain. It was working at one point in time until I installed Rollup 10. I figured removing it would solve the issue but it has not.
I've checked several settings such as AutoDiscover, several virtual directory's authentication, editted certificates, etc. I've even attempt to test it under port 80 rather than port 443. I don't believe it's an Authentication issue because even while the 2 boxes co-exsisted in the same Forest and Domain, it was working.
You can co-exist Exchange 2003 and 2007 systems, but 2007 CAS must be used for processing OWA and other "frontend" services. It will then talk to the backend exchange 2003 servers to present your users it's legacy OWA experience.
It is possible to upate to SP3, I would just have to correlate with the rest of the Department. I've already attempted to recreate the OWA virtual directory and to no avail. I do realize that the 2 can co-exsist. My mailboxes are stored on 2007, the only thing the 2003 box is doing is forwarding mail for out Blackberry clients.
I will update the SPs over the weekend and will keep you posted.
I've just come accross a new discovery that I have seen before with OWA 2007. My co-worker came accross the fact that OWA Light is accessible to log in. Some users can tick OWA Light through IE 8 and 9 and have access to thier mailbox while others do not. Same thing goes with External users logging in through their Mobile Device's browser.
Also, If another browser other than IE is used, such as Firefox or Safari, it allows the user to log in. I do realize that that option is ticked for any other browser other than IE.
Another strange thing is that the Logout Link is broken. You can click as much as you'd like and the page sits stagnant.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> OWA 2007 Interal Error 500 after logging in. 
OWA 2007 Interal Error 500 after logging in. - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
