Dynamics CRM IFD on Windows server 2012 R2 ADFS – CRM Addin for Outlook

Dynamics CRM IFD on Windows server 2012 R2 ADFS (aka ADFS 3.0) – CRM Addin for Outlook

Hearing questions on previous post I thought of checking CRM Outlook on the same VM. Luckily I didn’t nuke it right after the purpose so could get the CRM for Outlook Configuration Wizard spinning by starting Windows 7 VM, installing Office and CRM for Outlook.

Configuration wizard prompted for credentials, thrown an error after I entered credentials. Looking at config log it seemed like authentication failure. Here is snippet from configuration log:

07:50:38| Error| Error connecting to URL: https://crm.contoso.com:444/XRMServices/2011/Discovery.svc Exception: Microsoft.Crm.CrmException: Authentication failed
   at Microsoft.Crm.Outlook.ClientAuth.ClaimsBasedAuthProvider`1.AuthenticateClaims()
   at Microsoft.Crm.Outlook.ClientAuth.ClaimsBasedAuthProvider`1.SignIn()
   at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.SignIn(Uri endPoint, Credential credentials, AuthUIMode uiMode, IClientOrganizationContext context, Form parentWindow, Boolean retryOnError)
   at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo.DeploymentInfo.LoadOrganizations(AuthUIMode uiMode, Form parentWindow, Credential credentials)
   at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo.InternalLoadOrganizations(OrganizationDetailCollection orgs, AuthUIMode uiMode, Form parentWindow)

Above stack and exception from CRM doesn’t tell me the cause of failure, looking the ADFS event logs and debug tracing also left me clueless. Learnt from Fiddler trace that it’s a 503 Service Unavailable for the mex endpoint of ADFS, i.e. - https://sts.contoso.com/adfs/services/trust/mex. Browsed mex end point URL in IE to see 503 and again looked at ADFS event logs and debug trace but nothing relevant. Restarted ADFS service to see if there is something and I see it’s an error telling it couldn’t enable FS endpoints.

Event ID:      102
There was an error in enabling endpoints of Federation Service. Fix configuration errors using PowerShell cmdlets and restart the Federation Service.
Additional Data
Exception details:
System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted

Reason is clear and this VM being CRM server I know its CRM Sandbox service listening on 808 port, TechNet reference. This is where an ADFS configuration option comes handy. NetTcpPort is a setting available with ADFS tells ADFS to use a port other than 808, here is an article referring this setting. After setting my ADFS service to use port 809 using below PowerShell command and restarting ADFS service, mex endpoint could be browsed normally and so my CRM for Outlook configuration worked like a song.

Set-ADFSProperties –nettcpport 809


Hope this helps and Thank you!

Bhavesh Shastri


Comments (12)
  1. The warning is stating "ADFS Device Registration Service" and I doubt if it could be complete show-stopper for mobile devices. Needs to be investigated what ADFS Device Registration is needed for before making conclusion.

  2. Walter Pircali says:

    Thanks a log … saved my day (night as a matter of fact).


  3. mike says:

    Thanx like … well just plain thank you. Man, you just made my evening 😉

  4. Gyula says:

    Thank you so much. You saved my life… 🙂

  5. Anonymous says:

    Tutti sanno che ADFS viene usato…

  6. Patrick Mwangi says:

    You are the hero..thanks .

  7. Anonymous says:

    Configuring Outlook Client usually involved making sure the regular stuff was done i.e.:

    Adding the server url to trusted sites.
    Checking whether the machine time matches the…

  8. Anonymous says:

    Configuring Outlook Client usually involved making sure the regular stuff was done i

  9. Alex C. says:

    FYI, I read that running ADFS on a non-standard port will prevent you from working with mobile devices as noted in step 7 in this blog post:


  10. Apurv says:

    Thanks for this. 🙂

  11. Luise says:

    Thanks. You are a genius!!

  12. Devon Stern says:

    Thank you so much! I spent several hours trying to figure out why Outlook, Scribe, and other applications couldn’t connect to CRM. This did the trick. The weird thing is that ADFS was set to use port 1501 for the NetTcpPort and it was listening on that port, even though the error message mentioned port 808. Regardless, changing the NetTcpPort to 809 allowed them to reconnect. Saved my skin.

Comments are closed.

Skip to main content