NOTE: This article pertains to On-Premise environments.
When registering for the ClickDimensions solution, you may see one of the following error messages:
"Metadata contains a reference that cannot be resolved: 'https:///2011/XrmServices/Organization.svc'"
"Failed to connect to Dynamics/MS CRM. Please check your input and try again. Error: Data[0] = "The provided uri did not return any Service Endpoints! {0}" Data[1] = "")
This is due to a misconfiguration of your Dynamics environment's IFD (Internet-Facing Deployment) or external connectivity for your environment. When registering for ClickDimensions, our system performs a connectivity check to ensure that it can communicate with your environment. It is always recommended to try attempting to access and login from outside of your internal network to help confirm if this is an issue with the IFD setup or the external connectivity of your Dynamics environment.
There are two common causes for these errors:
- Multiple bindings on the Dynamics website, such as both an HTTP (port 80) binding, and a HTTPS (port 443) binding. In Microsoft Dynamics CRM 2011 and later versions, 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, you must remove the extra binding(s). On the Dynamics web server, open IIS and select the Dynamics website. Click on the "Bindings" link on the right to edit the bindings. If you plan on using HTTPS for connectivity to your Dynamics environment, and there is also an HTTP binding, remove the HTTP binding.
- The other common cause is having an incorrect value set for Dynamics' Organization Web Service in the Deployment Manager. (You can quickly tell if this is the case by looking at the URL returned in the error message. If the Dynamics server is not an externally-resolvable address, and shows just the name of your Dynamics server, for example, this indicates an incorrect value for the Organization web service address.) To correct this, log onto the Dynamics server as a Deployment Administrator and open the Deployment Manager. (Note: A "Deployment Administrator" is not the same thing as a user with the System Administrator role.) In the Deployment Manager, right-click "Microsoft Dynamics CRM" and click on Properties. In the dialog that opens, 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 Dynamics server.)
NOTE: Self-signed certificates are not supported. HTTPS connections must be made with certificates issued by a Trusted Certificate Authority.