CRM Migration Manager – manager cannot connect to the Microsoft CRM server

I thought I’d just let you know about an issue that CRM has after an upgrade (or any other potential times where you have changed the original server URL, and/or port number).

CRM fails to update its internal record for the ‘expected’ root domain for accessing the server.

 

So if you install CRM 3.0 on port 2444, it will record http://servername:2444 as the expected base URL.

 

If you then perform any type of querying through the APIs, you must specify that URL as the base URL…..

Now – if you upgrade to CRM 4.0, and your port changes, or you decide to move your instance to a different port – things will break.

 

If you run this:

Use [mscrm_config]

Select nvarcharcolumn from deploymentproperties where columnname = ‘ADSdkRootDomain’

Select nvarcharcolumn from deploymentproperties where columnname = ‘ADWebApplicationRootDomain’

 

You’ll get 2 rows, which will show you http://servername:2444 – even though, your server is now running on http://servername:5555

 

This will, in particular, cause an issue with the CRM 4.0 data migration manager – which will require that you use the base url to tell it where CRM is – you’ll be entering in the 5555 URL, but it will keep throwing errors back at you to the likes of “manager cannot connect to the Microsoft CRM server”.  As soon as you update the records, it will work fine:

 

USE MSCRM_CONFIG

Update DeploymentProperties SET NVarCharColumn = ‘servername:5555‘ WHERE ColumnName = ‘AsyncSdkRootDomain’

Update DeploymentProperties SET NvarCharColumn = ‘servername:5555’ WHERE ColumnName = ‘ADSdkRootDomain’

Update DeploymentProperties SET NvarCharColumn = ‘servername:5555’ WHERE ColumnName = ‘ADWebApplicationRootDomain’