Hello, We have a user in our enviroment that cannot logon through OWA (Outlook is working fine). Whenever he logs on he gets the below error. On the CAS server a similar event is logged. There is nothing much on the web that I can find about this error in relation to OWA. The servers are all 2008 SP2 with fixes up until a few weeks ago. Exchange is on SP2 rollup 9 any ideas out there? Request Url: https://servername:443/owa/forms/basic/BasicMessageView.aspx User host address: xx.xx.xx.xx User: User Name EX Address: /o=Org/ou=First Administrative Group/cn=Recipients/cn=username SMTP Address:smtp@address.com OWA version: 8.2.247.2 Mailbox server: servername Exception Exception type: System.IndexOutOfRangeException Exception message: Index was outside the bounds of the array. Call stack Microsoft.Exchange.Clients.Owa.Basic.Controls.ListViewContents..ctor(ViewDescriptor viewDescriptor, ColumnId sortedColumn, SortOrder sortOrder, Boolean showFolderNameTooltip, UserContext userContext) Microsoft.Exchange.Clients.Owa.Basic.Controls.MessageListViewContents..ctor(ViewDescriptor viewDescriptor, ColumnId sortedColumn, SortOrder sortOrder, Boolean showFolderNameTooltip, UserContext userContext) Microsoft.Exchange.Clients.Owa.Basic.Controls.MessageListView.InitializeListViewContents() Microsoft.Exchange.Clients.Owa.Basic.Controls.ListView.Initialize(Int32 startRange, Int32 endRange) Microsoft.Exchange.Clients.Owa.Basic.MessageView.CreateListView(ColumnId sortColumn, SortOrder sortOrder) Microsoft.Exchange.Clients.Owa.Basic.ListViewPage.OnLoad(EventArgs e) Microsoft.Exchange.Clients.Owa.Basic.MessageView.OnLoad(EventArgs e) System.Web.UI.Control.LoadRecursive() System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hi If he tries to logon from the LAN directly against the CAS server like: https://exchange2007cas.domain.local/OWA Do you have any sort of coexistence? Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Tried that indeed but get exactly the same error. There are still 2 2003 Exchange boxes in the environment (due to unity voicemail dependancies).

Have you migrated the account to your 2007 server(s)? The info below looks like it's located on your 2003 server EX Address: /o=Org/ou=First Administrative Group/cn=Recipients/cn=username Push the AD replication and check so it worksJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

The user came from a 2003 box, the part you're seeing is his legexchangedn / X500 address. Similar to a whole slew of others for which OWA works fine. It's just this one guy that has issues.

Can you move his mailbox to another store and test?

Sorry could have mentioned that. Yeah moved him to another CCR cluster altogether. Same issue. Ran set-mailbox -applymandatoryattributes just in case, reported it ran OK but there was nothing to update Reset the permissions on his account, did not help Tried opening it while logged on as myself after granting me permissions to his mailbox, no go Outlook works fine even through Outlook Anywhere via a ISA box Other then recreating the silly thing I don't know what else to try :) Though I'll be preventing that for as long as possible as I'll loose sleep over not knowing what the issue was ;)

Hi, To narrow the root cause, I recommend you first try to log into the user's mailbox by using another computer. If you can log into OWA without problem, the problem should reside in the user’s computer. If the issue persists, please try the following steps: 1. On exchange server, create a new mailbox database. 2. Move the user's mailbox to this new mailbox database. Then test to see if the issue persists.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Thanks for the suggestions Gen, but we had already tried both. (Even moved the mailbox to another server) Neither changed the situation and threw the error.

On Mon, 13 Sep 2010 12:39:44 +0000, Old Arn wrote: >Thanks for the suggestions Gen, but we had already tried both. (Even moved the mailbox to another server) Neither changed the situation and threw the error. What web browser is he using? It looks like he's using the "basic" version of OWA. If he uses IE as his browser and switches to the "premium" version of OWA does he still have the same problem? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Had not given that a try, but getting the same error in IE7 and 8. Since this is Exchange 2007 there is only "normal" and OWA Light. Both give the same error. Public vs Private computer also did not make a difference. Even tried firefox for the heck of it, it only has the light edition, same error Was definitly worth a shot.

On Mon, 13 Sep 2010 15:22:24 +0000, Old Arn wrote: >Had not given that a try, but getting the same error in IE7 and 8. Since this is Exchange 2007 there is only "normal" and OWA Light. Both give the same error. Really? The URL in the error was the same using both versions??? Request Url: https://servername:443/owa/forms/basic/BasicMessageView.aspx >Public vs Private computer also did not make a difference. Even tried firefox for the heck of it, it only has the light edition, same error That's not surprising. I really wasn't after a browser error, I just wanted to know if switching to the "normal" (i.e. 'premium') OWA resulted in the same problem. I thought that it would change the URL to use "...owa/forms/premium/MessageView.aspx" and perhaps use a different bit of code to render the message. >Was definitly worth a shot. I'd guess there's a message (mayby more than one) that's got something screwy in it. You've already tried moving the mailbox (that usually fixes lots of problems) and that didn't help, so I think you're into trying to export the mailbox contents to a PST and blowing away the mailbox. Importing the messages should give you a working mailbox. It may also be worth opening a case with Microsoft. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP