- 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.
03-26-2020 05:59 AM
Log filed this error in PSMConsole log, :: | 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)
From session ID log,
PSMRD171W Microsoft C Runtime Libraries will not be copied to the target machine because files already exist. Reason PSMOS003E Failed to copy [C:\windows\SysWOW64\msvcp120.dll] to remote machine resource [\\<FQDN>\admin$\SysWOW64\msvcp120.dll] (System error [80]: The file exists.)
When I checked, MaxConcurrentTSSessions set to 100 for us.
Any solution
02-01-2023 07:30 AM
Another possible root cause is AppLocker. It may block certain processes which are required for the session to be established.
Check logs in the Event Viewer "Applications and Services\Microsoft\Windows\AppLocker ". Filter log to display only Critical, Warning and Error events and look for the full path of the application, which is being blocked and add it to PSMConfigureAppLocker.xml then re-run PSMConfigureAppLocker.ps1.
Pay attention to add new rule to correct path <InternalApplications> (for PSMConnect and PSMAdminConnect) or <AllowedApplications> (for PSMShadowUsers), check which user is used to run application and add the rule respectively. Most probably you'll need to adjust <InternalApplications>.
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!

