Troubleshooting Aptean EDI

The configuration requirements for the Aptean EDI solution are very specific regarding what is and isn't acceptable, and if the solution is not set up properly, its functionality will not perform as expected. To assist in proper setup, we present below a number of common Aptean EDI issues and error messages, along with possible ways to address them.

Each troubleshooting instance contains the following information:

• Issue/Message: Either a brief description of the issue or the text of an error message that the user receives heads every issue. Note that the message text uses three instances of the pound symbol (###) as a placeholder for the inclusion of actual data. For instance, if a message specifies a particular trading partner’s ID number, the number will be presented as ### in the message text.
• Occurrence: The particular activity or situation that causes the issue.
• Message Location: If the issue represents a specific error message, the location of that message is provided.
• Possible Solution: Guidance as to how the issue can be corrected is provided. In some instances, an issue may have multiple causes, and, therefore, multiple solutions. In such a scenario, possible solutions will be listed in the order in which they should be attempted.

Message/Issue	Occurrence	Message Location	Possible Solution
Cannot create an instance of the following .NET Framework objects: assembly Aptean EDI.Handler, Version=### Culture=neutral, PublicKeyToken=###, type Aptean EDI.NAVHelpers.	Whenever Job Queue is run.	Message appears to the user at the time of occurrence.	Stop and re-start the Business Central Service Tier.
Could not load type 'Aptean EDI.EventLogHelper.'Aptean EDI.Handler, .	When codeunits are being compiled in the Dynamics Business Central Development Environment.	Message appears to the user at the time of occurrence.	Ensure that the Aptean EDI Handler has been installed on the machine on which codeunits are being compiled.
Customer could not be translated. TradingPartnerID: ###Vendor: ###AddressLocationNumber: ###	When attempting to process a failed EDI message.	Message appears to the user at the time of occurrence.	Set up an EDI translation for the relevant customer record. Assign a value in the EDI Vendor No. field on the relevant Customer card.
Failed to receive from EDI Port ### - A call to Aptean EDI.Inbound.Receive failed with this message: Your software maintenance on this application has expired. Please contact your reseller.	Whenever Job Queue is run.	EDI Log.	Contact your Dynamics Business Central partner to obtain an updated Aptean EDI license key.
Failed to receive from EDI Port ### - Failed to receive from EDI Port ### - System.IO.IOException: The network name cannot be found. At System.IO._Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.I.	Whenever Job Queue is run.	EDI Log.	Review your network's firewall settings and ensure that there are no settings preventing the transmission of data.
Failed to receive from EDI Port ### - System.Exception: Error: System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1. at System.Xml.XmlTextReaderImpl.Thr.	Whenever Job Queue is run.	EDI Log.	Ensure that there are no special characters (such as #, $, %, etc.) in the file name. Review the relevant In/Out address paths (either specific to the EDI port or the default values on the EDI Setup page) and ensure that they are correct (for example, the slashes go in the proper direction). Close and re-open the Dynamics Business Central Client.
Failed to receive from EDI Port ### - System.Exception: Error: System.Xml.XmlException: Unexpected end tag. Line 87, position 3.	Whenever Job Queue is run.	EDI Log.	Contact SPS with instructions to check the XML file's format; it needs an appended header or footer that meets Dynamics Business Central's requirements.
Item could not be translated.ConsumerPackageCode: ###BuyerPartNumber: ###VendorPartNumber: ###	When attempting to process a failed EDI message.	Message appears to the user at the time of occurrence.	Set up a cross reference for the relevant item record. The cross reference should have one of the following values: The Cross-Reference Type field should be set to Barcode and a cross reference established for the listed ConsumerPackageCode value in the error message, or The Cross-Reference Type field should be set to Customer and a cross reference established for the listed BuyerPartNumber or VendorPartNumber value in the error message.
Microsoft Dynamics Business Central Aptean EDI.Aptean EDIException: Error: System.XmI.XmIException: Unexpected end of file has occurred. The following elements are not closed:	Whenever Job Queue is run, or when attempting to manually process an inbound EDI message.	When Job Queue is run, this message appears in the EDI Log. When the user is attempting to manually process an inbound EDI message, this message appears to the user at the time of occurrence.	Ensure that the Aptean EDI Handler has been installed on the Service Tier server processing EDI messages. Because the Aptean EDI Handler also must be installed on any machine on which codeunits will be compiled, it is possible to confirm that the issue is due to the absence of the Aptean EDI Handler by attempting to compile codeunits (provided the user has permission to compile codeunits) in the Dynamics Business Central Development Environment. If this process fails as well, it is likely that the Aptean EDI Handler has not been installed.
No EDI messages are being created	Whenever Job Queue is run.	N/A	Review the relevant EDI ports and ensure that the Inactive field is unchecked.
System.Exception: Exception: System.UnathorizedAccessException: Access to the pathe is denied; at System.IO._Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalMOve(String sourceFileName, String destFileNave, Boolean checkHost) N NDirectory:... at Aptean EDI.Helpers.FailFile(String_filename at Aptean EDI.Inbound.ConvertFile(String filename) at Aptean EDI.Inbound.Receive(XmlDocument& doc)	Whenever Job Queue is run.	Message appears to the user at the time of occurrence.	Ensure that the user has been granted the necessary permissions to access the folder that has been assigned in the Message Directory field on the General FastTab of the EDI Setup page.
The Electronic Interchange department is not present in Dynamics Business Central	N/A	N/A	Open the Development Environment and, in the Object Designer, compile all menusuite objects. Close and re-open the Dynamics Business Central client.
The field Unit of Measure Code of table Sales Line contains a value (###) that cannot be found in the related table (Item Unit of Measure).	When attempting to process a failed EDI message.	Message appears to the user at the time of occurrence.	The specified unit if of measure has not been assigned to the relevant item record. Assign the appropriate unit of measure to the item.
The SMTP mail system returned the following error: "Transaction failed. The server response was: 5.7.1 <###@###>: Sender address rejected: Access denied".	When attempting to send a notification message.	Message appears to the user at the time of occurrence.	Review the values that have been assigned on the SMTP Mail Setup page and ensure that they are correct.
The trading partner ID is incorrect on outbound EDI activities	When processing an outbound EDI activity.	N/A	Ensure that there is an inbound sales order (850) document that has been associated to the relevant outbound EDI activity Verify that a valid EDI translation exists for the relevant customer record.
This message is for C/AL programmers exception was raised in the method Run. The the OLE control or Automation server has returned error (HRESULT)2147352567. The component did not provide the exception description.	When attempting to open the defined message directory by clicking the AssistEdit button to the right of the Message Directory field on the General FastTab of the EDI Setup page.	Message appears to the user at the time of occurrence.	Ensure that there are no special characters (such as #, $, %, etc.) or spaces in the directory name. For example, the following directory names would be incorrect: \\gunnar\EDI\bcED!\ \\gunnar\EDI\bc EDI\ The following directory name is correct: \\gunnar\EDI\Aptean EDI\
This message is for C/AL programmers not create an instance of the OLE control or Automation server identified byGUID= ###: UnknownAutomation Server.Unknown Class. Check that the OLE control or Automation server is correctly installed and registered.	Whenever Job Queue is run.	Message appears to the user at the time of occurrence.	Ensure that the Aptean EDI Handler has been installed on the Service Tier server processing EDI messages. Because the Aptean EDI Handler also must be installed on any machine on which codeunits will be compiled, it is possible to confirm that the issue is due to the absence of the Aptean EDI Handler by attempting to compile codeunits (provided the user has permission to compile codeunits) in the Dynamics Business Central Development Environment. If this process fails as well, it is likely that the Aptean EDI Handler has not been installed.
Unable to send notification. The SMTP mail system returned the following error: (0x80040213): The transport failed to connect to the server.	When attempting to manually process an EDI message. Prior to the display of the message, the program lags and performance is poor.	Message appears to the user at the time of occurrence.	Review the relevant EDI port and ensure that the Notify on Success field is unchecked. Review the EDI Setup page and ensure that the Notify on Success field is unchecked.