Metadata contains a reference that cannot be resolved error Alternately

(0) Share

Report

Posted on by sahara

645

I get the problem above when I run a job which tries to connect to my organizarion, the problem is that when I run my job suddently I get that error and after I wait fot five minutes it works fine, it happens with another organization of my, so I can understand from it that the problem is not the organization, maybe in my proxy or my system configuration... I don't know.. can I get some ideas why does the error jump after a "correct" run... I mean the job runs and if I try to run it again after a second I get this error.
thamns

*This post is locked for comments

I have the same question (0)

All responses (1)

Answers (0)

David Jennaway 14,065 on at

Like (0)

Report

RE: Metadata contains a reference that cannot be resolved error Alternately

Is this CRM OnPremise or Online ? If it's Online, then the problem is likely to be somewhere in your network configuration (client or firewalls / proxy). If it's OnPremise, then it could still be network, or maybe the CRM server. I'd enable tracing to see if there are any CRM server errors, but my suspicion is that this will lie somewhere in the network or authentication. If you use claims authentication, then also check if there are any errors on the ADFS server

Was this reply helpful? Yes No