PSM SSMS v20.2.1 Error Timeout

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM SSMS v20.2.1 Error Timeout

L4 Transporter

Hi Everybody,

 

I've been setting up the SSMS version 20.2.1 using this guide ( https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pasimp/psm_ssms.htm?tocpath=Administrator%7CComponents%7CPrivileged%20Session%20Manager%7CPSM%20Connectors%7CDatabases%7C_____3#Connecti )

 

And the result is unsuccessful, I've set the timeout up to 5000000 milli second

 

Field_Content_versions_oct20__068Vy00000bisaWIAQ.pngBelow is the error log of the PSM :

[17/06/2025 | 17:25:47] | :: | PSMSR1245W Connector deployment completed with errors. One or more connectors may not be deployed correctly.

 

[17/06/2025 | 17:35:03] | :: | PSMSR948W [95c8e02b-337a-4be3-b0ef-97f1764250d2] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 5). Reason: 946E [95c8e02b-337a-4be3-b0ef-97f1764250d2] Session keeper logoff timeout reached while waiting for the session to logoff. (Session id: 5)

 

[17/06/2025 | 17:35:04] | :: | PSMSR126E [95c8e02b-337a-4be3-b0ef-97f1764250d2] Failure occurred while handling session. PSMSR605E [95c8e02b-337a-4be3-b0ef-97f1764250d2] Error occurred while waiting for the dispatcher to communicate (Error details: [PSMSR606E [95c8e02b-337a-4be3-b0ef-97f1764250d2] Timeout occurred while waiting for a specific component to end]) (Codes: -1, -1)

 

[17/06/2025 | 17:35:52] | :: | PSMSR1245W Connector deployment completed with errors. One or more connectors may not be deployed correctly.

 

If I login directly without using PVWA, I can logon successful without writing the hostname in "Host name in certificate" & "Trust server certificate" is unchecked

 

Please help

3 REPLIES 3

L2 Linker

did you read the known issues?

By default, when opening SQL Server Management Studio, two windows are created – Editor and Object Explorer. The Object Explorer window requires credentials.

  • WorkAround: When the editor window is in focus, press ALT+Q+O; the Object Explorer window will be auto-authenticated.

 

did you read the known issues?

By default, when opening SQL Server Management Studio, two windows are created – Editor and Object Explorer. The Object Explorer window requires credentials.

  • WorkAround: When the editor window is in focus, press ALT+Q+O; the Object Explorer window will be auto-authenticated.

 

Hi @Martin Topgaard​ ,

 

My case has resolved by pressing ALT + Q + O

Field_Content_versions_oct20__068Vy00000fjQ0LIAU.png

  • 281 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!