Finance | Project Operations, Human Resources, ...

How to diagnose failed Data Management Exports to BYOD Server?

(0) Share

Report

Posted on by Ian Waring

436

I have a very simple export job. It is to do a full export of entity "Open Sales Price Journal Lines" to our connected BYOD SQLserver instance. Every time I try the export, I get "Export execution failed for entity Open sales price journal lines: Export failed while copying data from staging to target:". Opening up the Infolog, I get:

Infolog for job 'Export process: Brian SalesOpenSalesPriceJournalLine' (5642436926)

Infolog for task Move to staging from target: Open sales price journal lines (followed by job name)

BYOD export failed on final attempt
Could not export data from target to destination

I can verify the connection as okay. I can access the database on the BYOD server using SQLserver Management Studio. However, there is zero clue as to why the transfer is failing every attempt. Other exports are running fine.

Any ideas of any other place where Dynamics 365 Finance leaves any clues?

Categories:

Data Integration

All responses (9)

Answers (0)

Suggested answer

Alireza Eshaghzadeh 10,829 Moderator on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

Do you use the V2 entity? Can the entity be exported to Excel?

Can you try by creating a new data project.

Can you share the error message?
nunomaia 10,682 Moderator on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

Did you tried to drop PK of table in SQL ? Once we had duplicates keys of entity that generated a similar error in BYOD
Ian Waring 436 on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

I also deleted the previous version of the table on the BYOD server but the error frustratingly persists. :-(
Ian Waring 436 on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

I'm skipping staging. The first error it appears to hit is: "Package Execution Failed for Entity Store". Still plugging away...
Suggested answer

Alireza Eshaghzadeh 10,829 Moderator on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

Hi Ian,

I addition to Nuno feedback, please try to activate "Skip staging" once you export entity "Open sales price journal lines V2" to AzureSQL DB.
nunomaia 10,682 Moderator on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

Confirm you that data entity to don't generate a unique key violation using,

Just try this :

- Publish data entity to create SQL table

- Drop PK from SQL Table.

- Export Data Entity
Ian Waring 436 on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

Done that. Also deleted the old version of the table on in the BYOD database. Same error.

Probably need to wait for one of our Azure admins to see if there's any clue on their side.
nunomaia 10,682 Moderator on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

Try to publish again data entity to BYOD. Before we moved to datalake, we had to republish from time to time some data entities.
Ian Waring 436 on at

Like (0)

Report

RE: How to diagnose failed Data Management Exports to BYOD Server?

PS: I've remapped the entity fields, removed field ATTRIBUTEBASEDPRICINGID which was disabled by config ket PDSPotency and PRODUCTVERSIONID as disabled by config key EcoResProductVersion. No effect, same error.