web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Cannot create a record...
Microsoft Dynamics AX (Archived)

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

(0) ShareShare
ReportReport
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)
  • Cas van de Luijtgaarden Profile Picture
    Cas van de Luijtgaa... 5 on at

    We have had the same problem and solved it as follows.

    In the error message the number of the journal and the corresponding table is shown. Check the table to see that the number is already used.  If so,

    go to Organization administration/Common/Number sequences/Number sequences

    Select Number Sequences.

    Check Status List.

    There you will see the entry that's earlier shown in your error message. This is the entrie that AX thinks he must use the next time, but the problem is that it already exists.

    If it's the same entry, select the entry and delete it with ALT-F9.

    Run Manual Cleanup - Current

    The problem should be solved.

  • Suggested answer
    saransh321 Profile Picture
    saransh321 212 on at

    Thanks I too resolved this issue but in a different way. I checked whether the stored procedure exists which was positive. I also checked whether the AOS user has access to to this procedure and this too was positive. This problem was encountered for the first time. One thing to note that i received this error after i restored previous week database backup. I Couldn't remove continuous as this was requirement. I Simply restarted the AOS then the DB Server. This resolved my issue.

    Thanks again for you solution.

  • Ruud De Baecke Profile Picture
    Ruud De Baecke 10 on at

    run axutil schema command, it will regenerate the stored procedures including getNumInternal

  • Evaldas Profile Picture
    Evaldas 1,800 on at

    Thanks NICOLAS GRANJON!!! The problem was this store procedure not updated to AX 2012 R2. You have saved me tons of time ;)

  • Shirl Profile Picture
    Shirl 385 on at

    FYI, I had the same problem and the fix I had was updating the subledger journal entry number sequence to not be continuous.

  • Nicolas GRANJON Profile Picture
    Nicolas GRANJON 510 on at

    Hi,

    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 !

  • Community Member Profile Picture
    Community Member on at

    I faced the same issue and fixed it by modifying the number sequence of the

    General Journal Transfer in GL parameter

  • Ahmed Muhammad Alam Profile Picture
    Ahmed Muhammad Alam 3,089 on at

    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

  • Suggested answer
    Biju_John Profile Picture
    Biju_John 601 on at

    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

  • lp 181082 Profile Picture
    lp 181082 70 on at

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

    Rabia

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the December Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
TAHER Mehdi Profile Picture

TAHER Mehdi 3

#2
Martin Dráb Profile Picture

Martin Dráb 2 Most Valuable Professional

#2
Volodya Profile Picture

Volodya 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans