• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5621
  • Last Modified:

Outlook Web Access return "HTTP Error 405 - The HTTP verb used to access this page is not allowed." on Windows SBS 2003 IIS 6.0

Hi,

Since I've ran the Internet connection wizard this morning in order to change the self served certificate, everything seem to be worst then ever...

Now that I've almost got rid of all that mess, only one thing remain and this is the Outlook Web Access for the Exchange server. The web site is back online, asp pages work just fine and we can gain access to the OWA login page. But as soon as a domain user try to login it ends up to this link

https://XXXX.XXXXXXX.com/exchweb/bin/auth/owaauth.dll

With the following webpage content;

The page cannot be displayed
The page you are looking for cannot be displayed because an invalid method (HTTP verb) was used to attempt access.
--------------------------------------------------------------------------------

Please try the following:

Contact the Web site administrator if you believe that this request should be allowed.
Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
HTTP Error 405 - The HTTP verb used to access this page is not allowed.
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 405.
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Setting Application Mappings, Securing Your Site with Web Site Permissions, and About Custom Error Messages.  


I ve went thru ExpExc and found nothing about it. Even on MS web site, it is not clear.

Does anyone have an idea of what it is and how to solve this issue?
0
SirTKC
Asked:
SirTKC
  • 2
  • 2
1 Solution
 
SembeeCommented:
Haven't seen that one for a while.

Lets try the simple fixes first.

In IIS Manager, check the Application pools are set correctly:

/exchange - ExchangeApplicationPool*
/exchweb - ExchangeApplicationPool*
/exadmin - ExchangeApplicationPool*
/public  - ExchangeApplicationPool*
/oma - ExchangeMobileBrowseApplicationPool
/Microsoft-Server-ActiveSync - ExchangeApplicationPool

* will probably show ExchangeApplicationPool but greyed out.

While in IIS, ensure that asp.net is allowed, as is asp.

Also take a look at this KB article...

http://support.microsoft.com/default.aspx?kbid=831464

Is sharepoint on this machine?

Another one that might work is to reset the virtual folders totally.
http://support.microsoft.com/default.aspx?kbid=883380

Simon.
0
 
SirTKCAuthor Commented:
Hi Simon,

I did check what you mentionned. It was all as your list above.

ASP.NET & ASP are allowed

KB 831464 Does not apply. The patch available is older then the one on the server. So it refuse to get installed

And yes: SharePoint is running on that server. Is this having any impact on OWA?

I did'nt went further then that.

I really do suspect that this is a permission issue!
0
 
SembeeCommented:
Sharepoint breaks OWA.

They will co-exist, but you have to make changes to the sharepoint config.

http://support.microsoft.com/default.aspx?kbid=823265

Simon.
0
 
SirTKCAuthor Commented:
Thanks,

Yes this comment should be classified but the solution has been found on site.

When this problem occured, we renewed our server certificate (SSL). because we went from a self server certificate to a registered one, we did'nt made the change on SharePoint. So we were getting this error every time we tried to access Exchange using OWA.

As soon as we specified the same certificate to sharepoint as Exchange, everything started to run smooth and clean.

This post should be classified but remain available for any further query about it. It was not an easy one!
0
 
GranModCommented:
PAQed with points refunded (500)

GranMod
Community Support Moderator
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now