ADXStudio Portal and Dynamics 365 SDK v8.2 are not compatible.

If you are attempting to use ADXStudio Portal and Dynamics 365 SDK v8.2, after entering the Dynamics CRM Organization Service URL during the setup of ADXPortal V7 and Dynamics 365, the following error will appear.

The Organization Service URL is invalid. Metadata contains a reference that cannot be resolved: ‘https://[organization name].api.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl=wsdl0’. There is an error in XML document (1, 1298). The maximum nametable character count quota (16384) has been exceeded while reading XML data. The nametable is a data structure used to store strings encountered during XML processing – long XML documents with non-repeating element names, attribute names and attribute values may trigger this quota. This quota may be increased by changing the MaxNameTableCharCount property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 1298.

This appears because ADXStudio Portal and Dynamics 365 SDK v8.2 are not compatible.

This error can be solved by replacing both the Microsoft.Xrm.Sdk.dll and the Microsoft.Crm.Sdk.Proxy.dll with the versions from the v8.1 SDK.

Here are the steps for resolution:

1. Download and Install the Dynamics 365 SDK. To get  the latest SDK, login to Dynamics 365, to Settings > Customization > Developer Resources  and open the Download SDK link.

2. Browse to the SDK folder and copy Xrm.Sdk.dll and the Microsoft.Crm.Sdk.Proxy.dll

3. Paste (and replace) the files in Step 2 to the MasterPortal The default directory for ADXStudio install is: C:\Program Files (x86)\Adxstudio\XrmPortals\[ADXPortalVersion]\Samples\MasterPortal but it may be different for you.

4. Next we need to update the config file and add the following dependent assembly reference.

<dependentAssembly>

<assemblyIdentity name=”Microsoft.Xrm.Sdk” publicKeyToken=”31bf3856ad364e35″ culture=”neutral”/>

<bindingRedirect oldVersion=”0.0.0.0-8.0.0.0″ newVersion=”8.0.0.0″/>

</dependentAssembly>

<dependentAssembly>

 <assemblyIdentity name=”Microsoft.Crm.Sdk.Proxy” publicKeyToken=”31bf3856ad364e35″ culture=”neutral”/>

<bindingRedirect oldVersion=”0.0.0.0-8.0.0.0″ newVersion=”8.0.0.0″/>

</dependentAssembly>

5. Save the Web.config file

Open the ADXStudio Portal setup and the connection will work now. There might be however some unknown issues with the ADXStudio.

If other errors still appear, or for more information on this issue, please refer to the ADX Studio Portal blog site or contact us via the web.