We use web services to establish a connection to your Dynamics CRM environment. If your web address settings aren't configured properly in CRM, we may receive this error:
“Metadata contains a reference that cannot be resolved: https:///2011/XrmServices/Organization.svc”
This is due to a misconfiguration of your CRM's web address or IIS settings. This could be caused by one of the two common issues below:
- The most common cause we see is an incorrect value on the CRM’s Organization Web Service in the CRM Deployment Manager. You can quickly tell if this is the case by looking at the URL returned in the error message (like in the example above). If the CRM server is not a valid externally resolvable address, and shows just the name of your CRM server, for example, this indicates an incorrect value for the Organization web service address. To fix this, log onto the CRM server as a Deployment Administrator and open the CRM Deployment Manager. In the Deployment Manager, right-click "Microsoft Dynamics CRM" and click on Properties. Then click the Web Address tab. Verify that the value in the Organization Web Service address is one that will be externally resolvable, such as mydomain.com, or crm.mydomain.com, or mydomain.com:444. It should not contain the internal server name of your CRM server.
- Multiple bindings on the CRM website, such as both an HTTP (port 80) binding, and a HTTPS (port 443) binding. In Microsoft Dynamics CRM, Microsoft only supports a single binding for the HTTP protocol. According to Microsoft: “The Web site should have a single binding. Multiple IIS bindings, such as a Web site with an HTTPS and an HTTP binding or two HTTPS or two HTTP bindings, are not supported for running Microsoft Dynamics CRM.” To resolve this, remove the extra bindings. On your CRM server, open IIS and select the CRM website. Click on the “Bindings” link on the right to edit the bindings. If you plan on using HTTPS for connectivity to your CRM, and there is also an HTTP binding, remove the HTTP binding.
If you're using SSL (recommended), self-signed certificates are not supported. HTTPS connections must be made with certificates issued by a Trusted Certificate Authority.