- 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.
04-02-2019 01:04 AM
it's very weird i got this error when initialize SSH connection over PSM. But with the same PSM server, RDP connection over PSM works well.
i have checked PSMConnect PSMAdminConnect startup commands, folder permission, RD Access settings, no idea what to do next.
the brief log is like:
PSMSR020I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Received password properties successfully (Safe: S-SecSvcPlat-Dow, Folder: Root, Object: Operating System-UnixviaSSH-test.unix.com-testacct) (Diagnostic information: 1)
PSMSR021I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Received password content successfully (Safe: S-SecSvcPlat-Dow, Folder: Root, Object: Operating System-UnixviaSSH-test.unix.com-testacct)
PSMSR009I Privileged Session Manager exception occurred. PSMSR768E [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Failed to find file category [PSMRemoteMachine] in the account. (Codes: -1, -1)
PSMSR009I Privileged Session Manager exception occurred. PSMSR768E [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Failed to find file category [LimitDomainAccess] in the account. (Codes: -1, -1)
PSMSR174I Starting configuration management operation (operation: lock entities cache for read)
PSMSR175I Configuration management operation ended successfully (operation: lock entities cache for read)
PSMSR174I Starting configuration management operation (operation: release entities cache lock (read))
PSMSR175I Configuration management operation ended successfully (operation: release configuration manager lock (read))
PSMSR572I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Attempting to add supported capabilities to session
PSMSR425I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] No policy specific settings were specified for capability [LogonAccount]. Using default settings
PSMSR566I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Attempting to add [LogonAccount] capability to the session capabilities' manager
PSMSR567I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Successfully added [LogonAccount] capability of type [4] to the session capabilities' manager
PSMSR1141I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Creating capability [SSHPasswordHiding] with default implementation.
PSMSR567I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Successfully added [SSHPasswordHiding] capability of type [4] to the session capabilities' manager
PSMSR573I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Successfully added supported capabilities to the session. Total number of session capabilities: [7]
PSMSR936I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] RemoteApp user experience is enabled for this session
PSMSR009I Privileged Session Manager exception occurred. PSMSR768E [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Failed to find file category [ExtraPass1Safe] in the account. (Codes: -1, -1)
PSMSR769I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Logon account file category is missing. Reason: [PSMSR768E [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Failed to find file category [ExtraPass1Safe] in the account.]
PSMSR772I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Logon account capability is enabled but is not defined for the target account.
PSMSR049I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Preparing metadata PSMRecordingEntity
PSMSR049I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Preparing metadata EntityVersion
PSMSR049I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Preparing metadata TicketID
PSMSR364I [4a60fa9d-96e9-4d0b-9538-28b20a2aedc3] Attempting to attach by image name [PSMInitSession.exe]
PSMSC158I There are 7 processes detected in session of Id 14.
PSMSC001E Session common exception occurred. PSMSC036E No Process was found for image [PSMInitSession.exe], session 14 (Codes: -1, -1)
PSMSC158I There are 8 processes detected in session of Id 14.
PSMSC001E Session common exception occurred. PSMSC036E No Process was found for image [PSMInitSession.exe], session 14 (Codes: -1, -1)
PSMSC158I There are 7 processes detected in session of Id 14.
04-25-2019 05:42 PM
I finally resolve the issue by myself.
Found that the hardening script change the default permission of several executables under system32 folder, after I revert them with default permission, OS can launch those corresponding exe.
We have 4 PSMs, hardening was performed against 2 so they were having issue. Another 2 always work because we don't harden them.
04-02-2019 01:29 AM
i have tried before posted this question, it didn't work.
as mentioned, RDP connection is working, v.s. SSH is not.
04-03-2019 03:13 AM
Does *any* SSH connection work... meaning do all your Unix/Linux accounts (try with different vault users and different target machines) have the same problem?
04-03-2019 06:18 PM
yes, we have 4 PSM servers in the same OU the same subnet. 2 of them work well, another 2 don't.
04-25-2019 02:17 PM
Hi Pyu,
Could you please let me know if the above issue has been resolved from your side or not. If yes then kindly let me know the procedure as we are also facing the same issue for the SSH connection.
Thanks in Advance,
Regards,
Dhurjati
04-25-2019 05:42 PM
I finally resolve the issue by myself.
Found that the hardening script change the default permission of several executables under system32 folder, after I revert them with default permission, OS can launch those corresponding exe.
We have 4 PSMs, hardening was performed against 2 so they were having issue. Another 2 always work because we don't harden them.
04-25-2019 05:57 PM
Hi Pyu,
Thanks for your response. Could you please let me know if you have received this error after PSM hardening of the PSM. Also kindly let us know which were those executable files which you have changed the permissions of it.
Regards,
Dhurjati
04-25-2019 06:00 PM
cmd.exe is one, I cannot remember the name of another one. If you are familiar with Process Monitor tool, the "access denied" error can be easily traced.
10-16-2019 08:24 AM
Hi Pyu and Dhurjati,
We are also facing same issue.Kindky let us know the solution to resolve this.
Thanks.
10-16-2019 05:46 PM
first, you may check your hardening script to unblock SSH executable s.
second, SSH initiation would launch a couple of Windows builtin commands, make sure that your PSMApp accounts have enough privilege in system32 folder
09-11-2023 09:31 PM
Hi Ankush, this link isn't functional. do you have any alternate working link ?
09-12-2023 05:11 AM
Hi @Amit Maharana
It seems article 00003306 was archived as no longer accurate/relevant.
However, from a quick search in the community, I've located the below articles that may be relevant to your issue:
I hope this helps!
Thanks,
Gil
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!

