Problems when using Host Headers

If host headers are used for the CRM web site a number of problems may occur including, workflows stuck at waiting, duplicate detection rules not working, Outlook configuration not working and so on. The issue appears to be how rows in the DeploymentProperties table in MSCRM_CONFIG are configured.

To check whether this is the issue, run the following SQL statements against the MSCRM_CONFIG database:

USE MSCRM_CONFIG

SELECT NVarCharColumn
FROM deploymentproperties
WHERE columnname = 'AsyncSdkRootdomain'

SELECT NVarCharColumn
FROM deploymentproperties
WHERE columnname = 'ADSdkRootdomain'

SELECT NVarCharColumn
FROM deploymentproperties
WHERE columnname = 'ADWebApplicationRootdomain'

The results should be of the form:

crm:80

for each query (depending on the host header name used and whether you have split out the various services to different servers). Often the AsyncSDKRootDomain value is blank and this is the cause of the problems.

To correct this, use the following SQL Statement (use the correct host header for your installation):

UPDATE DeploymentProperties SET
NVarCharColumn = 'crm:80'
WHERE ColumnName = 'AsyncSdkRootdomain'

 

Categories