Dynamics 365 CRM Version 9.0 OnPrem Installation Experience

Microsoft Windows Server 2016 & SQL Server 2016 with Service Pack 2 are the primarily prerequisites to install and configure Dynamics 365 CRM Version 9.0. it should work fine if all prerequisites are met.

But if you want to try Dynamics 365 V9 with SQL Server 2017, then there will be an issue happened where no SSRS instance identifies at the time of SSRS connector installation. The similar case happens in upgrading CRM 2016 version to Dynamics 365 8.2 in SQL Server 2017. 

This issue revolves around SQL Server 2017 where SSRS 2017 is yet to be supported in Dynamics 365 Version 9.0 OnPrem.

In the meanwhile SQL Server 2016 SP2 SSRS could resolve the installation and configuration issue. 

Hopefully Dynamics 365 future service updates shall have the fixes for SQL Server 2017. 😊

Happy Dynamics 365 Journey!!

Waiting for a page to be retrieved from a CRM Server - Dynamics Outlook Connector - 8.2.2.137

There was some complains from business users in accessing their CRM Organization through MS Outlook Client. It was started happening after the installation of MS Outlook Connector 8.2.2.137.

This issue was resolved after following the instruction written in Microsoft Support link:

https://support.microsoft.com/en-hk/help/4049314/microsoft-dynamics-365-for-outlook-is-unable-to-render-webpages-after

Hopefully It will help for other to resolve the similar issue.



Cheers,

Outlook Connectivity Issue with Microsoft Dynamics 365 Server

One of our customer had experienced an issue in Microsoft Outlook while connecting for Microsoft Dynamics 365.

Metadata contains a reference that cannot be resolved: 'https://orgname.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl&sdkversion=8.2'. at System.ServiceModel.Description.MetadataExchangeClient.MetadataRetriever.Retrieve(TimeoutHelper timeoutHelper)
at System.ServiceModel.Description.MetadataExchangeClient.ResolveNext(ResolveCallState resolveCallState)
at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(MetadataRetriever retriever)
at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(Uri address, MetadataExchangeClientMode mode)
at Microsoft.Xrm.Sdk.Client.ServiceMetadataUtility.RetrieveServiceEndpointMetadata(Type contractType, Uri serviceUri, Boolean checkForSecondary)
at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1..ctor(Uri serviceUri, Boolean checkForSecondary)
at Microsoft.Xrm.Sdk.Client.OrganizationServiceConfiguration..ctor(Uri serviceUri, Boolean enableProxyTypes, Assembly assembly)
at Microsoft.Xrm.Sdk.Client.ServiceConfigurationFactory.CreateConfiguration[TService](Uri serviceUri, Boolean enableProxyTypes, Assembly assembly)
at Microsoft.Xrm.Sdk.Client.ServiceConfigurationFactory.CreateConfiguration[TService](Uri serviceUri)
at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.DiscoverAuthUsingServiceMetadata(Uri endPoint, Uri webEndPoint)
at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.GetAuthProviderForDeployment(Uri endPoint, Uri webEndPoint)
at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo`1.GetAuthenticatedProvider(OrganizationDetail orgDetail, Control parentWindow)
at Microsoft.Crm.Application.Outlook.Config.ServerForm.LoadDataToServerInfo()
at Microsoft.Crm.Application.Outlook.Config.ServerForm.<InitializeBackgroundWorkers>b__3(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) 

 
The issue was resolved after following the instructions mentioned on Microsoft Support link: https://support.microsoft.com/en-us/help/4073398/there-is-a-problem-communicating-with-the-microsoft-dynamics-365-serve

Hopefully It will help for other to resolve the similar issue.

Cheers,