Universal AutoIT connector via a Thick client closes immediately after logging in successfully.

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

Universal AutoIT connector via a Thick client closes immediately after logging in successfully.

L3 Networker

Hi All,

Universal AutoIT connector to a DB via a Thick client closes immediately after logging in successfully.

 

Soon after logging in, the session closes almost immediately after the windows blue signing out animations finish. There are nothing much on the component logs.

There only a sessionkeeper log for the session ID which has only the below line

 PSMSK013I Start monitoring session state

 

The PSMConsole has the below log.

PSMSR948W [xxxxx] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 40). Reason: 946E [xxxxxx] Session keeper logoff timeout reached while waiting for the session to logoff. (Session id: 40)

 

I have tried increasing the below timeouts as per some articles I've seen:

PSM\Components\conf file to 30000 and the InitSessionTimeout to 30 to match.

SessionLauncherTimeout 30000

RecorderConnectionTimeout 30000

SessionKeeperConnectionTimeout 30000

 

Really appreciate any help on this.

1 accepted solution

Accepted Solutions

L3 Networker

Thanks @Uditha Arunasiri​  and @Shudansu Singh​ for your help. I have found the issue to be a PID change with the initial app client opening child processes. Found the fix here:

https://community.cyberark.com/s/question/0D52J00007QIVZGSA5/failed-to-send-pid-to-psm

 

Thanks again

View solution in original post

3 REPLIES 3

L4 Transporter

Hi @Jinal Jayawardhana​ ,

 

Other than the timeout mentioned above, try increasing the SessionKeeperShutdownTimeout as well. (Set to about 50000)

 

PVWA > Options > Privileged Session Management > General Settings > Session Settings > Advanced Settings

 

Allow approximately 10 minutes for the changes to take effect.

L1 Bithead

Check the Lock Application Window parameter set to No

L3 Networker

Thanks @Uditha Arunasiri​  and @Shudansu Singh​ for your help. I have found the issue to be a PID change with the initial app client opening child processes. Found the fix here:

https://community.cyberark.com/s/question/0D52J00007QIVZGSA5/failed-to-send-pid-to-psm

 

Thanks again

  • 1 accepted solution
  • 137 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!