Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

(0) Share

Report

Posted on by Rizwan Idrees

525

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.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (18)

Answers (0)

Suggested answer

Muhammad Rizwan Idrees on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

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.

Was this reply helpful? Yes No
Brendon Breedt 160 on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

Hi Rizwan,

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.

Thanks

Was this reply helpful? Yes No
Juliuz 115 on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

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.

Was this reply helpful? Yes No
Muhammad Rizwan Idrees on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

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"

Was this reply helpful? Yes No
Girard Manon 160 on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

Good day

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 ?

Suzanne

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

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.

Was this reply helpful? Yes No
Renjith Mathew 130 on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

Delete the free numbers in the status list for the number sequence code corresponding to General journal transfer.

Was this reply helpful? Yes No
Gina Luciano 30 on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

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

Was this reply helpful? Yes No
lp 181082 70 on at

Like (0)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

Uncheck the continuous box of number sequence code which you define in GL setup> parameter > number sequence > Subledger Journal entry

Rabia

Was this reply helpful? Yes No
Suggested answer

Biju_John 601 on at

Like (1)

Report

Re: Cannot create a record in General journal entry (GeneralJournalEntry). Date: .The record already exists.

Hi

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!

Regards

John

Was this reply helpful? Yes No