OWA Migration Issue

[swasser]

I am currently running a co-existence environment with Exchange 2003 and Exchange 2010. The 2010 environment is 4 CAS server and 2 mailbox/hub transport servers. Recently I ran into an issue with a couple of accounts that were migrated in where they are now unable to access OWA. When they attempt to login to OWA it simply hangs, almost looking like the CAS server is having trouble with which server to direct the request to. Other migrated users on this same mailbox server can access OWA with out any issue. The only commonality I can place with the users who do not work is they are all part of the same mailbox store. Now Outlook did not have any issues transitioning over to the correct server and presenting their mailboxes so its only an OWA issue.

Any thoughts or ideas on this would be greatly appreciated.

Thank you,

 

[theravager]

try a set-mailbox xxx -applymandatoryproperties on the affected accounts

 

[theravager]

Other common one is to check the user accounts that inheritance is enabled on the accounts in the security tab in aduc.

 

[swasser]

Update: When using Chrome to access OWA users are hit with this error message.

"/languageselection.aspx has resulted in too many redirects."

I have taken quite a few steps to resolve this issue without any success. The CAS servers are running Exchange 2010 SP2 with rollup 3. All of the latest MS security patches have been installed. I have removed and re-created the OWA virtual directories, but the problem still persists. Now I know I can force a default language selection on everyone which will allow users past the language selection screen. But then they are not able to perform any functions while they are in their mailbox. They keep receiving the following error message when setting the default language.

"unexpected error occured and your request can't be handled.

 

[swasser]

This is the other error users are receiving when attempting to do any work in their mailboxes.

"Your network connection is unavailable. Please reconnect and try again

 

[ShackDaddy]

How about looking at the language settings mailbox properties on the users affected: "Get-mailbox [useralias] | fl languages" and see if the language options are set already to a language that is not supported by the server. If you could set that property to $null, then maybe they wouldn't have any issues, or you could set the property to what everyone else has. Probably {en-us}.

Dave Shackelford
ThirdTier.net
TrainSignal.com