asked on

Bad Request when loading ECP on Exchange 2010

When I or any other user try to open webmail.domain.dk/ecp we are redirected to the Language selection page and when clicking Ok we get a "Bad request" and the address bar shows https://webmail.domain.dk/owa/lang.owa.

As far as I can see, it is because of the mailboxregionalConfiguration which is set to danish.

[PS] C:\tools>Get-MailboxRegionalConfiguration kasper

Identity             Language        DateFormat TimeFormat TimeZone
--------             --------        ---------- ---------- --------
                     da-DK           dd-MM-yyyy HH:mm

Open in new window

What is going on here? How do I get into ECP again. I have to keep the regional settings.

Any help is appriciated.

Rodney Barnhardt

You could try a reset of the virtual directory.

set-OwaVirtualDirectory "owa (default web site)" -DefaultClientLanguage 0

Kasper Katzmann

ASKER

It didn't help. I gor this instead:

[PS] C:\Windows\system32>Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -DefaultClientLanguage 0 -LogonAndErrorLanguage 0

WARNING: The command completed successfully but no settings of 'CAS2\owa (Default Web Site)' have been modified.

Open in new window

Rodney Barnhardt

Does your external link for OWA exactly match the ECP link path? If not, then ECP will not work correctly. The paths must match up to the /ecp or /owa. If you correctly match the paths this should work fine. Do the paths match?

Kasper Katzmann

ASKER

They match just fine (unfortunately)

Rodney Barnhardt

That is strange, because your problem sounds just like this one.

https://www.experts-exchange.com/questions/27572683/Users-can't-access-OWA-2010-ECP-page.html

Kasper Katzmann

ASKER

Latest update:
It now seems that for some users it is working, but for others it don't.
That doesn't make it any less strange, but baybe it can give you some clue...

ASKER CERTIFIED SOLUTION

Kasper Katzmann

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Kasper Katzmann

ASKER

It was due to missing timezone information on those users. When I updated them to use the same timezone as the rest of the organization, it worked. Problem solved.