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,
Please make a backup and logout all users before doing the following to remove any stuck records on temp table.
SELECT * FROM DYNAMICS..ACTIVITY
SELECT * FROM DYNAMICS..SY00800
SELECT * FROM DYNAMICS..SY00801
SELECT * FROM TEMPDB..DEX_LOCK
SELECT * FROM TEMPDB..DEX_SESSION
If you get answers / results to any of the above, make sure everyone is in fact logged out of GP and then run the following scripts to clear the tables.
DELETE DYNAMICS..ACTIVITY
DELETE DYNAMICS..SY00800
DELETE DYNAMICS..SY00801
DELETE TEMPDB..DEX_LOCK
DELETE TEMPDB..DEX_SESSION
Please let me know how you are getting on with this.
That did not fix the issue. I also re-ran the grant script.
Hi,
Is this problem happen to one specific user, if so please try the following. Please make a backup before running the following.
run the following delete statement on the SY00800 table against the DYNAMICS database.
DELETE SY00800
Look for the problem records in the SY00500 table by running both the following statements against the company database.
Note In the following statements, xxx represents the user ID that contains the error.
SELECT * from SY00500 where BACHNUMB = ''
SELECT * from SY00500 where BACHNUMB = 'xxx'
If you have records that are returned with a blank BACHNUMB field, use the following delete statement.
DELETE SY00500 where BACHNUMB = ''
If you have records that are returned with a User ID in the BACHNUMB field, use the following delete statement.
Note In the following statement, xxx represents the user ID that contains the error.
DELETE SY00500 where BACHNUMB ='xxx'
This problem is with all users, all batches, all companies.
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.
Yes and no help.
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.
Ok,
Please run GP Utilities as administrator and logback and see.
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
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!!!
Share
Report
All responses (
Answers (
