There were some stuck sessions. I cleared the session locks. There was also a stuck batch. Stuck batches occur when connectivity is lost, and someone is in a transaction that has not been saved to a batch. I would recommend saving transactions to a batch and avoiding single transaction posting. Occasionally, users forget to close the posting journals and the process does not complete. Let us know if this keeps happening and we could do a systems review.

For stuck batches for each company database:

select * from SY00500

If the BACHNUMB is a user id such as mcates all lowercase then that is evidence of a stuck batch. These records should be deleted.

Other places to look are:

Select * from dynamics..sy00800

These are sessions and could well be legitimate. You can check after hours when everyone is out. You should clear anything from the sy00800 if everyone is out.

select * from dynamics..activity

To check who is in.

Stuck sessions are in two tables in the TEMPDB. DEXLOCKS and DEXSESSIONS. Dex Locks are bad and should be cleared. Dex sessions are ok if people are active in the system. The dexsession has a reference number to the user in the activity table.

Article ID: 29, Created: March 10, 2022 at 2:57 PM, Modified: March 10, 2022 at 2:57 PM

Great Plains "Stuck sessions"

Add Feedback

Was this article helpful?

Share this article