Repeated Error on Sales Transaction Entry: "Your previous transaction level posting section has not finished processing. Please allow time for it to finish......."

(0) Share

Report

Posted on by Community Member

Hi All,

One of our GP user is repetitively experiencing an error in Sales Transaction Entry window.

The error is:

"Your previous transaction level posting section has not finished processing. Please allow time for it to finish. If you believe it has failed, log out of Microsoft Dynamics GP and log back in to recover transactions."

She continued to experience this and cannot open the Sales Transaction Entry window again IF I will not run the script below:

SELECT * FROM SY00500 WHERE BACHNUMB = '';

SELECT * FROM SY00500 WHERE BACHNUMB = 'rreyes';

If records are found, the script below should be run:

DELETE SY00500 WHERE BACHNUMB = 'rreyes';

Why does this error keeps on returning after he posted some transactions?

Thanks in advance,

Rotchine

*This post is locked for comments

I have the same question (0)

All responses (20)

Answers (2)

Suggested answer

MattPaulen 6,912 on at

Like (1)

Report

When doing transaction level posting, the posting will not complete until the user closes out of the Sales Transaction Entry window. I've seen the error happen often when a user is connecting through Citrix or some other type of terminal server and there is an inactivity timeout. So the user would be entering and posting transactions throughout the day and not close out of GP when they leave. They then get dropped from Citrix/terminal due to inactivity which leaves the batch stranded.

I can't say for certain that this is the issue but it's something to check. I'd definitely have them close out of the transaction window whenever leaving their desk that way the batch will finish posting.

Was this reply helpful? Yes No
Verified answer

Tristan Clores 2,812 on at

Like (1)

Report

Hi Rotchine,

Matt is spot-on on the possibility this is happening if you are on a Citrix environment. Some users do have a tendency of not logging out after their shift ends.

Another cause can be a corrupted User ID data. If this is happening only to a specific user, I can also recommend recreating the User ID.

Another option would be to check the workstation the user is using. It may be encountering connectivity problems to the server.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Matt,

The user is connecting to GP thru remote desktop only to the server where GP is installed. She logged out once she is done using GP.

Thanks,

Rotchine

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tristan,

Yes, only on that specific user this issue happens. As she is the one posting the transactions..

What if I recreated her User ID in GP, does it have any effect on her GP works?

Thanks,

Rotchine

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

Like (1)

Report

Run this script:

SELECT * FROM SY00500 ORDER BY BACHNUMB

Do you see any batches beginning with an '*' and her name. If so remove them. Also try running

select * from DYNAMICS..SY00800. What does this return? If you run this while no one is in GP there should be no records. If it does return records delete them.

If all else fails run these while no one is in GP and having performed a backup.

SELECT * FROM DYNAMICS..ACTIVITY

SELECT * FROM DYNAMICS..SY00800

SELECT * FROM DYNAMICS..SY00801

SELECT * FROM TEMPDB..DEX_SESSION

SELECT * FROM TEMPDB..DEX_LOCK

If any records are returned from any of them delete them from their respective tables.

Was this reply helpful? Yes No
MattPaulen 6,912 on at

Like (2)

Report

"She logged out once she is done using GP. "

Is she truly exiting out of GP or is she just logging out of the Remote Desktop session? I still think this could potentially be related to not fully exiting GP each day. I have this happening on a daily basis here. People tend to be in such a hurry to leave for the day that they don't exit properly.

As Tristan said, you could try recreating the user. It won't have any negative effect. You could even create a secondary user for them for a brief period of time to see if this is causing the issue or not.

Was this reply helpful? Yes No
Verified answer

Tristan Clores 2,812 on at

Like (0)

Report

Hi Rotchine,

It should not have any negative effect especially if you use the same User ID.

It is likely that she just closes her RDP session - either by clicking the X on the window or logging off - which causes her GP login to stay in the system.

If you have other GP users that has the same task as the one in question - just use the COPY function when recreating her User ID. That way, you'll be sure that the issue is not access/permission related.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tristan,

What I did is created a new user access and copied the access from the user id that has issues on Sales Transaction Entry window after posting.

Thanks,

Rotchine

Was this reply helpful? Yes No
Suggested answer

Tristan Clores 2,812 on at

Like (0)

Report

Hi Rotchine,

And is the user still encountering the issue? If she is, then it definitely has something to do with a corrupted user id.

Like what I mentioned before, it would be best to copy from another user who has the same task/role and is not encountering the issue.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tristan,

She is using her new user ID now on GP. As the user has the role of accounting manager, she's the only one has the access as accounts manager that's why I just copied her new user ID from her original user account.

We are still on stand by if the same issue will show once she started posting transactions. Once the error still appears, I will let you know via this thread.

Many thanks! :)

Rotchine

Was this reply helpful? Yes No