locked
CRM 2016 On Premise IFD: 405 - HTTP verb used to access this page is not allowed. RRS feed

  • Question

  • Okay, have installed CRM, set up SSL and IFD with a customer.

    The customer is handling the DNS side of things.

    We are now getting the following error:

        405 - HTTP verb used to access this page is not allowed.

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

    This isn't an error I have seen before and am at a loss as to how I should debug it.

    HTTP has certificate but is still set to 5555 rather than 443.

    server:5555 is mapped to crm.customer.co.uk in DNS.

    The federated metadata is all mapped fine.  Not sure how to determine the issue (CRM side or Network side).

    Can anyone shed any light on this problem?

    Tuesday, May 30, 2017 4:19 PM

Answers

  • Thanks.

    Firstly I need to add the 5555 port to all the domain fields in the wizards.  There were a number of firewall issues as well that combine to make this quite complicated.

    Of course examples tend to assume port 443 so it's not always obvious that you need to do that.

    Friday, June 2, 2017 7:41 AM

All replies

  • Should say the crm.customer.co.uk:5555 bounces to crm.customer.co.uk which the displays the error.

    Not sure if that is significant.

    Feels more like the URL is not hitting the CRM web site properly!?

    Tuesday, May 30, 2017 4:24 PM
  • First thing to check is that https is used throughout - i.e. the user should be going to https://crm.customer.co.uk . If the client is trying to connect using http, then I'd expect it to fail, as and DNS or port mapping won't change the protocol

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Wednesday, May 31, 2017 9:14 AM
    Moderator
  • Thanks.

    Firstly I need to add the 5555 port to all the domain fields in the wizards.  There were a number of firewall issues as well that combine to make this quite complicated.

    Of course examples tend to assume port 443 so it's not always obvious that you need to do that.

    Friday, June 2, 2017 7:41 AM