You’re offline. This is a read only version of the page.
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
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.
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.
run axutil schema command, it will regenerate the stored procedures including getNumInternal
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 !
I faced the same issue and fixed it by modifying the number sequence of the
General Journal Transfer in GL parameter
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
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
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,228
Super User 2024 Season 2
#2
Martin Dráb
230,056
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (