While setting up IFD, we had issues in enabling the claims for CRM 2011. After trying to enable claims for CRM 2011 through Microsoft Dynamics CRM 2011 Deployment Manager when we trid to browse the URL: https://XYZ.com/FederationMetadata/2007-06/FederationMetadata.xml we were getting one of the following errors:
– HTTP 503 Service Unavailable error.
– HTTP 404 Not Found error.
When “FederationMetadata/2007-06/FederationMetadata.xml” is requested through the browser CRM website, it has the rule that rewrites the URL to handlers/Federation Metadata.ashx. So when one gets such types of error then it means IIS URL Rewrite module is not rewriting the URL correctly.
The solution for this issue is to re install the IIS URL Rewrite.
If the reinstallation of IIS URL Rewrite does not resolve the issue. The Issue could be due to Reserved URL. To find the Reserved URL follow the below given steps.
a) Open Command Prompt.
b) Type the Command NETSH HTTP SHOW URLACL.
c) This command will show all the reserved URL’s.
d) If you get any reserved URL with error as given below.
Reserved URL : https://ABC:443/
Can’t lookup sid, Error: 1332
SDDL: D:(A;;GA;;;S-1-5-80-2246541699-21809830-3603976364-117610243- 975697593)
e) Then we have to delete each URL for which we get such type of error as given above using the below command. Please provide the full URL for which you get the error in the command Prompt.
netsh http delete urlacl url=https://ABC:443/
f) After that again run the command to check if the reserved URL is still having an error message through command NETSH HTTP SHOW URLACL.
g) Repeat the step (e) for each URL for which you are getting the error.
h) After deleting all the Reserved URL through the Command,do IIS RESET on CRM server.
i) Configure CLAIMS again using Deployment Manager on CRM 2011.
j) Now try to access the federation Url “FederationMetadata/2007-06/FederationMetadata.xml”again.
We have refereed the blog http://blogs.msdn.com/b/emeadcrmsupport/archive/2011/05/13/we-receive-http-errors-while-accessing-the-crm-federationmetadata-url.aspx to resolve the issue.
The above listed steps should resolve the issue.