"The export file, [Path_Name], has already been transmitted. You can no longer void these entries" error message when you try to void an electronic payment in the RoleTailored client in the North American version of Microsoft Dynamics NAV 200...

S’applique à : Dynamics NAV 2009 Service Pack 1

This article applies to Microsoft Dynamics NAV for the the North American region.

Symptoms


In the RoleTailored client in the North American version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1), when you try to void an electronic payment through the payment journal, you receive the following error message:
The export file, [Path_Name], has already been transmitted. You can no longer void these entries.

Resolution


Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.




Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
  • The Modify permission for the object that you will be changing.
  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.


Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, change the code in the EndExportFile function in the Export Payments (ACH) Codeunit(10090) as follows:
Exsiting code
...
ExportFile.CLOSE;
IF ISSERVICETIER THEN BEGIN
ClientFile := BankAccount."E-Pay Export File Path" + BankAccount."Last E-Pay Export File Name";

// Delete the following line.
IF NOT DOWNLOAD(FileName,'','','',ClientFile) THEN BEGIN
// End of the deleted line.

ERASE(FileName);
EXIT(FALSE);
END;
ERASE(FileName);
END;

EXIT(TRUE);
...
Replacement code
...
ExportFile.CLOSE;
IF ISSERVICETIER THEN BEGIN
ClientFile := BankAccount."E-Pay Export File Path" + BankAccount."Last E-Pay Export File Name";

// Add the following line.
IF NOT COPY(FileName,ClientFile) THEN BEGIN
// End of the added line.

ERASE(FileName);
EXIT(FALSE);
END;
ERASE(FileName);
END;

EXIT(TRUE);
...

Change the code in the EndExportFile function in the Export Payments (RB) Codeunit(10091) as follows:
Exsiting code
...
ExportFile.CLOSE;
IF ISSERVICETIER THEN BEGIN
ClientFile := BankAccount."E-Pay Export File Path" + BankAccount."Last E-Pay Export File Name";

// Delete the following line.
IF NOT DOWNLOAD(FileName,'','','',ClientFile) THEN BEGIN
// End of the deleted line.

ERASE(FileName);
EXIT(FALSE);
END;
ERASE(FileName);
END;

EXIT(TRUE);
...
Replacement code
...
ExportFile.CLOSE;
IF ISSERVICETIER THEN BEGIN
ClientFile := BankAccount."E-Pay Export File Path" + BankAccount."Last E-Pay Export File Name";

// Add the following line.
IF NOT COPY(FileName,ClientFile) THEN BEGIN
// End of the added line.

ERASE(FileName);
EXIT(FALSE);
END;
ERASE(FileName);
END;

EXIT(TRUE);
...

Change the code in the EndExportFile function in the Export Payments (Cecoban) Codeunit(10092) as follows:
Exsiting code
...
ExportFile.CLOSE;
IF ISSERVICETIER THEN BEGIN
ClientFile := BankAccount."E-Pay Export File Path" + BankAccount."Last E-Pay Export File Name";

// Delete the following line.
IF NOT DOWNLOAD(FileName,'','','',ClientFile) THEN BEGIN
// End of the deleted line.

ERASE(FileName);
EXIT(FALSE);
END;
ERASE(FileName);
END;

EXIT(TRUE);
...
Replacement code
...
ExportFile.CLOSE;
IF ISSERVICETIER THEN BEGIN
ClientFile := BankAccount."E-Pay Export File Path" + BankAccount."Last E-Pay Export File Name";

// Add the following line.
IF NOT COPY(FileName,ClientFile) THEN BEGIN
// End of the added line.

ERASE(FileName);
EXIT(FALSE);
END;
ERASE(FileName);
END;

EXIT(TRUE);
...

Prerequisites

You must have the North American version of Microsoft Dynamics NAV 2009 Service Pack 1 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.