Dual-write initial sync fails - "Server returned non-success HTTP response"

(0) Share

Report

Posted on by Phil Matthews

Hi,

We're getting a fairly generic error message when instigating Dual-write initial syncs on a number of maps:

Executed leg:From Dynamics 365 for Finance and Operations Customer groups to Dynamics 365 for Sales msdyn_customergroups - GB1
 with exported records count: 0, ImportRecordsErrorCount: 0, ImportRecordsInsertedCount: 0 and ImportRecordsUpdatedCount: 0 
ErrorsDetails:
Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=FinOps export encountered an error.(Type=Microsoft.PowerApps.CoreFramework.Communication.Http.NonSuccessHttpResponseException, StatusCode=BadRequest, Msg=Server returned non-success HTTP response). ExportErrors: (1)
Record Id: , ErrorMessage: Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=FinOps export encountered an error.(Type=Microsoft.PowerApps.CoreFramework.Communication.Http.NonSuccessHttpResponseException, StatusCode=BadRequest, Msg=Server returned non-success HTTP response). ImportErrors (0)

We've started with all legal entities enabled, and DMF shows that an export package is being created for DAT (with no records), then every single other legal entity fails with the above message and does not create the export package. Execution history for the job doesn't show any errors recorded.

All health checks in Dual-write pass.
These are standard OOB Dual-write maps.
The entity data in Finance can be read using OData calls in a browser
Live sync seems to work fine if the map is just started without an initial sync.
This is a Tier 2 environment running version 10.0.44.
No errors logged against the app registrations.
Have tried resetting the link, truncate and refresh entities.

Can anyone suggest further troubleshooting steps please? It's logged with Microsoft, but they're taking their time to respond since it's a non production environment.

Thanks in advance.

Categories:

Power Platform integration

I have the same question (0)

All responses (7)

Answers (1)

PD-17062034-0 6 on at

Like (2)

Report

We have exactly the same problem for TST12 and UAT environments running on version 10.0.44.

It worked last week and suddenly stopped after 10.0.44 update, so the only answer is Microsoft ticket.

I just reported it, so I should know something more in 2-3 working days.

Was this reply helpful? Yes No
Komi Siabi 13,109 Most Valuable Professional on at

Like (0)

Report

Have you also checked the FO related solutions on Dataverse to see if there are update avail? If yes, update them and retry.

Was this reply helpful? Yes No
Phil Matthews 98 on at

Like (2)

Report

All solutions are up to date.

Just to add extra information to this, we have now narrowed down the scope of the problem.

During the initial sync from FO to CE, an export package is only created for the first legal entity which is attempted to be synced and all others fail with the non success HTTP response. The Legal Entities are synced in the order that they are shown in the Legal Entities tab within Dual-write.

For example if DAT, LE1, LE2, and LE3 are the legal entities in order, an export package for DAT will be created and creation of packages for LE1-3 will all fail. If we then delete the DAT legal entity from the config, save, and re-add it, it is then added to the end of the list (and so is synced last). If we then repeat the initial sync under these conditions, LE1 will succeed, LE2, LE3, and DAT will fail.

This is almost certainly, as stated below, a bug with Dual-write in 10.0.44.

Was this reply helpful? Yes No
Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

Hi @Phil Matthews @PD-17062034-0

I'm experiencing the same issue this evening, have either of you had any response from MS or found a workaround?

Thanks,

Anthony

Was this reply helpful? Yes No
Phil Matthews 98 on at

Like (1)

Report

@Anthony Blake Not yet, I'm afraid. I will make sure to update here if/when we get a resolution. In the interim we've had to recreate the environment on 10.0.43. Luckily not a production environment yet!

Was this reply helpful? Yes No
Phil Matthews 98 on at

Like (0)

Report

Further to this (and still waiting on Microsoft support...), I have found that the problem is now resolved in Tier 2 environments by deploying the latest hotfixes (although Microsoft cannot state which one resolves the issue and none of them outwardly have anything to do with the issue).

Tier 1 however, the issue persists even with the same hotfixes deployed, and additionally an LCS deployed 10.0.43 Tier 1 (which worked perfectly on 10.0.43) starts to present this error when updated to 10.0.44.

Was this reply helpful? Yes No
Verified answer

Phil Matthews 98 on at

Like (2)

Report
Ok, I have a fix! This can be disabled by enabling a flight in SSMS:

DECLARE @flightName NVARCHAR(100) = 'DMFDisableThrowErrorWhenDataProjectInManifestExistsAsExportProject'; IF NOT EXISTS (SELECT TOP 1 1 FROM SysFlighting WHERE flightName = @flightName) INSERT INTO SYSFLIGHTING(FLIGHTNAME,ENABLED, FLIGHTSERVICEID,PARTITION) SELECT @flightName, 1, 12719367,RECID FROM DBO.[PARTITIONS]; ELSE UPDATE SysFlighting SET enabled = 1, flightServiceId = 12719367 WHERE flightName = @flightName;

Then restart IIS.

This obviously is only viable for Tier 1 environments, but it seems like Microsoft have bulk updated Tier 2 environments and will fix properly in a future hotfix or something like that.

3 people found this reply helpful.

Was this reply helpful? Yes No