We help IT Professionals succeed at work.

How do I stop HTTP Error 400 - Request is badly formed when opening an email using OWA

Medium Priority
7,425 Views
Last Modified: 2012-05-06
Hi Experts

Can you help me with the following;
Our email was working perfectly until now, no hardware changes were made to the server. We moved the page file to another drive on the server as our C Drive was running low in disk space.  The logs and Database files are located on a different drive. There has been now new WIn updates or any other applicatiosn installed since issue occured.   We use Exchange 2003, IIS6.0 all running on Win 2003 Server Standard.

We can log on internally & exteranlly to our mail and indeed can see all the messages in our inbox etc.  However when we try to open a message, forward or reply we get the following error...
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.

I cannot figure this out, any advise greatly appreciated.


Comment
Watch Question

Expert of the Quarter 2009
Expert of the Year 2009

Commented:
Error 400 is highly generic, doesn't say a great deal.
Run the best practises tool on the server (download from Microsoft) and see if that flags anything of interest.
You may have to go through the IIS logs to see if those show anything of interest as well.

-M
Hi Mestha

Thanks, I actually manged to sort it out
I simply reinstalled KB950159

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.