CRM 4.0 - SQL Server Named Instance - Non-Default Port - Multi Tenancy RRS feed

  • Question

  • --Poor english below

    Hi all!

    Here is my environment: (Please note that I've tried to keep the info to a minimum and yes, this env. is strange! It is used for simultaneous development teams)

    I have:

    3 Windows 2003 Virtual Servers running on Virtual Server 2005. Same Microsoft Dynamics CRM 4.0 Deployment, multi tenancy configuration. Fresh Install. We will call these servers CRM01,CRM02 and CRM03 - (Useless Info...)

    1 Windows 2003 w/SQL Server 2005, running 4 instances. 
    Lets call them
    - SQL01 (default instance, running on default port  )
    This instance is used for another application.
    - SQL01\INSA (named instance, running on default port 4050 )
    This instance hosts the MSCRM_CONFIG database, and the ''Organization A'' database
    - SQL01\INSB (named instance, running on default port 4051 )
    This instance hosts the ''Organization B'' database
    - SQL01\INSC (named instance, running on default port 4052 )
    This instance hosts the ''Organization C'' database

    So I have installed CRM 4.0 on CRM01, created a new deployment and a new org. No problem. 
    I have installed CRM 4.0 on CRM02 and CRM03 and add joined the deployment.

    Now i want to create the two other organization

    In the Deployment Manager, I create a new organization: When its time the enter the SQL Server for that organization, I put "SQL01\INSB", Then I will end up with an error saying that the SQL Server could not be reached. 

    Note that I have not specifed the port number anywhere. 

    My workaround:

    I keep the Wizard open. I open the OBDC Data Source Administrator, create a new Data Source, specify, Server\Instance and Port number, Test Connection successfully.

    I go back to the Wizard in the Deployment Manager, and I works.

    So, now i need your help for two thing:

    1) Please explain me why it works.
    2) How do you specify which port to use in the Dynamics CRM 4.0 wizards for SQL Server named instances?

    I've read that "Microsoft supports named instances out of the box with Microsoft Dynamics CRM 4.0"... 



    Monday, October 20, 2008 7:41 PM


  • You can't specify the port of a SQL Server Named Instance during Microsoft Dynamics CRM 4.0 installation process. And you don't need to...

    If you cant connect to the SQL Server Named Instance, create the following key in the registry:

    in HKLM\Software\Microsoft\MSSQLServer\Client\ConnectTo

    Create the following: 

    Name : <SQLServerName>\<SQLServerInstanceName>
    Type : REG_SZ
    Value: DBMSSOCN,<SQLServerName>\<SQLServerInstanceName>,<PortNumber>


    Wednesday, November 5, 2008 1:22 PM