Link to home
Start Free TrialLog in
Avatar of comphil
comphilFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Outlook Web Access 'Bad Request' When Viewing Emails

Hi there,

I am supporting a server which is about 1 year old and runs Windows Small Business Server 2003 (fully up to date).  Normally it behaves fine but recently a new problem has emerged:

When using Outlook Web Access, you can log in fine, but any user I've tried has problems opening/replying/forwarding emails which have long subject lines (such as the Working Remotely with Windows Small Business Server email) or contain characters like : (colon) .  There doesn't appear to be one defining characteristic with all the affected emails.

When opening them, instead of the message pane on the righthand side, I get an error page stating:

Bad request
The page that you are looking for might have been removed, had its name changed, had its content expired, or is temporarily unavailable.

Please try the following:

    * Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
    * If you reached this page by clicking a link, contact the Web site administrator to alert them that the link is incorrectly formatted.
    * Click the Back button or open the home page for this Web site and look for other links to the information that you want.

HTTP Error 400 - Request is badly formed.
Internet Information Services (IIS)

Technical Information (for support personnel)

    * Go to Microsoft Product Support Services and perform a title search for the words HTTP and 400.
    * Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Web Site Setup, Web Site Administration, and About Custom Error Messages.

One-word subject emails seem to be fine.  I've tried everything I can think of but have had no joy.  It doesn't appear to have any relation to a similar problem on an MS KB where the HTTP Error is to do with the URL being too long.  I've tried the 3 registry fixes as suggested anyway with no luck.  Have also downloaded .NET Framework 1.1 SP1 but it won''t apply so I appear to have the latest version.

Can anyone help?

Thanks in advance.

Phil

Avatar of Carlos_Paleo
Carlos_Paleo

There are some things you can try:

http://support.microsoft.com/?scid=kb%3Ben-us%3B839913&x=18&y=12

Go into Internet Options, Advanced, and untick "Enable Integrated Windows Authentication".  Restart IE, and try connecting to OWA again. Then add the http://*COMPANYNAME*/ to the trusted sites zone via Group Policy, all clients will then be able to connect.
Avatar of comphil

ASKER

Sorry but the Microsoft article doesn't address the problem I'm having.  I've already tried adding the site to the Trusted Zone without success.

This error is almost certainly server-caused because I can reproduce it by visiting the OWA site from anywhere inside and outside the network using both the site IP and the full DNS address plus it also occurs browsing locally on the server.
Avatar of comphil

ASKER

The error also occurs both in Internet Explorer 6, 7 and Firefox 3
Ok, so it may be solved by the KB: http://support.microsoft.com/default.aspx?scid=kb;en-us;831464

In case it states you dont need that KB, double check if you have excluded the MDBDATA directories from AV scanning in your software.
ASKER CERTIFIED SOLUTION
Avatar of comphil
comphil
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am having this exact same issue - and a reboot has not resolved.