Outlook Web App 2010 Redirect to Outlook Web Access 2007 for New Mailboxes when selecting German language at first Logon resulting in 400 Bad Request.

  • Article

Consider the following scenario – Exchange 2010 SP1 RU1 + Exchange 2007 SP3 mixed environment.

 

Internet Facing CAS Server is an Exchange 2010 SP1 RU1 CAS.

1.) Create a new User on Exchange 2007, open Outlook Web App 2010 to log on to Exchange 2007 Mailbox https://Exchange2010server/owa and Log On

2.) Select German as the Language when being prompted to select Language and Time Zone, click OK

RESULT: Redirection goes to https://Exchange2007server/Owa/OWA.lang  with a 400 Http Error.

IIS LOGS: show the same: 400 Bad Request.

This is a known issue at the moment, we are currently working to fix this.

Until the fix is out, we would like to provide you with the following workaround:

The only way to make this working for the moment is to set the default language on the Exchange 2007 Virtual Directory to 1033 ( En-Us Language )

To do this, please adapt this Powershell command to your environment:

Get-OwaVirtualDirectory "Exchange2007cas\owa (Default Web Site)" |Set-OwaVirtualDirectory -DefaultClientLanguage 1033

Result: New created Mailboxes, will have the default Language set to English.

After this, when accessing https://Exchange2010server/Owa they will be automatically redirected to their Mailbox on the Exchange 2007 Server https://Exchange2007server/owa

They will have to manually go to options, Regional and language settings and set their language to German if needed.

We are currently working on the Fix, please be patient. We apologize for this inconvenience and thank you for your understanding.

 

 If you have any questions, please send me an Email to patrisel@microsoft.com

Patrick

Comments

  • Anonymous
    January 01, 2003
    Hi Shurley, Thank you very much for the feedback. Can you please inform us also what the exact language was, so that we can document this internal and maybe also here in the article ? Patrick

  • Anonymous
    January 01, 2003
    Hi Darren, Thanks for your feedback ! Yes, this is correct, you have to set it on all of your CAS servers. Anyway, I hope the workaround fits you :) If you have anymore questions, please leave a comment or write me an Email.

  • Anonymous
    January 01, 2003
    Hi Sebastian, It's internally documented that this issue will be fixed in Exchange 2010 Service Pack 2. Patrick

  • Anonymous
    November 12, 2010
    Patrick, FYI, this happens in our environment for new users even when we leave it set to English.  The workaround hasn't worked for us.

  • Anonymous
    November 12, 2010
    Okay, I spoke too soon!  We hadn't set the DefaultClientLanguage on ALL of our 2007 CAS servers.  Thank you!

  • Anonymous
    December 01, 2010
    Thank you!  I have this very situation, but it was not "German" but one of the Asian languages.  However, the work around did fix the issue.

  • Anonymous
    February 24, 2011
    Hi Patrick,   I know this is an old thread, but I'm experiencing a somewhat similar issue.   In a new Exchange 2010 SP1 (RU2) environment upgrading from 2003, we set the defaultClientLanguage property on all the OWA sites so that users wouldn't get the initial prompt when they first logged in. This works fine, but when they go to access Options (the ECP), they are prompted with the "languageselection.aspx" page, and no matter what they pick, they get an HTTP 400 error on lang.owa and can't reach the options.   The only workaround I've found is to use Set-MailboxRegionalConfiguration for each mailbox and manually define the "language" property. This bypasses the language selection page and lets them access ECP.   I haven't found any other references to this issue online, so I don't know if I'm the only one experiencing this. Any ideas? Thanks!

  • Anonymous
    April 15, 2011
    Hi Patrick, Do you know when this problem is going to be fixed?

  • Anonymous
    July 05, 2011
    Hi Patrick, I too, am having the same issue as Aaron Firouz: "In a new Exchange 2010 SP1 (RU2) environment upgrading from 2003, we set the defaultClientLanguage property on all the OWA sites so that users wouldn't get the initial prompt when they first logged in. This works fine, but when they go to access Options (the ECP), they are prompted with the "languageselection.aspx" page, and no matter what they pick, they get an HTTP 400 error on lang.owa and can't reach the options". Is there a known fix for this issue?   Thanks!

  • Anonymous
    July 05, 2011
    Just wanted to post a solution that seems to have worked for me: I entered this in the exchange management shell: set-OwaVirtualDirectory "owa (default web site)" -DefaultClientLanguage 0 The user is then asked for the language once. After that they could access Options.