ERROR: Your previous transaction-level posting session has not finished process. Please allow time for it to finish.

(0) Share

Report

Posted on by Community Member

Our customer is getting the below message:

"Your previous transaction-level posting session has not finished process. Please allow time for it to finish." This is across all users in Receivables Transaction Entry. It will not clear upon log out and log in as instructed on error message.

How can they fix this problem? What is causing it?

*This post is locked for comments

I have the same question (6)

All responses (18)

Answers (0)

Sort by

Richard Wheeler 75,852 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Please have everyone exit GP and then delete all records in the tempdb..dex_lock and tempdb..dex_session tables.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like
a
(2)

Report
Copy link

Link copied!

Hi WennSoft,

Richard is right you will need to clear the stuck record for users. If clearing tempdb..dex_lock and tempdb..dex_session does not fix the issue. You can also try deleting all records from the SY00800 and SY00801 tables in the DYNAMICS database. (All users must be logged out of GP).

If the issue is still there, check for any batches in the company database SY00500 table with the user’s login ID as the BACHNUMB.

Rubal,

http://dynamicsgphelp.com/

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Is there a script for the tempdb..dex clearing?

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

delete [tempdb]..[dex_lock]

delete [tempdb]..[dex_session]

delete [dynamics]..[sy00800]

delete [dynamics]..[sy00801]

select * from [companydb]..[sy00500] where bachnumb like username%

Make sure everyone is out of GP when you do this.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

thank you! i shall ask the customer try it out! i appreciate everyone for getting back to me so fast.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Here is a script that might help you

delete from DYNAMICS..ACTIVITY where USERID not in (select loginame from master..sysprocesses)

delete from tempdb..DEX_SESSION where session_id not in (select SQLSESID from DYNAMICS..ACTIVITY)

delete from tempdb..DEX_LOCK where session_id not in (select SQLSESID from DYNAMICS..ACTIVITY)

delete from DYNAMICS..SY00800 where USERID not in (select USERID from DYNAMICS..ACTIVITY)

delete from DYNAMICS..SY00801 where USERID not in (select USERID from DYNAMICS..ACTIVITY)

I talked about it on my blog

gp.rosebizincblogs.com/.../removing-stranded-user-sessions-in-dynamics-gp-via-sql-server.html

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

My customer wrote back "Just tried running that script and it cleared a couple of rows, but seem to have no impact after logging back in."

Any other advice?

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Did they run these scripts while no one was in GP?

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

That's what the customer said.

Was this reply helpful? Yes No
veeyeskay Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi

Can you run the following scripts and let us know if it returns any records?

SELECT * FROM SY00500 WHERE BACHNUMB = ''

SELECT * FROM SY00500 WHERE BACHNUMB = '<User ID who faces the issue>'

SELECT * FROM RM00301 WHERE BACHNUMB = ''

SELECT * FROM RM10301 WHERE BACHNUMB = '<User ID who faces the issue>'

Was this reply helpful? Yes No