Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
While connecting through Dynamics 365 Customer Engagement through a web application we were getting OrganizationServiceProxy value as null.
There was nothing out of ordinary in the authentication call
var connectionString = ConfigurationManager.AppSettings["CRMConnectionString"];
var conn = new CrmServiceClient(connectionString);
value of conn.OrganizationServiceProxy was null and there was no specific exception thrown by the code.
While checking connection object only exception we saw was for LastCrmError object
LastCrmError “Unable to Login to Dynamics CRMOrganizationServiceProxy is null”
To resolve the issue we tried to change the authentication code to
OrganizationServiceProxy proxy = new OrganizationServiceProxy(serviceUri, null, credentials, null);
and got exception
Metadata contains a reference that cannot be resolved: ‘https://***.api.crm5.dynamics.com/XRMServices/2011/Organization.svc?wsdl&sdkversion=9
While hunting for possible cause we came across Microsoft blog post stating that they have changed the connectivity to utilize TLS 1.2. (Default version used by .Net framework is SSL3 | TLS).
To enforce TLS 1.2 we included
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
just before connection request being sent to CRM. Tesolved issue in both authentication methods.
The post Issue while authenticating with CRM Organization Service from Web App (July 2017 Update) appeared first on Abhinav Ranjan.
Business Applications communities