7,925 questions
Hi @hyt joseph ,
Hopefully, this helps you.
owa error 400 Bad Request
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 28.000000000000004%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHJ%3C/text%3E%3C/svg%3E)
hyt joseph
86
Reputation points
When I try to access OWA from any client I get an HTTP 400 Bad Request error.
Accessing ECP works fine. what's wrong?
Exchange | Exchange Server | Management
Accepted answer
1 additional answer
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Joyce Shen - MSFT 16,701 Reputation points2020-07-31T05:38:41.733+00:00 What's your Exchange server CU version and what changes have been made recently on your server? Could you please provide the complete error information or any screenshot about your error?
Have you tried recreating the OWA virtual directory and recycling the OwaAppPool in IIS manager and verify the result again?
Generally we could also try running the UpdateCas.ps1 and UpdateConfigFiles.ps1 to rebuild your OWA interface below the path C:\Program Files\Microsoft\Exchange Server\V15\Bin\
You could refer to the solutions in this similar thread to help resolve your issue as well: Exchange 2013 OWA 400 Bad Request