Issue in Excel Add in for D365 (ClientAuthError)

(0) Share

Report

Posted on by murtuzahasmi

Hi,

Our users are suddenly facing the below issue when trying to use the Excel add in for D365 , when using to upload Journal lines.

The ADFS is working fine when trying to access the normal D365 platform , but issue persists only which using Excel Addin integration.

Appreciate any help.

I have the same question (0)

All responses (23)

Answers (1)

Simba Chitsiku 12 on at

Like (0)

Report

i also started having this issue since Saturday 15 July. did your issue also start around the same time.

Was this reply helpful? Yes No
murtuzahasmi 55 on at

Like (0)

Report

I think around the same time. Was working fine before it.

Was this reply helpful? Yes No
Justin T 5 on at

Like (0)

Report

Our users have also started experiencing this same issue. Last confirmed successful attempt was July 4th and this issue was reported from July 14th.

Was this reply helpful? Yes No
Suggested answer

Muratvzr 743 on at

Like (0)

Report

New platform update needs some tweak on adfs and local agent. Here is the steps I did earlier after PU 50

Just upgarde local agent and set office365AdfsCompatibility true

docs.microsoft.com/.../onprem-adfscompatibility

After this you have to go to adfs server and run this

.\Test-ADFSConfiguration.ps1 -ConfigurationJsonFilePath "\\Fileserver\agent\wp\EN10\StandaloneSetup-746342\config.json"

based on your path and config file This script ll tell you if your adfs has problem.

I hope this ll solve your problem.

Was this reply helpful? Yes No
Verified answer

Muratvzr 743 on at

Like (2)

Report

My last reply was not correct, I found the correct solution.

This happens when your ADFS server is configured on Windows Server 2016 you need to upgrade server Windows Server 2019 because ADFS 2016 is deprecated and re publish adfs application.

I can manage to solve my problem.

Was this reply helpful? Yes No
murtuzahasmi 55 on at

Like (0)

Report

Yes, the issue is with Windows Server 2016 support ending and Microsoft no longer supporting Office ADFS integrations for ADFS setup on 2016.

Upgrading the ADFS server to 2019 and further upgrading the ADFS helped solve the issue.

Was this reply helpful? Yes No
Munyah 22 on at

Like (0)

Report

Thanks. Any pointers on how you did the upgrade? I tried an in-place upgrade as per Microsoft's recommendations and it kept failing. Did you build a completely new ADFS server and how do you go about republishing of the upgraded ADFS.

Was this reply helpful? Yes No
murtuzahasmi 55 on at

Like (1)

Report

You will create a new ADFS server with Windows 2019 and setup ADFS. Once activated, the old ADFS will be deactivated.

Was this reply helpful? Yes No
Suggested answer

Muratvzr 743 on at

Like (0)

Report

ADFS is not available for upgrade, You have to remove ADFS role on the server and add this role again then

Then Setup Adfs with this link

docs.microsoft.com/.../setup-deploy-on-premises-pu41

Once you done this the system gives you an error to your client id is not match on the adfs server cause of you create a new application group and the client id are different. You can change the setting on the lcs and re-deploy your envoirements.

Or you can change ADFS client ids

Microsoft Dynamics 365 for Operations On-premises - Native application

Microsoft Dynamics 365 for Operations On-premises - Financial Reporting - Native application

and change the relying part identification

Microsoft Dynamics 365 for Operations On-premises - Web application

Then re-start all servers and node.

I hope this ll help

Was this reply helpful? Yes No
Suggested answer

Munyah 22 on at

Like (0)

Report

Thanks, Murat. This answers my question.

Was this reply helpful? Yes No