Access the answers to your technology questions today.
Subscribe Now
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
Subscribe Now
30-day free trial. Register in 60 seconds.
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Join the Community
by: feridunPosted on 2009-08-10 at 13:48:56ID: 25063918
Did you follow the instructions in the Implementation Guide (see www.microsoft.com/download s and search for CRM implementation) for installing CRM on a cluster? There is a step where you have to update the MSCRM_CONFIG database. This may have nothing to do with your problem but I thought it worth checking. I've copied the step below:
n' in' and ADsdkRootDomain values may be different. For example, if you installed the application-server role group on a server in an NLB cluster that is named crmcluster1 in the contoso domain but installed the platform-server role group on a different server in a different NLB cluster such as crmcluster2 in the same domain, the FQDN will be different for each of the ADWebApplicationRootDomain and ADSdkRootDomain values. 5.
Step 4: Update the configuration database to address the NLB cluster
You must manually update the configuration database by adding the fully qualified domain name (FQDN) cluster name. To do this, follow these steps.
Warning
Incorrectly modifying the configuration database can cause unexpected behavior in the Microsoft Dynamics CRM system, or cause it to stop working. We recommend that you back up the Microsoft Dynamics CRM system before you start these steps. For information about how to back up the Microsoft Dynamics CRM system, see the Operating and Maintaining Guide that is part of this document set.
Run the following update statements against the configuration (MSCRM_CONFIG) database:
" Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'ADWebApplicationRootDomai
" Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'ADsdkRootDomain'
For an Internet-facing deployment of Microsoft Dynamics CRM, run the following update statements in addition to the statements specified above:
" Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'IFDWebApplicationRootDoma
" Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'IFDsdkRootDomain'
Important
Depending on how you deployed the Microsoft Dynamics CRM Server role group or separate server role installation, and the configuration of each server in the NLB cluster, the ADWebApplicationRootDomain
For a full server role deployment, replace crmcluster.contoso.com with the FQDN of the cluster. If you are using a TCP port other then 80 (non-secure HTTP) or 443 (secure HTTP or SSL), you must specify the port number by appending the FQDN name with :5555, where 5555 is the port number, such as crmcluster.contoso.com:555