IFD on Windows Server 2008 R2 problem with plugin registration

A customers system I was working on today has just been reconfigured to and IFD setup. The server is a Windows Server 2008 R2 and I had made sure that it worked on port 80 with NTLM/AD internally. However, when I tried to connect the plugin registration wizard in the normal manner, it just gave me an error:

“Request IP Address has different address family from network address.”

I found and interesting thread on Egghead café where some guys had run in to the same problem.
http://www.eggheadcafe.com/software/aspnet/31655329/-crm-4-on-2008-server–ipv6-related-problem.aspx

So I did as they suggested, added the servername to the hosts-file to the IP 127.0.0.1. If you don’t know what this means, it works as a local DNS. The IP 127.0.0.1 is assigned to always be the local computer and “localhost” is usually directed to this adress. You can try by browsing to it if you havn’t tried.

The hosts file can be found in C:WindowsSystem32Driversetchosts. There are usually an entry or two in there so you can usually figure it out, the syntax is simple:

127.0.0.1 servername

If you tried pinging the servername before doing this, you would get the IP v6 address, after doing this, you will get an answer from 127.0.0.1 and after confirming this, you should have no problems getting it up and running.

Gustaf Westerlund
CEO, Chief Architect and co-Founder at CRM-konsulterna AB

www.crmkonsulterna.se

Could not find GUID for server…

Interesting error today.

All of a sudden our development server stopped working. We got the following error in CRM:
Microsoft CRM Error Report:

Error Details:


Could not find GUID for server: CRMSERVER$


Full Stack:


[ActiveDirectoryObjectNotFoundException: The local computer is not joined to a domain or the domain cannot be contacted.]


at System.DirectoryServices.ActiveDirectory.Domain.GetComputerDomain()


at Microsoft.Crm.BusinessEntities.SecurityUtils.GetGuidFromServerName(String serverName)…
 
It seems that it was caused by the fact the the domain servers DNS was down. I have read of other causes for the same error, but make sure that the DNS service of the domain server is up and running.
 
Gustaf Westerlund
Microsoft Dynamics CRM Chief Architect

Logica
www.logica.com