Metadata contains a reference that cannot be resolved

Have a client using Microsoft Dynamics CRM 2011 Online, and I was trying to connect using Plugin Registration Tool from SDK (v5.0.16) but received error: Metadata contains a reference that cannot be resolved. Came home from office and tested it at home and it worked fine. I immediately realised this has to be proxy server configuration that caused the problem.

So, quick search on the web and found the following article:
http://xrmbits.com/plugin-registration-tool-error-metadata-contains-a-reference-that-cannot-be-resolved/

Essentially, we can use app.config file to specify the proxy settings. Example provided in the article above:






  
    
  



However, it didnt work for me. Then, I found the following: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2397357-fix-it-so-that-net-apps-can-access-http-thru-auth

Then updated the config file to the following


 
 


Hope this post helps someone out there.

Comments

Post a Comment

Popular posts from this blog

Error when defaulting field value using paramaters on form

Seems to be a bug in CRM 2013 Online RU1 that generic error occurs when defaulting a lookup field value using parameters on form. I had the following code:        var parameters = {};              parameters["new_customid"] = "621E9F4C-AD5C-E311-84F4-D89D67768C0C";              parameters["new_customidname"] = "Record Name";        parameters["new_customidtype"] = "new_customentity";        Xrm.Utility.openEntityForm("new_anotherentity", null, parameters); to pre-populate the 'new_customid' lookup field but generic error occurred. Searched on the web for a bit and found Form Query String Parameter Tool, and noticed that the last parameter ["new_customidtype"] is not required. However, CRM SDK states that this last parameter is required. Nonetheless, removed the last parameter and it works now.
Read more

Request not supported new_xxx when calling Custom Action via WebApi

Image
Using CRM 2016 Online, you can create custom Action to execute custom business logic to meet your specific business requirements leveraging the workflow-like configuration window to define the business logic rather having it written in the code. The custom Action can be called via CRM WebApi, and I encountered the following error whilst working on one of the projects. 'Request not supported new_xxx' Whilst there could be different causes to the error, one that occurred in my case is because the Unique Name has been changed after it was created. The initial name was too long, hence, shortened afterwards. However, the new name is not re-generated in the API metadata. Rather than re-creating the custom API, you can find the original name before it was updated by inspecting the API metadata which you can view at the following Url. https://[organization uri]/api/data/v8.0/$metadata   Simply download the file and open in a text editor, you can search for the custom Act...
Read more

CRM 4: Cannot login - 'Invalid Action', key has expired.

Just started our development environment and added a new organisation. When I start CRM on web client, an error message displayed 'Invalid Action'. Checked the Event Log and found the following error message: Event Type: Error Event Source: MSCRMKeyGenerator Event Category: None Event ID: 18949 Date: 12/12/2008 Time: 3:50:28 PM User: N/A Computer: DEVSERVER Description:Current active key (KeyType : CrmWRPCTokenKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:003e7d3c-72ac-dd11-a929-0003ffce439d, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:11/07/2008 02:17:34, ExpiresOn:12/10/2008 02:17:34, CreatedOn:11/07/2008 02:17:34, CreatedBy:NT AUTHORITY\NETWORK SERVICE. Key Setting : For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp . Thanks to the following post, it solved my problem instantly. http://www.henrycordes.nl/po...
Read more