- 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.
10-29-2024 10:11 AM
We are getting below errors whenever end users try to initiate the session and hit some keystrokes after initiating the session. However, after initiating new session again for same machine it doesn't throw same errors.
Our ShellPrompt setting is configured by default as shown here --> (.*)[>#\\$]$
End users' machines also prompt same prompt as we have defined in the setting under CC. We are perplexed why "Keystrokess Logging failed" error get shown in the logs.
However, we have seen the solution here related to prompt which are given below, but we want to know what may be other reasons beside shell prompt configurations? Anything else may be causing Keystrokes logging failed.
Errors:
| PSMIN035I Control character keystroke detected (Character values: [0xa;]), ignoring
[29/10/2024 | 01:14:01.306370] | :: | PSMIN035I Control character keystroke detected (Character values: [0xa;]), ignoring
[29/10/2024 | 01:14:02.209180] | :: | PSMSH007I Parameter [Password] was initialized with value [****]
[29/10/2024 | 01:14:27.592260] | :: | PSMIN035I Control character keystroke detected (Character values: [0xa;]), ignoring
[29/10/2024 | 01:14:27.688391] | :: | PSMSH003E PSMSSHClient exception occurred. Reason: 134E The session shell prompt did not match the configuration. This session continued without a detailed audit. (Codes: -1, -1)
[29/10/2024 | 01:14:27.688866] | :: | PSMPR077I Commands Access Control client is sending an error message : [134E The session shell prompt did not match the configuration. This session continued without a detailed audit.]
[29/10/2024 | 01:14:27.689061] | :: | PSMPR039I Sending data
[29/10/2024 | 01:14:27.689224] | :: | PSMPR040I Session index has been increased (new index: 2)
[29/10/2024 | 01:14:27.689371] | :: | PSMPR030I Protocol message prefix has been serialized. Serialized prefix length: 25.
[29/10/2024 | 01:14:27.689508] | :: | PSMPR056I Protocol message data has been serialized. Serialized data length: 29.
[29/10/2024 | 01:14:27.689644] | :: | PSMPR041I Encrypting the message before sending it. Total number of bytes to be encrypted: 55, Number of data bytes (without the message prefix): 29.
[29/10/2024 | 01:14:27.689833] | :: | PSMPR042I Message is being sent over the pipe channel (Pipe timeout: 500, Packet identifier: StartCommandRestriction)
[29/10/2024 | 01:14:27.690025] | :: | PSMPR048I Waiting for the following expected packets: ACK
Solution found links:
After PSM-SSH session is established, user needs to wait for 30s before they can enter the command
10-29-2024 01:19 PM
Hi @sanjay sah
Can you try with this on AuditShellPrompt --> (.*)[>#\\$\]]\s?$
11-06-2024 08:59 AM
Hi @sanjay sah
As it seems phenriquez provided an answer for your question, could you kindly share if this solution resolved your issue?
If so, could you please mark the answer as "Select as Best" to help other community members?
If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.
Thank you, Liad
11-06-2024 09:11 AM
Actually, as per our environment. Users are clicking on RDP file twice and it throws the shell prompt error. Its weird
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!

