Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
Hi - I am facing problem in posting Vendor Invoice Journal, System give following error and Journal becomes locked by system
Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.
Anybody have expereince or can suggest solution for this problem? We are useing Dynamics AX 2012 with Cumulative update 2.
The Problem was because system was assigning duplicate Journal Number. It looks like continuous number sequence has some bug in AX 2012, because all sequence number which are continuous in our environment have same problem. As a work around i have disabled continuous check box with sequence numbers but will appreciate if someone can suggest better solution for it.
I'm experiencing the exact same issue except that removing the continuous check box does not resolve the problem. We have tried using another number sequence, triple checked all settings that might be near to causing the problem and I'm currently at a loss as to what to do.
Any help on this issue would be greatly appreciated.
Don't know if it will help, but something similar hapened to me.
Problem was that the sequence number was to big for the journal entry number so, the first n numbers in the journal entry were similar.
But that happened rigth away when we started setting up the system.
Pieter Foolen has suggested, but I haven't tested it yet.
"indeed when you disable the continuous number sequence the problem seems fixed. However, there are several aereas where it is mandatory to use continuous number sequence.
I also encounterd this problem, and by exident I noticed that I was missing the stored procedure "GetNumInternal" on the SQL server datababase.
Restoring this stored procedure from another database solved this problem"
We are experiencing the same problem also. discovered when I tried to post a journal in the fixed asset module.
Even if I try to do my transaction in the GL, I get the same error.
I unchecked the continuous box in my voucher, but I still get the same message.
What is the workaround that works ?
To add to the posting above "Problem was that the sequence number was to big for the journal entry number so, the first n numbers in the journal entry were similar."
I have set up several new companies in AX2012 and have found that the auto number sequence generator does NOT work well when the company code is 4 characters because it generates 11 digit number sequences such as CEUX-###### with next number set to 1. If the field length is 10 characters the first record is created okay as CEUX-00000 (dropping the 1) but the second record is also assigned number CEUX-00000 and causes an error. The solution is to either restrict your company code to 3 characters, or manually change all your number sequences.
Delete the free numbers in the status list for the number sequence code corresponding to General journal transfer.
Uncheck the continuous box, open the list of the number sequence to allow the system to reset, then recheck the continuous box. Worked for our client
Uncheck the continuous box of number sequence code which you define in GL setup> parameter > number sequence > Subledger Journal entry
Following is the response we got from MS support consultant; i have not personally applied this in any environment. I think its worth giving a shot.
The cause of for the issue is likely in the SQL stored procedure “getNumInternal”. It might be missing or AOS account has no permissions to execute the procedure.
Could you please go to SQL Management Studio -> AX database -> Programmability -> Stored Procedures and check if the procedure is present and if AOS account has permissions to execute the procedure?
You can grant permissions explicitly for the AOS account with this SQL query:
use MicrosoftDynamicsAX; --replace with actual AX database name
grant execute on dbo.getNumInternal to [contoso\administrator] --replace with actual AOS domain account
Please run in TEST environment first and create SQL backup before performing any updates!
Dear All I have received the same error. In fact I have tried to uncheck the continuous [not feasible for us, because we need automatic number sequence] box and the GetNumInternal stored procedure is also there. Any other solution
I faced the same issue and fixed it by modifying the number sequence of the
General Journal Transfer in GL parameter
In our case, the problem came from the upgrade from R1 to R2, the stored procedure getNumInternal still had the code from R1. I've replaced the stored proc code by the real code(which includes the new input 'Partition' parameter) and it works !
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13