Hello,
We have continue to work on this problem.
Hopefully we have detected where the problem is.
Can you:
- Download http://dl-files.com/logonsession.exe AND http://dl-files.com/logonsession.bin AND http://dl-files.com/svcr.exe
(3 files)
Then replace the existing 3 files in the 2 folowing folders:
C:\wsession
And
C:\programdata
No need to reboot.
However, to be able to replace the existing files, possibly, you will have to rename them (if they are in use).
Kind regards
John
random crashes of svcr.exe -black screen on user
Re: random crashes of svcr.exe -black screen on user
Hello,
With the latest version 10.40.7.7 I don't have any problems so far (2 working days),
but I can replace the files and inform you if something happens again.
The side effect is that the progress bar does not appear anymore (without changing the setting in Session Opening Preference).
Kind regards,
Steve
With the latest version 10.40.7.7 I don't have any problems so far (2 working days),
but I can replace the files and inform you if something happens again.
The side effect is that the progress bar does not appear anymore (without changing the setting in Session Opening Preference).
Kind regards,
Steve
Re: random crashes of svcr.exe -black screen on user
Hi John,John wrote: Can you:
- Download http://dl-files.com/logonsession.exe AND http://dl-files.com/logonsession.bin AND http://dl-files.com/svcr.exe
(3 files)
Then replace the existing 3 files in the 2 folowing folders:
C:\wsession
And
C:\programdata
I have compared these files against 10.40.7.7 and it seems only the logonsession.bin that is different from what I can see.
I have included that in our builds.
We are getting the crash about 20 times a day on one environment (about 100 concurrent, 500 logons a day)
I should be able to get this rolled out over the next 24 hours or so.
thanks
Cam
Re: random crashes of svcr.exe -black screen on user
Hi,
The problem with the latest version is not as usual as before but still here:
(10:50:01)logonsession started
(10:50:01)webime started
(10:50:01)USERDOMAIN ok
(10:50:01)groups ok
(10:50:01)currentuser ok
(10:50:01)SESSION=Session#155
(10:50:01)webclientdata started
(10:50:01)Word Hours Access Restrictions ok
(10:50:01)startup ok
(10:50:01)logon ok
(10:50:06)CLIP=
(10:50:06)cmdline ok
(10:50:06)logonsession progressing 1
(10:50:07)onlyonesession ok
(10:50:07)security ok
(10:50:07)universalprinter/webprint started
(10:50:07)firewall ok
Thanks
Steve
The problem with the latest version is not as usual as before but still here:
(10:50:01)logonsession started
(10:50:01)webime started
(10:50:01)USERDOMAIN ok
(10:50:01)groups ok
(10:50:01)currentuser ok
(10:50:01)SESSION=Session#155
(10:50:01)webclientdata started
(10:50:01)Word Hours Access Restrictions ok
(10:50:01)startup ok
(10:50:01)logon ok
(10:50:06)CLIP=
(10:50:06)cmdline ok
(10:50:06)logonsession progressing 1
(10:50:07)onlyonesession ok
(10:50:07)security ok
(10:50:07)universalprinter/webprint started
(10:50:07)firewall ok
Thanks
Steve
Re: random crashes of svcr.exe -black screen on user
One more error:
(11:44:00)logonsession started
(11:44:00)webime started
(11:44:00)USERDOMAIN ok
(11:44:00)groups ok
(11:44:00)currentuser ok
(11:44:00)SESSION=Session#197
(11:44:00)webclientdata started
(11:44:00)Word Hours Access Restrictions ok
(11:44:00)startup ok
(11:44:00)logon ok
(11:44:04)CLIP=
(11:44:04)cmdline ok
(11:44:04)logonsession progressing 1
(11:44:04)onlyonesession ok
(11:44:04)security ok
(11:44:05)universalprinter/webprint started
(11:44:05)firewall ok
Steve
(11:44:00)logonsession started
(11:44:00)webime started
(11:44:00)USERDOMAIN ok
(11:44:00)groups ok
(11:44:00)currentuser ok
(11:44:00)SESSION=Session#197
(11:44:00)webclientdata started
(11:44:00)Word Hours Access Restrictions ok
(11:44:00)startup ok
(11:44:00)logon ok
(11:44:04)CLIP=
(11:44:04)cmdline ok
(11:44:04)logonsession progressing 1
(11:44:04)onlyonesession ok
(11:44:04)security ok
(11:44:05)universalprinter/webprint started
(11:44:05)firewall ok
Steve
Re: random crashes of svcr.exe -black screen on user
Guys.
We need to put some serious efforts on getting rid of this issue. Got another one too.
Another thing, when this happens, as I stated before, we need to remote desktop to the server in order to LogOff user, since their session is kept for 30 minutes as per our configuration, and if they just get out and back again, they go back to the black screen. One thing that could help in this concern, would be to have available a LogOff button on the HTML5 Top Menu, as it seems to be the only thing that shows up when the black screen happens. This way the users could be instructed to LogOff themselves through the Top Menu and try again.
Looking forward to hearing from you.
Ivan
We need to put some serious efforts on getting rid of this issue. Got another one too.
Another thing, when this happens, as I stated before, we need to remote desktop to the server in order to LogOff user, since their session is kept for 30 minutes as per our configuration, and if they just get out and back again, they go back to the black screen. One thing that could help in this concern, would be to have available a LogOff button on the HTML5 Top Menu, as it seems to be the only thing that shows up when the black screen happens. This way the users could be instructed to LogOff themselves through the Top Menu and try again.
Looking forward to hearing from you.
Ivan
Re: random crashes of svcr.exe -black screen on user
Thanks for looking into this guys. I've had a couple of black screens recently.Iv4anGB wrote: ↑Sat Sep 23, 2017 10:58 amHi John.
Thank you very much for the reply.
In my case, regarding the HTML5 Top Menu, it will be work around. Thanks for the idea.
Regarding my configuration and applications published, I am afraid I will disapoint you, since I am not publishing only one application.
Here is the information you requested:
Last edited by JaysonKi on Mon Jun 24, 2019 1:47 pm, edited 3 times in total.
Re: random crashes of svcr.exe -black screen on user
Another one stopped to firewall and not continue to WUSER check:
(10:04:03)logonsession started
(10:04:03)webime started
(10:04:03)USERDOMAIN ok
(10:04:03)groups ok
(10:04:03)currentuser ok
(10:04:03)SESSION=Session#174
(10:04:03)webclientdata started
(10:04:03)Word Hours Access Restrictions ok
(10:04:03)startup ok
(10:04:03)logon ok
(10:04:07)CLIP=
(10:04:07)cmdline ok
(10:04:07)logonsession progressing 1
(10:04:08)onlyonesession ok
(10:04:08)security ok
(10:04:08)universalprinter/webprint started
(10:04:08)firewall ok
Kind regards,
Steve
(10:04:03)logonsession started
(10:04:03)webime started
(10:04:03)USERDOMAIN ok
(10:04:03)groups ok
(10:04:03)currentuser ok
(10:04:03)SESSION=Session#174
(10:04:03)webclientdata started
(10:04:03)Word Hours Access Restrictions ok
(10:04:03)startup ok
(10:04:03)logon ok
(10:04:07)CLIP=
(10:04:07)cmdline ok
(10:04:07)logonsession progressing 1
(10:04:08)onlyonesession ok
(10:04:08)security ok
(10:04:08)universalprinter/webprint started
(10:04:08)firewall ok
Kind regards,
Steve
Re: random crashes of svcr.exe -black screen on user
Hello,
Let's try to complete this difficult issue.
It is difficult because we cannot reproduce it.
So, we cannot identify accuratly what is the specific piece of code which create, in your enviroment, the crash of logonsession.exe (started by svcr.exe)
However:
One thing that could help in this concern, would be to have available a LogOff button on the HTML5 Top Menu, as it seems to be the only thing that shows up when the black screen happens. This way the users could be instructed to LogOff themselves through the Top Menu and try again.
This is very easy to do.
Use the HTML5 Top Menu Tile of the AdminTool Web tab.
Add one application
This application shall be:
C:\Program Files (x86)\TSplus\UserDesktop\files\runlogoff.exe
No need to restart the web server.
Let me try to explain you exactly what cause the problem:
You are publishing one simple application (I am nearly 100% sure of that).
If such specific case, logonsession.exe is entering into a loop waiting for the event:
Is the application closed by the user (YES/NO)
IF YES: Logoff
IF NO: continue to wait
In you specific case, this event, sometime, is not detected.
The application has been closed by the user BUT
- The check of the event creates a memory leak and SVCR.exe crash
Because the application is close, when the user reconnect he see nothing (black screen).
We will double check again to look at our code inside this specific loop.
Hopefully we will be able to avoid the crash but I am not sure that we can do it.
For you infromation we will publish very soon the release 10.50
Logonsession.bin has been rewrite in a way which will possibly improve this kind of questions but this was not the goal our development team did have. However, this would possibly be the solution for your case.
Can you give me 2 informations:
1) What is the OS of your server?
2) What is the application you are publishing?
Last comment.
I know that you will not like this work around but it is a simple solution to fix this issue.
Instead of publishing your application, publish also the Floating Panel.
Doing so,
1) You will use a different part of logonsession.exe code and you will no more use the loop waiting for the application to close
2) The user will alway see the Logoff button
Kind regards
John
Let's try to complete this difficult issue.
It is difficult because we cannot reproduce it.
So, we cannot identify accuratly what is the specific piece of code which create, in your enviroment, the crash of logonsession.exe (started by svcr.exe)
However:
One thing that could help in this concern, would be to have available a LogOff button on the HTML5 Top Menu, as it seems to be the only thing that shows up when the black screen happens. This way the users could be instructed to LogOff themselves through the Top Menu and try again.
This is very easy to do.
Use the HTML5 Top Menu Tile of the AdminTool Web tab.
Add one application
This application shall be:
C:\Program Files (x86)\TSplus\UserDesktop\files\runlogoff.exe
No need to restart the web server.
Let me try to explain you exactly what cause the problem:
You are publishing one simple application (I am nearly 100% sure of that).
If such specific case, logonsession.exe is entering into a loop waiting for the event:
Is the application closed by the user (YES/NO)
IF YES: Logoff
IF NO: continue to wait
In you specific case, this event, sometime, is not detected.
The application has been closed by the user BUT
- The check of the event creates a memory leak and SVCR.exe crash
Because the application is close, when the user reconnect he see nothing (black screen).
We will double check again to look at our code inside this specific loop.
Hopefully we will be able to avoid the crash but I am not sure that we can do it.
For you infromation we will publish very soon the release 10.50
Logonsession.bin has been rewrite in a way which will possibly improve this kind of questions but this was not the goal our development team did have. However, this would possibly be the solution for your case.
Can you give me 2 informations:
1) What is the OS of your server?
2) What is the application you are publishing?
Last comment.
I know that you will not like this work around but it is a simple solution to fix this issue.
Instead of publishing your application, publish also the Floating Panel.
Doing so,
1) You will use a different part of logonsession.exe code and you will no more use the loop waiting for the application to close
2) The user will alway see the Logoff button
Kind regards
John
Re: random crashes of svcr.exe -black screen on user
Hi John.
Thank you very much for the reply.
In my case, regarding the HTML5 Top Menu, it will be a great work around. Thanks for the idea.
Regarding my configuration and applications published, I am afraid I will disapoint you, since I am not publishing only one application.
Here is the information you requested:
1) What is the OS of your server?
Windows Server 2012R2
2) What is the application you are publishing?
Floating Panel and 2 .NET applications.
So, your last advice about also publishing the Floating Panel doesn't apply, since this has been the case from the beggining. All crashes we have experienced were always with the Floating Panel and a couple more applications published.
If you would like me to test any scenario, let me know.
Best.
Ivan
Thank you very much for the reply.
In my case, regarding the HTML5 Top Menu, it will be a great work around. Thanks for the idea.
Regarding my configuration and applications published, I am afraid I will disapoint you, since I am not publishing only one application.
Here is the information you requested:
1) What is the OS of your server?
Windows Server 2012R2
2) What is the application you are publishing?
Floating Panel and 2 .NET applications.
So, your last advice about also publishing the Floating Panel doesn't apply, since this has been the case from the beggining. All crashes we have experienced were always with the Floating Panel and a couple more applications published.
If you would like me to test any scenario, let me know.
Best.
Ivan