We have an error in production in the journal entry window. When a user tries to make an entry to any JE they receive a message "it's been delted by another user".
This has virtually stopped ME close. Any help is greatly appreciated.
*This post is locked for comments
Hi Donnette,
Sounds like a user is stuck in this window in a temp table. Have all users get out of GP and these tables should be empty when no users are in. If not, then delete them and try again.
SELECT * FROM DYNAMICS..ACTIVITY
SELECT * FROM DYNAMICS..SY00800
SELECT * FROM DYNAMICS..SY00801
SELECT * FROM TEMPDB..DEX_LOCK
SELECT * FROM TEMPDB..DEX_SESSION
DELETE DYNAMICS..ACTIVITY ---make sure all users are out before you run this.
DELETE DYNAMICS..SY00800
DELETE DYNAMICS..SY00801
DELETE TEMPDB..DEX_LOCK
DELETE TEMPDB..DEX_SESSION
Thanks,
Cheryl
Microsoft Community
Yes. Thank you.
All,
The problem was with the AIT tool designed by MC2. I am not happy with their support team who apparently is 1 person.
Thank you for the help.
Donnette
Run the below query against the and attach the result.
SELECT * FROM SY00500 WHERE BACHNUMB= 'ENTET YOUR BATCH ID'
From the above query check BCHSOURC contains the * symbol and also run the below query to check JV is available in both table with correct batch number & source.
SELECT * FROM GL10000 WHERE JRNENTRY='ENTER YOUR JV NUMBER'
SELECT * FROM GL10001 WHERE JRNENTRY='ENTER YOUR JV NUMBER'
Hope this helps!!!
Throwing a random thought here as I've not seen this error on your window ever but get it on occasion when I'm developing a new window which has a scrolling window.
Out on a limb here but I would guess you have something like GL work lines saved in the GL work line table (GL10001) that have the next JE number already on them but no corresponding record in the GL work header (GL10000) and they might be what GP considers the next JE number.
I would try setting the next JE number up one in the Setup -> Financial -> General Ledger setup window and/or explore the records in Gl10001 / Gl10000 tables and see if you find an orphan situation. I don't recall for sure but I don't think the next JE number is managed as a lock in dex_locks so I'd try the above and see what happens.
Best
Tim
Ok,
Please run GP Utilities as administrator and logback and see.
If Babu's latest advice doens't resolve the issue, I would reboot the GP server. You've got a record lock occurring somewhere which rebooting should clear.
Yes and no help.
Hi,
Have you tried to run check link against System-Security setup & Security user assignment. As well as you can try to run Financial-Transactions.
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,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (