Link to home
Start Free TrialLog in
Avatar of dblake15

asked on

OWA HTTP 405 verb error

All of a sudden when I try to connect to owa I get a The page you are looking for cannot be displayed because an invalid method (HTTP verb) was used to attempt access.  

It used to work fine and now it does not.  Not sure what changed.  Any ideas on how to fix this??

Avatar of Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Based on the information that you have provided above, impossible to say.

Do you have SP1 installed?
What has changed? OWA etc doesn't stop working for no reason. Anything new installed on the server?

Hi dblake15,

where there any changes made to your system at all as you noticed the failure? When you look in the IIS is the virtual folder " Exchange" still there?

Could you post your IIS Logfile?
Avatar of dblake15

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of LeeDerbyshire
Have a look at your IIS log file ( the latest file in C:\Windows\System32\logfiles\w3svc1 ) and look for the request that generates the 405 error.  Note that the times are in GMT.  The 405 status will usually (but not always) be the third number from the end of each line.  The verb is near the beginning of the line, and will probably be POST, but may be something else like GET, PUT, SEARCH, HEAD, PROPFIND, etc.  Whatever it is will be missing from the IIS config for the Virtual Directory (exchweb or owa).
Avatar of dblake15


POST /owa/auth/owaauth.dll - 443 - 10.0.x.xx Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+WOW64;+SV1;+.NET+CLR+2.0.50727) 405 0 1

This is the only 405 error that I see in there.
Can you see any other entries that have POST near the beginning, but do not have 405 near the end?
Do I need forms based auth even set??
No, it just provides a pretty login screen, instead of the grey popup box.  It does stop your users saving their credentials in the browser's cache, though.
how have you published your OWA? Is the Form Based yoused by your Exchange or over an ISA Server?
just by exchange, no ISA server.
You can try the followring and see if it works:

FIX: IIS 6.0 compression corruption causes access violations

I was able to fix this problem on Exchange 2003 by disabling Forms Based Authentication on the Exchange Virtual Server, restarting IIS, re-enabling Forms Based Authentication on the Exchange Virtual Server and then restarting IIS again.