Craig, Scott,
Thanks for your answers, I could identify the problem and it's not uttsc
/ SRS related.
SRS did its job well by returning error code 5 as another debug (and
faulty) script tried to connect to the same session.
Thank you for your help.
Regards,
Vincent.
Le 26/03/2013 00:39, Craig Bender a écrit :
If you log into a TS session that up from a "different" device,
Windows will terminate the connection to where it was displaying, i.e.
the "WINSTA", and redirected to the new WINSTA. Windows isn't
complaining, it's informing the old WINSTA's client why it ended that
WINSTA. Same client, same user, nothing would happen.
If they were all using the same Windows user name and password, and
the TS settings were changed to "Limit users to one session" (which is
the the default), each time a new kiosk session started, it will cause
the previous to end, due to the above. This would look like all the
kiosk sessions crashed, but in reality, it's just moving from one to
the next, to the next, to the next, etc.
If that error code isn't coming from uttsc, then it would be coming
from their kiosk script, kiosk.sh.
On 3/25/13 4:29 PM, Nishimura, Scott L (ESS) wrote:
Craig,
But should that action produce an error? From Windows'
standpoint, that's a legal operation. It just means that the user has
accessed a locked session [possibly from a different TC but not
necessarily so].
When you wrote "same account", do you mean the SRS utku account or
the Windows account? I assume it's the latter. The scenario I'm
envisioning is a user logs into Windows via a TC, locks his session,
them comes back in to Windows. Windows shouldn't complain because he
provided the correct credentials. I don't see why uttsc would
complain either. I didn't think uttsc could see that far into the
process.
Scott
-----Original Message-----
From: sunray-users-boun...@filibeto.org
[mailto:sunray-users-boun...@filibeto.org] On Behalf Of Craig Bender
Sent: Monday, March 25, 2013 3:53 PM
To: SunRay-Users mailing list
Subject: EXT :Re: [SunRay-Users] [SRSS 5.4] All Kiosk sessions
crashed at once
Error 5 is that some one else logged into a WTS session with the
same account as one that is active. Do all the Kiosk instances use
the same username/password? Did you happen to change the TS session
properties at all?
On 3/25/13 2:57 PM, Vincent Sourin wrote:
Hello Everyone,
This evening all our kiosk sessions have crashed with the same error
message :
kioskcrit: [ID 702911 user.notice] Info: critical application kiosk.sh
(pid=27667) exited with non zero status: 5
Actually, all these sessions uses a very basic custom Kiosk script
which only called uttsc binary depending on the user. So I assume that
the exit code comes from uttsc.
This script runs without any problem since 2 years now (with previous
SRSS versions) so I don't think the problem comes from the script
itself.
Does anyone know where I could find uttsc exit codes so I can identify
the root cause of this problem ?
Thank you in advance.
Best Regards,
Vincent.
-
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
