Dynamics AX DIEF error: Package Execution Failed Please Check Event Log in DMF Service Box

By Josh Score | May 24, 2016

When previewing and importing in Dynamics AX using the Data Import Export Framework tool (DIEF), I recently ran into this error: Package execution failed please check event log in DMF service box.                                                        

Package execution failed please check event log in DMF

This error message was quite deceiving when we found the answer to the issue. It was particular to imports using Excel formats. Almost all CSV format imports worked without issue and in this scenario changing the Excel format to CSV did not resolve it.

To give a bit more background, we were able to verify Excel file formats did import when using a scaled down template and data set. This was important, as we were able to verify the components for DIEF and Dynamics AX to read Excel files was working properly. To test this, try limiting your import file to just required fields and enter something (ex: 1) as a value in each column. This should allow you to preview the file and verify the data is able to be read, even if it isn’t applicable or accurate.

Example: Vendors

Preview source filesAs I mentioned before, the error received was quite deceiving, as we found it was actually our data and setup that was causing the error. We first verified the data that we were attempting to import. Make sure you remove any duplicate values where the record type should be unique. In our scenario, there were duplicate vendor account numbers.

Our second find was empty space. Make sure you review the data for any missing record fields that would be a required when setting up the data manually within Dynamics AX. In our scenario, we had found a few records without a vendor group assigned to a vendor account. To add to this issue, our initial plan was to auto-default currency and language on the vendor records. This was rather interesting, as this is something that defaults when creating a vendor manually, but LanguageID was not a required field in the vendor DIEF entity. We made sure to set the auto-default in the DIEF Modify Source Mapping details form for the columns. This was an easy oversight, as we didn’t think the preview source file process would verify this.

Modify source mappingThe last step I wanted to mention was deleting the empty space columns and rows from the source file. We received the data from another source and even though the blank rows and columns appeared empty, there was something in these fields causing the preview/import to fail. This likely was from text spaces within the fields, as that is something I’ve seen cause issues in both Excel and CSV import files alike.

That being said, the lesson of the story is to verify your source data file. Whether it’s blank columns, required fields, or empty space in random cells, make sure you follow these steps and you can avoid wasting some time on an error that isn’t very clear.

On a side note: This is what the SQL server Event View caught when receiving the error: Package “{xxxx-xxx-xx-xxxx}” failed.

Package execution failed

Here are a couple of interesting resource blogs I came across during this issue:



Under the terms of this license, you are authorized to share and redistribute the content across various mediums, subject to adherence to the specified conditions: you must provide proper attribution to Stoneridge as the original creator in a manner that does not imply their endorsement of your use, the material is to be utilized solely for non-commercial purposes, and alterations, modifications, or derivative works based on the original material are strictly prohibited.

Responsibility rests with the licensee to ensure that their use of the material does not violate any other rights.

Start the Conversation

It’s our mission to help clients win. We’d love to talk to you about the right business solutions to help you achieve your goals.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!