Metadata contains a reference that cannot be resolved: ‘’ error in Dynamics 365

We would run into this issue while trying to connect to Dynamics 365 Version 9.0 from a client application.

It is because Customer Engagement Platform (version 9.0) only supports TLS 1.2.

More details here

How we can fix it à

We need to add the following line of code to our existing code

public static OrganizationServiceProxy GetOrganizationServiceProxy()
ClientCredentials clientCredentials = new ClientCredentials();

clientCredentials.UserName.UserName = "username";
clientCredentials.UserName.Password = "password";

// Set security protocol to TLS 1.2 for version 9.0 of Customer Engagement Platform
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

return new OrganizationServiceProxy(new Uri(""),
null, clientCredentials, null);

Helpful post

Hope it helps..

User does not have the privilege to act on behalf another user error while using impersonation in Web API in Dynamics 365.

We might receive below error while using impersonation in Web API call.

{\r\n  \”error\”:{\r\n    \”code\”:\”\”,\”message\”:\”User does not have the privilege to act on behalf another user.\”,\”innererror\”:{\r\n      \”message\”:\”User does not have the privilege to act on behalf another user.\”,\”type\”:

Impersonation in Web API

This error can occur in a scenario when User A is trying to impersonate User B, but user A doesn’t have “Act on Behalf of Another User” privilege.

Below article nicely explains it

Hope it helps..

Service Unavailable – HTTP Error 503 error while trying to login to Dynamics 365 Online.

While trying to login into Dynamics 365 Online, we got the below issue

It could be some issue related to ADFS ( Until it is corrected, the only solution is to wait for some time for the service to be up and running.

It was close to 90 minutes for us.

Hope it helps..

A security error has occurred. Make sure you are signed into Microsoft Dynamics CRM and try again in Click Dimensions.

We had this issue in past when we started getting below error in most of the entities of Click Dimensions.

The issue can occur if the password would have expired or changed for the Service Credentials account of Click Dimensions.

Go to Settings à ClickDimensions Settings à Service Credentials.

In our case it wasn’t changed but we were still getting the issue. The only way we were able to fix it was to specify a different account for the Service Credentials.

Hope it helps.

The remote server returned an error: (403) Forbidden while sending SMS from Click Dimension

We got the below while sending SMS from Click Dimension. We were using Bulk SMS as our SMS connector for Click Dimension.

When we opened the Text Messages record we figured out that we were getting “The remove serve returned an error (403) Forbidden.

This occurred because we had our credit with Bulk SMS already consumed.

The issue got fixed when bought the credits again with Bulk SMS.

Hope it helps.

How to – Convert Fetch XML to SQL in Dynamics 365


Recently we had a requirement to convert Fetch XML query of certain views to SQL. Basically, we wanted to validate it again the source DB from which we push the data inside Dynamics 365.

For this we can use the below managed solution,

The tool is built using Silverlight so will only work in IE.

The other tool is that we can use is one of the most useful plugins –  Fetch XML Builder of  XRM Tool Box.


Below video explains how to use them

And in case you’d feel like converting fetch xml to SQL we have

Hope it helps..

%d bloggers like this: