Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Organization Data Service (OData) Service does not work on all of the IIS binding ports RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    My CRM 2013 instance has been configured on HTTPS protocol in the CRM Deployment Manager. I have more than one binding for the CRM web application in IIS (HTTP:80, HTTP:8080 and HTTPS)

    Most of the CRM pages and services are working on all of the IIS Bingings, including Organization Service (SOAP)

    The problem is that Organization Data Service (OData) works only on the port that is defined in the CRM Deployment manager. The other IIS Binding ports are unavailable.

    How can I have Organization Data Service (OData)  work on all of the ports available through IIS bindings not just what is defined in the Deployment manager?

    Thank you,

    Sunday, October 19, 2014 1:40 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    "The Web site should have a single binding. Multiple  IIS bindings,  such as a Web site with an HTTPS and an HTTP binding or two HTTPS or two HTTP bindings, are not supported for running Microsoft Dynamics CRM."

    http://technet.microsoft.com/en-us/library/hh237635.aspx

    the symptoms are like you mention, most everything works, some endpoints will die

    I Hope I could help. If I have answered please mark as 'Answer'. If was just helpful, please vote. Thanks and happy coding! Bruno Lucas, http://dynamicday.wordpress.com/

    • Marked as answer by amx2012 Wednesday, June 3, 2015 8:48 PM
    Monday, October 20, 2014 3:15 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    "The Web site should have a single binding. Multiple  IIS bindings,  such as a Web site with an HTTPS and an HTTP binding or two HTTPS or two HTTP bindings, are not supported for running Microsoft Dynamics CRM."

    http://technet.microsoft.com/en-us/library/hh237635.aspx

    the symptoms are like you mention, most everything works, some endpoints will die

    I Hope I could help. If I have answered please mark as 'Answer'. If was just helpful, please vote. Thanks and happy coding! Bruno Lucas, http://dynamicday.wordpress.com/

    • Marked as answer by amx2012 Wednesday, June 3, 2015 8:48 PM
    Monday, October 20, 2014 3:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    so the solution would be to configure the IIS and the Deployment-Manager to support just http OR https, and not mixing the bindings?

    Then application access and web service access would also be the same protocol wise.

    Friday, June 3, 2016 7:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, there should be just one binding. Deployment Manager only lets you specify one, and you should only have one in IIS. I think the reason OData fails to work is that it will always try to connect using the binding specified in Deployment Manager, even if pages are served from a different binding

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

    Friday, June 3, 2016 4:39 PM
    Moderator