Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Authentication with host headers RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I have an installation in which MS CRM 4.0 (Rollup4) has been installed on IIS with multiple sites and as such, installed using host headers and IFD.

    The site is reacheable externally using the following url: http://dynamics.mycompany.com
    On the MS CRM machine however I can't reach the web page. 'http://dynamics.mycompany.com' resolves to the localhost address 127.0.0.1, so I would assume there are no DNS issues.

    Suggestions appreciated.
    Karlo Swart - http://www.ver206.com
    Monday, June 29, 2009 10:25 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Karlo,

    It looks like you are facing the loopback related issue. Please find the following KB to check for the solution. In similar cases that I have faced, disabling loopback checking helped (solution 2 from the KB). The KB is here: http://support.microsoft.com/kb/896861

    I hope that helps,
    Kuba
    -- Kuba Skałbania, Netwise
    Monday, June 29, 2009 10:28 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Karlo,

    It looks like you are facing the loopback related issue. Please find the following KB to check for the solution. In similar cases that I have faced, disabling loopback checking helped (solution 2 from the KB). The KB is here: http://support.microsoft.com/kb/896861

    I hope that helps,
    Kuba
    -- Kuba Skałbania, Netwise
    Monday, June 29, 2009 10:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Kuba thanks. That seemed to have resolved the local access.

    Just to elaborate on our problem and the resolution. The client was unable to run any workflows on their system, which I believe was partly as a result of this problem.

    Based on an article from http://www.sadev.co.za/node/155, we manually updated the following fields to point to the correct host header.

    USE MSCRM_CONFIG
    Update DeploymentProperties SET NVarCharColumn = 'dynamics.myclient.com' WHERE ColumnName = 'AsyncSdkRootDomain'
    Update DeploymentProperties SET NvarCharColumn = 'dynamics.myclient.com' WHERE ColumnName = 'ADSdkRootDomain'
    Update DeploymentProperties SET NvarCharColumn = 'dynamics.myclient.com' WHERE ColumnName = 'ADWebApplicationRootDomain'

    In particular updating the first value (     AsyncSdkRootDomain) and restarting that service resolved their issue. Note I appreciate this would be considered 'unsupported' to process with caution.

    Many thanks,
    Karlo


    Karlo Swart - http://www.ver206.com
    Tuesday, June 30, 2009 5:09 PM