Metadata contains a reference that cannot be resolved: 'https://adfs.hostname.com/adfs/services/trust/mex'.

(0) Share

Report

Posted on by Euclides Pelisco Jr

133

Having issue on connecting to my environment in my console app.

Metadata contains a reference that cannot be resolved: 'adfs.hostname.com/.../mex'.

Anyone knows how to resolve this? Thanks.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

David Jennaway 14,065 on at

Like (0)

Report
The first things I'd check are:

Can you browse to the metadata url that you get in the error message ? If not, the CRM ADFS configuration may be incorrect, or you may have firewall or other connectivity issues

Check the event log on the ADFS server (ADFS creates a separate log rather than using the Application log) to see if it has any useful errors

It's also worth checking if you can connect programmatically using other tools. I'd suggest using XrmToolbox. If you can connect, it indicates an issue in your code, whereas if you can't, then it's more likely to be an ADFS or CRM ADFS configuration issue

Was this reply helpful? Yes No
Euclides Pelisco Jr 133 on at

Like (0)

Report

Hi David. Thank you for the tips.

I tried to connect using xrmtoolbox and it worked.

I used this code to establish connection. This code works to my trial environment. But when I tried to connect to our environment with adfs setup, connection error pops up. Do you have any idea what I missed in the code connecting to environment with adfs setup?

Was this reply helpful? Yes No
Suggested answer

Kokulan 18,054 on at

Like (0)

Report

Hi

For your credentials part, could you try with the following

var _credentials = new ClientCredentials();

_credentials.Windows.ClientCredential.Domain = "domainname";

_credentials.Windows.ClientCredential.UserName = "username";

_credentials.Windows.ClientCredential.Password = "pw";

And TLS12 setting is not necessary for CRM 2016.

Was this reply helpful? Yes No
Verified answer

Euclides Pelisco Jr 133 on at

Like (0)

Report

The issue is now fixed. According to some suggestions on my research.

I just tried to update .NET framework to 4.6 and Microsoft.CrmSdk.CoreAssemblies to 9.0.0.7

Was this reply helpful? Yes No
Euclides Pelisco Jr 133 on at

Like (2)

Report

Hi guys.

Thank you for taking time to check my inquiry.

The issue is now fixed. According to some suggestions on my research.

I just tried to update .NET framework to 4.6 and Microsoft.CrmSdk.CoreAssemblies to 9.0.0.7

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi, Can you tell me how you resolved this issue as I'm running into the same problem. Thanks.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

update to the new version of .net 9.0.0.7, in new update this problem has been solved,i suggest you to use xrm tool .

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for the response. I updated to 9.0.2.12, which is the latest version, but still getting the same error. Think I figured it out. The top level SSL certificate needs to be installed on our servers.

Was this reply helpful? Yes No