- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-27-2019 05:22 AM
Hi All,
We have users reporting a "Timeout has expired. User is being disconnected" error while using PSM. I had to restart PSM service on all PSMs and then it went away. Also, checked PSM Trace file and found the below errors. Any help would be appreciated! Thanks!
Trace errors:
PSMSR913E Failure occurred while handling session. PSMSC050E Failed to get user token of TS session [42] (System error [2]: The system cannot find the file specified.) (Codes: -1, -1)
PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 1, Reason: PSMSR873E Failed to read parameters from vault file. Reason: PSMSR870E Failed to open vault file. Reason: PSMSR875E Open vault file operation failed (Diagnostic information: Safe=PSMSessions, Folder=Root, Object=dbb938f802869c091b7964368637f0534c551835). Reason: ITATS053E Object dbb938f802869c091b7964368637f0534c551835 doesn't exist.
06-28-2019 02:31 AM
Thanks @Himanshu Pandey
I checked the setting here: PVWA -> Administration -> Options-> PSM-> General Settings -> Server Settings. Both MaxConcurrentTSSessions & MaxConcurrentUploaders is both set to 10. Could this be the reason?
06-28-2019 02:36 AM
@Jelle Verreth Yeah mate. It does fix the issue temporarily.
06-28-2019 02:40 AM
Hi @Rohan Rajwade ,
Do you have gathered extra logs? Event viewer of the PSM, PSM erros, italog.log, ...
Anything that could help us. 🙂
Kind regards,
Jelle
06-28-2019 02:46 AM
I just did a restart of PSM server and the sessions looks good for now. will monitor and keep you posted
06-28-2019 03:29 AM
You need to check with OS team about allocation of RDS CALs, Is it really installed in the number which is required for concurrent sessions?
06-28-2019 03:29 AM
You need to check with OS team about allocation of RDS CALs, Is it really installed in the number which is required for concurrent sessions?
06-28-2019 03:35 AM
I checked that the license server is configured on the PSMs and it has sufficient RDS CALs (~2K). I have changed the setting MaxConcurrentTSSessions to 100 and MaxConcurrentUploaders to 50. Will keep monitoring this and keep you posted. Appreciate your help!
06-28-2019 03:46 AM
~2k for 1 PSM?? I doubt mate, it must be total pool you have, whereas I was stressing on the fact that how many CALs allocated per PSM or the PSM which is in subject.
06-28-2019 03:46 AM
~2k for 1 PSM?? I doubt mate, it must be total pool you have, whereas I was stressing on the fact that how many CALs allocated per PSM or the PSM which is in subject.
06-28-2019 04:19 AM
Yeah its a pool. PSMs refer to a single license server. is ther a way to find out how many CALs are allocated per PSM?
06-28-2019 04:43 AM
That's what I am referring continuously, get in touch with Windows folks who has allocated it or are not allocated at all?
06-28-2019 04:43 AM
That's what I am referring continuously, get in touch with Windows folks who has allocated it or are not allocated at all?
07-01-2019 02:47 AM
@Naveen Krishnappa We changed the MaxConcurrentTSSessions parameter in PVWA (Administration -> Options-> PSM-> General Settings -> Server Settings) from 10 to 50 and as of now, we are not getting any errors. WIll monitor this for a couple more days and keep you guys posted.
07-02-2019 12:04 AM
@Jelle Verreth It looks like changing MaxConcurrentTSSessions parameter has fixed the issue. Haven't seen the issue prop up in the last 3 days. appreciate your help! Also, Thanks to @Himanshu Pandey for his valuable inputs 🙂
08-26-2019 03:34 AM
Hello,
Is it normal that this error will crash the PSM and not start again? Have you experienced it? see below logs from PSM server
[23/08/2019 | 00:05:07] | :: | PSMSR948W [sessioncode] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 2). Reason: 947E [sessioncode] Failed to send stop command to the session keeper, session keeper is not accessible. (Session id: 2)
[23/08/2019 | 00:05:08] | :: | PSMSR059E Failed to wait for Internal jobs to exit. Error CASGE001E Thread pool failed to wait for threads
[23/08/2019 | 00:05:08] | :: | PSMSR036I Privileged Session Manager has been normally terminatedThank you.
Regards,
Krystian
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

