Stay up-to-date with hotfixes and new product releases by subscribing to the RSS feed.
- The Layer2 ADO.Net Providers have been updated to the version 220.127.116.11.
- The error "Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information." that prevented the connection-string validation while using the DynamicsCrmOnline authentication has been fixed.
- If after installing the Layer2 ADO.Net Providers v18.104.22.168 you get the error "The URL 'https://yourSite.crm4.dynamics.com/XRMServices/2011/OrganizationData.svc/' does not refer to a valid OData-service." while validating the connection-string
using the OAuth2NoPopup_DynamicsCrmOnline authentication, it's very likely that the SchUseStrongCrypto property must be enabled in the Windows Registry to use the TLS 1.0, 1.1 & 1.2 as default protocols.
Please download, extract and double click the following package BDLC-DynamicsCrmOnlineAuth-SchUseStrongCrypto.zip to enable the SchUseStrongCrypto property in your Windows Registry.
If you prefer to add the Registry Keys manually please follow the instructions on the following page under section B1): _Enable_SSL_Protocols_for_your_Integrations_-_TLS_1.1_and_TLS_1.2
The OAuth2NoPopup_DynamicsCrmOnline authentication method must be specified in the connection-string as shown: Url=https://myDomain.crm4.dynamics.com/XRMServices/2011/OrganizationData.svc/; Collection=myCollectionName;Authentication=OAuth2NoPopup_DynamicsCrmOnline;User=myUser;Password=myPass;