Has anyone ever seen this message before or know what causes it. It seems to appear upon loading a sales trx entry record. The user cannot do anything when this message appears. The only resolution to free up the locked session is to change the batch number. Any help would be appreciated.
Thanks,
Justin
*This post is locked for comments
Glad you were able to find it. It always pays to look at your DYNAMICS.SET file to see what program are installed.
So, after monitoring this issue after manualling removing all data from the session tables, I found that an add-in program written by a third party needed an update - it was running a stored procedure that seemed to be just crashing and leaving an orphan SQL session out there in GP. It has since been addressed and I haven't seen the problem since. Thanks again Richard.
That is exactly what that means. These normally result from users abnormally exiting GP. Hopefully that was the source of the issue.
Hi Richard,
I got everyone out and ran the script. Hopefully we will be good going forward. I did notice however before running the script, with all users out of the system, there were still records in DEX_SESSION (a decent number of them). I'd imagine this was the source of the problem. Does that mean there were 'orphan' sessions out there?
Thanks again,
Justin
I've been trying to pinpoint the frequency or any patterns with it. Thanks for the suggestion Richard, I'll give it a try.
Justin
How often does this occur? I would start by running this script when no one is in GP in SSMS
DELETE DYNAMICS..ACTIVITY
DELETE DYNAMICS..SY00800
DELETE DYNAMICS..SY00801
DELETE TEMPDB..DEX_LOCK
DELETE TEMPDB..DEX_SESSION
You have something not clearing in SQL. Hopefully you do not have users who are losing connection to the SQL server.
Share
Report
All responses (
Answers (
75,848
