501 - Header values specify a method that is not implemented

All Replies

• Friday, July 17, 2009 2:06 AMWayne Phillips.MVP

   
  

  0

  Sign In to Vote

  If you are running Exchange 2007 SP1 than the URL should end in /owa rather than /exchange. If you have a mixed 2007,  2003 environment then /exchange is fine. Give us a bit more information regarding Exchange server roles... is this a CAS server ?
  
  The /exchnage and /exchweb directories should have Basic Authentication enabled.
  
  I'm assuming you want to enable Mobile Services (ActiveSync) ?
  
  Cheers Wayne
  Airloom

  • Reply
  • Quote

   
• Friday, July 17, 2009 5:51 AMPeterN22

   
  

  0

  Sign In to Vote

  One server with all roles on it (mbx, ht, cas).
  
  There is a trhid party application that needs to connect to mailboxes using https://mail.mydomain.local/exchange/user@mydomain.com/inbox.
  If I try that, I always receive an authentication pop up, and after that there is a redirection to forms-based authentication. So I have to authenticate twice, and that is the problem. This application is not able to handle that.
  
  
  Regards
  Peter

  • Reply
  • Quote

   
• Monday, July 20, 2009 10:54 AMElvis Wei -MSFTMSFT, Moderator

   
  

  1

  Sign In to Vote

  Hi Peter,

   

  I suggest trying the following steps:

   

  1) Open Exchange Management Shell

  2) Run the following commands:

   

  Remove-OwaVirtualDirectory "exchange (default web site)"

  Remove-OwaVirtualDirectory "exchweb (default web site)"

  IISRESET

  New-OwaVirtualDirectory "exchange" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Mailboxes -WebSiteName "Default Web Site"

  New-OwaVirtualDirectory "exchweb" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Exchweb -WebSiteName "Default Web Site"

  IISRESET

   

  3)Test the issue again.

   

  Thanks,

   

  Elvis

  • Reply
  • Quote

   
• Wednesday, July 22, 2009 3:39 PMPeterN22

   
  

  0

  Sign In to Vote

  Hi Elvis
  
  Thanks for your response.
  That seems work, but now there is another problem.

  I'm logged in on my workstation and I open a connection to https://mail.mydomain.local/exchange/myuser@mydomain.com/inbox. Then I receive an authentication popup. I enter my credentials and I have the connection to my mailbox. That works because of the windows integrated authentication.
  
  Now I am still logged in as myuser and I open a connection to https://mail.mydomain.local/exchange/anotheruser@mydomain.com/inbox. Again I receive an authentication popup. I enter the credentials of "anotheruser" and I am redirected to the forms-based window, where I have to authenticate again. Because I am logged in as myuser, the windows integrated authentication does not work for "anotheruser".
  
  The problem is that this third party application runs on a server and has to do connections to different mailboxes, and it has a problem with this double authentication process.

  Might there be a way to avoid the first authentication popup?
  
  
  Regards
  Peter

  • Reply
  • Quote