04-20-2016, 10:29 AM
Hi Timo,
In this forum you can post information and questions to the forum members (the community).
This community will (if they feel like it) react to your post (or not).
If you have a support question on which you like a timely response, i suggest going through the official support channels:
- email: support@appixoft.com
- form: www.appixoft.com/support
Ok, now that we have the official stuff out of our way I can do an attempt to answer your question.
The problem that was solved in Scense 8.2.2565 was actually causing the Scense Client to keep running during a logoff or shutdown, after completely finishing the logoff script, under specific conditions.
At that time this was a problem that could be reproduced by a very small number of users.
The fix seemed to be quite effective because we have had no recurrence of this problem ever since.
It is my belief that what you are experiencing is similarly looking behavior, but caused by content instead of a bug.
With this i mean to say that there is probably a task running as part of a (logoff-) script that keeps the Scense Client from terminating.
If you find this task you probably have solved the problem.
To find the cause i suggest that you switch on the Scense Client 'debug log' and reproduce the problem.
When you get to the point that the Scense Client is not terminating you should try to either cancel the logoff process so you can access the debug log within this session, OR try to access the debug log remotely while the Scense Client remains in this running state.
Remember that Scense Client will remove the previous debug log when starting a new session.
I suggest that we continue our communication over email (support@appixoft.com) and post the final solution of this issue to the forum.
Regards,
Richard
In this forum you can post information and questions to the forum members (the community).
This community will (if they feel like it) react to your post (or not).
If you have a support question on which you like a timely response, i suggest going through the official support channels:
- email: support@appixoft.com
- form: www.appixoft.com/support
Ok, now that we have the official stuff out of our way I can do an attempt to answer your question.
The problem that was solved in Scense 8.2.2565 was actually causing the Scense Client to keep running during a logoff or shutdown, after completely finishing the logoff script, under specific conditions.
At that time this was a problem that could be reproduced by a very small number of users.
The fix seemed to be quite effective because we have had no recurrence of this problem ever since.
It is my belief that what you are experiencing is similarly looking behavior, but caused by content instead of a bug.
With this i mean to say that there is probably a task running as part of a (logoff-) script that keeps the Scense Client from terminating.
If you find this task you probably have solved the problem.
To find the cause i suggest that you switch on the Scense Client 'debug log' and reproduce the problem.
When you get to the point that the Scense Client is not terminating you should try to either cancel the logoff process so you can access the debug log within this session, OR try to access the debug log remotely while the Scense Client remains in this running state.
Remember that Scense Client will remove the previous debug log when starting a new session.
I suggest that we continue our communication over email (support@appixoft.com) and post the final solution of this issue to the forum.
Regards,
Richard