CRM 2016 integration with SharePoint 2016 On Premise (401) Unauthorized Error

-
We spent a lot of time while we encountered  the below exception when we were integrating CRM with SharePoint.

Exception: System.Net.WebException: The remote server returned an error: (401) Unauthorized.

Environment details:

CRM 2016 on-premise with Claims authentication enabled.
SharePoint Server On-premise with Claims authentication enabled.
User Account using to set up is Admin on both the CRM and Sharepoint servers.

Reason & Fix:

Fix suggested in the following MSDN Forum worked for us. (https://social.microsoft.com/Forums/en-US/9d3ebcf2-daf4-4564-a992-67a038aef9c5/crm-and-sharepoint-integration-401-unauthorized-when-setting-trusted-security-token-issuer?forum=crm)

It seems there is a known issue/bug with CRM 2016 that doesn’t allow this to work if you try using https in the MetadataEndPoint.

To get this working, you will have to temporarily do the following items before running the SharePoint Power Shell command.

Note : Make sure you note all the existing settings before executing below steps which helps you to roll back, if something goes wrong.

Steps:

Open the CRM Deployment Manager tool
Disable CRM IFD
Disable CRM Claims Configuration
Open the IIS and remove the https binding on the CRM Web site and add back the http binding for the CRM Web site.
Run CRM Deployment Manager and change the properties of the deployment for the Web Address to use http instead of https.
Run an IISReset on the CRM Server to ensure this is now accessible via http.
Run the SharePoint PowerShell commands (you should be able to access the MetadataEndpoint using http vs. https now if you put it in the browser (and it should prompt to download a .json file).
Once the SharePoint commands are finished running, you need to reverse the changes above in CRM to re-enable IFD.
Change the CRM Web Address to use https in the CRM Deployment Properties.
Remove the http binding on the CRM Web site and add back the https binding, selecting the correct SSL Certificate.
Run the Configure CRM Claims in the CRM Deployment Manager.  (keep the existing settings)
Run the Configure IFD in the CRM Deployment Manager (keep existing settings).
Run an IISReset on the CRM Server.

I would highly recommend you Refer MSDN article  which details integrating SharePoint on-premise with CRM on-premise.

Comments

Post a Comment

Popular posts from this blog

How to Query Microsoft Dataverse Data using SQL from Power BI or SSMS

-
Image
Microsoft in recent months made available a much requested feature by many with the additional way to access read-only data in Microsoft Dataverse. The TDS endpoint for Microsoft Dataverse allows read-only access to Dataverse for reporting and analytics requirements. The Tabular Data Stream (TDS) Protocol endpoint functionality is managed by an administrator with access to the Admin center. This feature becomes a game changer as many Microsoft customers who required this feature and often went down the root of the Data Export Service can now start exploring this capability Prerequisites: To get started using this feature, you will need to ensure that TDS endpoint is enabled as this is required to be able to use this feature via Power BI or SSMS. Sign into the Power Platform Admin Center :( https://admin.powerplatform.microsoft.com/environments ), and then select the appropriate sandbox environment. Note: Its always good practice to test new features in a Sandbox Environment Validate t
Read more

Users Unable to See Flow Button and run On Demand workflows in Dynamics 365 CE

-
Image
Overview. Dynamics 365 CE provides functionality to automate business processes in the background or on a click of a button requiring a user to initiate this automation. In this blog post the scenario is focused on an issue a user may experience while using dynamics 365 CE on automation which is initiated by a user looking to use an On Demand. This automation triggered by a user is called an on-demand workflow. Problem When a user goes into Dynamics 365,  they are unable to see or run a workflow/flow which may have been created. So how do you resolve this issue? Steps to Resolve System Settings 1.a) Login into the Power Platform Admin center ( https://admin.powerplatform.microsoft.com/environments ) and Select your Environment name > Settings  > Behavior . At this point validate that the " Show Power Automate on forms and in the site map " is toggled  1. b) Validate that the setting, you will need to navigate to Settings > Administration > System Settings >
Read more

How To Deploy Dynamics App For Outlook (On-Premise)

-
Purpose The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item Audience This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments. Pre-Requisites Dynamics 365 with IFD Configuration Dynamics 365 Update 8.2.2.112 (KB4046795) Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later Office 2016 *Recommended, Office 2013 *Compatible Supported browsers for Outlook on the web Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers: Internet Explorer 10, Internet Explorer 11, or Microsoft Edge The following configuration is supported: Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet. Protected Mode
Read more