*This post is locked for comments
Today, I have experienced the same issue and I would like to write the solution down so that others might solve it as well. I will be talking about MDyn365FO version.
We modified Customers standard data entity and added 2 new fields. Once we installed that code into "Demo" env, we refreshed data entity list and re-generated target mapping. After that, when I tried to export Customers data, this error appeared. It seems that the system cached old mapping and I noticed that when I tried to add the entity to the export project without staging and with staging. Strange enough that "with staging" the system exported data without errors and "without staging" this error appeared. I assumed that it was a cache. So I did the following in order to solve it:
1. Removed data entity from the project
2. Removed data entity at all
3. Refreshed entity list
4. Regenerated target mapping
5. Created a new project
6. Added data entity to the newly created project
And it works as expected.
All we did to fix this issue was to validate the service directory. Go to DIXF > Setup > Data Import/export parameters > Validate. It's like the AX or the DIXF service is losing the path to the directory. This has happened twice now since our kernel upgrade and this fixed it both times. Would love to know what the permanent fix is, though.
Dear All,
I'm having exactly the same issue , can anybody please advise what is the solution
many thanks
Best Regards,
Iwan Sunardy
Hi Andi,
Thanks for sharing.
@Florian, can you indicate if this could be your answer?
This time i had the same error on another system / other customer. I played a bit around and it seems to print out the error if the entity mapping is not correctly configured. I just describe the way i did it for exporting vendors.
First I created a definition group 'VendorsToStaging' to put the entities to staging on the source system. I configured the file format to AX. The I run the 'To Staging' and checked the staging files.
Next I created a second entity 'VendorsCSV' to export the entities. I set the file format to CSV and created a "sample file" with all fields. I saved the sample file as Vendors-Sample.txt and set it in the sample path line (via UNC Path). I also clicked regenerate source definition and openden the source definition for a short check if the mappings are done.
Then I switchend back to the first entity 'VendorsToStaging' and clicked export to file. In the (second) dialog I selected the VendorsCSV def group and then the data was exported correctly.
Hi Andre,
we will do that. Thanks for your time.
Best regards
Florian
Hi Florian, AndiRudi,
I have no clue what could have caused the error other than perhaps a compilation problem or some caching?
Whenever you have the error again, please update this post again; probably with any information that could be usefull.
We are not quite sure why, but when we tried the export today, it worked as expected. Probably there was some issue with the export data, although we are using the contoso demo data.
Hi Andre, i am also working on the issue. The version of the files is 6.2.1000.4051. I already checked that with another working dmf cu7 Installation and they seem to be the newest.
In the meantime i decompiled the whole stuff tracked it down to the line
HRESULT: 0xC0202009
bei Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSDesigntimeComponent100.ReinitializeMetaData()
bei Microsoft.Dynamics.AX.DMF.SSISHelper.DMFFlatFilePackageExport.UpdateSourceProperties(IDTSComponentMetaData100 flatFileSourceComponent, CManagedComponentWrapper srcFlatFileInstance, String name, Package _Package) in Microsoft.Dynamics.AX.DMF.SSISHelper.pdb.source\Microsoft\Dynamics\AX\DMF\SSISHelper\DMFFlatFilePackageExport.cs:Zeile 598.
The method ReinitalizeMetaData throws the exception but there is no more Information i can get. Seems to be some rights issue, but I cannot find the cause. We've already reinstalled dmf and it's now using the aos service account which is a local administrator at the moment....
Any ideas?
Hi Florian,
Did you removed the binaries from the older DIXF prior to the upgrade (Client, Server, Integration services)?
The dll's that are shipped with CU7 are newer and do not overwrite the older versions.
Can you otherwise try to explore the event viewer for possible errors or warnings?
André Arnaud de Cal...
292,111
Super User 2025 Season 1
Martin Dráb
230,934
Most Valuable Professional
nmaenpaa
101,156