Some times there are session in AX that are in ending blocked mode and causing the AX perfomance impact.
What you can do just right the below query to check if there is blocked session in AX or not.
'select * from SysClientSessions where SysClientSessions.STATUS = 3'
if you got any record than it means that there is blocked session in AX.
Before deleting it first verify the 'same session id' in AX -> administration -> online users.
filter the record with that session id and u will see the record with status 'ending blocked'
Now go to sql and delete the record that you find in above query or call the Sql Stored Procedure [KillDBSession] with correct session id.
Once you kill the session the user will be successfully able to login again in AX.
For more details on this please refer to the following blog:
https://axatoz.wordpress.com/2014/04/10/how-to-kill-a-blocking-session/
Thanks,
Muhammad Zahid.
What you can do just right the below query to check if there is blocked session in AX or not.
'select * from SysClientSessions where SysClientSessions.STATUS = 3'
if you got any record than it means that there is blocked session in AX.
Before deleting it first verify the 'same session id' in AX -> administration -> online users.
filter the record with that session id and u will see the record with status 'ending blocked'
Now go to sql and delete the record that you find in above query or call the Sql Stored Procedure [KillDBSession] with correct session id.
Once you kill the session the user will be successfully able to login again in AX.
For more details on this please refer to the following blog:
https://axatoz.wordpress.com/2014/04/10/how-to-kill-a-blocking-session/
Thanks,
Muhammad Zahid.
No comments:
Post a Comment