Otreva currently supports Internet Explorer 9 and higher. You should consider upgrading to get all intended functionality. ×
microsoft-dynamics-there-is-a-problem-communicating

Dynamics CRM There is a problem communicating with the Microsoft Dynamics CRM server.

in Blog

I installed Dynamics CRM 2011 on-premise the other day and tried connecting the Outlook CRM connector but kept running into the error message:

There is a problem communicating with the Microsoft Dynamics CRM server. The server might be unavailable. Try again later. If the problem persists, contact your system administrator.

I was always able to access the site through my web browser to the server’s IP address. But if I tried http://servername in my browser, I would have to enter my username and password 3 times and then get a 401.1 error.

If I tried http://servername I had the same error as if I tried http://192.xxx.xxx.xxx in the outlook connector. Little did I know that that would lead to my answer.

I tried multiple times going through this wizard with no luck.

http://rc.crm.dynamics.com/rc/2011/en-us/online/5.0/outlook-troubleshooting.aspx

Background on my install:

  • Dynamics 2011 On Premise
    • Originally was Roll Up 5 but I upgraded to 6 > 7 > 8
    • Updating didn’t change anything
  • My CRM Application Pool was running with a custom account and not network service.

 

Suggestions if you have this problem:

  1. Can you access the web service via http://servername ?
    1. If you get 401.1 error after entering your account info 3 times, continue on with this guide, you likely have a Kerebros authentication issue.
    2. If the above works for you, you likely have a different error than I and should stop here.
    3. Open IIS Manager on the CRM server,  and click expand next to your servername.
    4. Click Application Pools
      1. Are CRMAppPool and  CrmDeploymentServiceAppPool running as a domainuser or NetworkService?
      2. Mine were domainuser so I ran the following from an elevated command line:
        1. setspn –A HTTP/servername:5555 domainserviceusername_or_computername
        2. setspn –A HTTP/servername.company.com domainserviceusername_or_computername
        3. setspn -L Domainservice_account_name
      3. Finally I went into the CRM Deployment Manager on the CRM server and right clicked on Microsoft Dynamics CRM and click properties.
      4. I set all 4 addresses to exampledns.exampledomain.com:80
      5. Then when I went back to Outlook, I was set!

Here is what led me to the above solution.

Comments are closed.