Help!!!! What to do about this error message?

The most common reason for a 400 Bad Request error is because the URL was typed wrong or the link that was clicked on points to a URL with some kind of mistake in it.

Explanations(sp) of error message:

Error Message: "400 Bad Request"

Interpretation: This message falls into a catch-all category, and unfortunately, it doesn't tell you a lot (other than you can't access the page you requested, which you already know).

This behavior is expected when the GET request itself cannot be parsed because of some kind of packet corruption. If you send a bad request to the IIS Web server, the Custom Errors functionality is not invoked, which causes the "HTTP/1.1 Error 400 - Bad Request" error message.

With that said you can patch the .net framework using windows update and see if that resolves the issue.

Also, If you enable this fix mentioned below, you increase the attack surface of the application. You should not enable this fix unless the application requires it.

After you install the service pack, set the following registry key to enable the fix:

DWORD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET VerificationCompatibility = 1

3 hundred and sixty 5 days-month/day errors: 569-17 sorry we are no longer able to deliver you message right now in case you suspect it particularly is an errors message #569-17 respond: connect *your first call Ex; connect *sam