Share
ReportHi All,
On my customer, after the an upgrade performed during last December from Dynamics Ax 2012 R3 CU13 to Dynamics Ax 2012 R3 CU3 Feb'2019 (build 6.3.6000.8149) I am facing a very strange error.
Not for all users, not for all number sequence, not always for the same process, but many times during the labor day, we get an error like the following:
- Purchase number %1 is already in use.
- Voucher %1 is already used as at date %2.
- Voucher %1 is already being used.
When we went to investigate, we notice that the number that is in one of the three messages above instead of the %1 already exists as a document posted or a voucher transaction also posted.
The system is trying the use the number in question, because his still remains on the status list form of the number sequence. The number is in the status "active" and is assigned to the user that receive the error log during the process that he's executing.
Someone with the same problem in the past?
Can the problem be related to a setup on number sequence? Can the problem be related to Ax code? Can the problem be located on the stored procedure "getNumInternal"?
Thank you.
All responses (
Answers (
293,202
