web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Dual write setup Apply solution error

(1) ShareShare
ReportReport
Posted on by 131

Hi,

We encountered with the error on the dual write page, when we click on “We are trying to refresh UAT database from PROD, database refresh is successful, while doing setup for Dual write in UAT environment after refresh, we are facing below error when we click on “Apply solution” after doing the Reset link:

Steps followed are as below:
Step 1: Stop all table maps.
Step 2: On Reset link, select Current Database Environment, Acknowledge reset and force reset, click on legal entity and then completing the reset process.
Step 3: Click on “Apply solution” and got the error:
[Unknown] Failed to get solutions containing entity maps. - Type=Microsoft.PowerPlatform.Dataverse.Client.Utils.DataverseConnectionException, Msg=Failed to connect to Dataverse(Type=System.AggregateException, Msg=One or more errors occurred. (Exception - Fault While initializing client - RefreshInstanceDetails))

PU version for UAT and PROD: Update57 (7.0.6861.53)

Can you help us to rectify this issue.

Thankyou,

AyuSri.

I have the same question (0)
  • vicky1234 Profile Picture
    66 on at
    RE: Dual write setup Apply solution error

    Even I am facing same issue after the recent update .

    Did you find any solution for this ?

  • SH-30040526-0 Profile Picture
    14 on at
    Dual write setup Apply solution error
    have you resolved this issue?
  • Raj Borad Profile Picture
    1,373 on at
    Dual write setup Apply solution error
    Hi,
     
    I think the error occurs because of the Dataverse connection metadata is stale or mismatched after a UAT refresh from PROD. The error `Fault While initializing client - RefreshInstanceDetails` suggests the dual-write configuration still points to the original PROD Dataverse URL/token.
     
    Try below things:
    1. In UAT, go to System Administration > Dual-write > Link to Dataverse, and relink it to the correct UAT Dataverse instance.
    2. Ensure UAT has proper Dataverse application user and permissions (in Azure AD and Power Platform).
    3. Clear any cached data in Dual-write by restarting the Dual-write orchestration service.
     
    After relinking, retry “Apply solution.” Always avoid using PROD-linked Dual-write settings post refresh. Validate app registration and Dataverse environment mappings. 
     
    Is your UAT Dataverse environment active and accessible independently?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 683 Super User 2025 Season 2

#2
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 620

#3
Martin Dráb Profile Picture

Martin Dráb 563 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans