You’re offline. This is a read only version of the page.
Announcements
97
We have a custom data entity that has been in place for several years that is incrementally pushed to our BYOD database every hour across all legal entities. Earlier this week, one of the legal entity jobs began failing due to a timeout. It is the first LE to execute. The remaining LEs ran to completion, but the first timed out after 1 hour. We were able to perform a full push for this LE, but the next incremental attempt would fail again.
To troubleshoot/resolve this issue we republished the data entity and attempted to perform a full push for all LEs, however we now have a bigger problem. Most of the LEs are now failing after successfully pushing a subset of the data to the byod. There are a few LEs that are succeeding but have a very small amount of data. The document log gives the following error for the Export stage "Export execution failed for entity <data entity>: Export failed while copying data from staging to target:". In addition, the Infolog for the Export stage gives the following error: "BYOD export failed final attempt. Could not export data from target to destination." The Target stage give the following error: "Package Execution Failed for Entity Store".
In addition to republishing the data entity we have regenerated the mapping, enabled and disabled change tracking, all to no avail.
We are running 10.0.23 in production and I've noted that there is chatter here that a similar issue was identified in 10.0.25 and fixed in 10.0.26. Unfortunately, we are in the process of upgrade to 10.0.26 and we have recreated the issue in a 10.0.26 environment. There have been no recent changes to the data entity in question. The largest LE has only around 300K rows in this table, so it is not an excessive amount of data.
There are many data entities being pushed to the BYOD in production and all seem to be doing fine. Also note that I am able to successfully export the data entity for an LE to excel without issue.
Can anyone suggest a possible solution or next step to troubleshooting this?
Well, I guess I needed to type a detailed explanation to figure this out.
The issue was a unique key violation. Error messaging from D365 is not particularly helpful in this regard.
The solution was to drop the primary key on the BYOD database table.
#1
André Arnaud de Cal...
293,302
Super User 2025 Season 1
#2
Martin Dráb
232,108
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
