Symantec Privileged Access Management

Tech Tip - CA Privileged Access Manager: Failed to initiate CA PAM Client session

By wonsa03 posted 04-10-2017 12:59 AM


CA Privileged Access Manager Tech Tip by Kelly Wong, Principal Support Engineer for 10th April 2017



Users remote access to a common Terminal Server and run CA PAM Client session. CA PAM Client session is locked to the user that initiated CA PAM Client session first.



Privileged Access Manager: 2.7, 2.8



CA PAM Client is installed by Windows Administrator and make available to all users. Hence, all users are initiating CA PAM Client from a common location.


When another user remote access to the Terminal Server and attempt to initiate CA PAM Client session from the same file directory, in parallel to another user, some files are locked and new session goes back to the first user:


c:\Program Files (x86)\CA PAM Client>classpath: updater__V2.8.0.0.jar;lib/log4j-1.2.15__V2.8.0.0.jar;lib/slf4j-api-1.7.12__V2.8.0.0.jar;lib/slf4j-log4j12-1.7.12__V2.8.0.0.jar
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=250m; support was removed in 8.0
2017-02-27 22:47:55 INFO - Application started with parameters [CAPAMClient.exe] [main]
2017-02-27 22:47:56 WARN - Can't update awtAppClassName, awtAppClassName [main]
2017-02-27 22:47:56 INFO - Free memory: 118956488 bytes [main]
2017-02-27 22:47:56 INFO - Available memory: 129761280 bytes [main]
2017-02-27 22:47:56 INFO - Maximum memory: 1037959168 bytes [main]
2017-02-27 22:47:56 TRACE - Client ROOT autodetected as C:\Program Files (x86)\CA PAM Client [main]
2017-02-27 22:47:56 INFO - Client ROOT set to C:\Program Files (x86)\CA PAM Client [main]
2017-02-27 22:47:56 DEBUG - Locking client instance: C:\Program Files (x86)\CA PAM Client\temp\.lock [main]
2017-02-27 22:47:56 DEBUG - Locking C:\Program Files (x86)\CA PAM Client\temp\.lock [main]
2017-02-27 22:47:56 INFO - Strating second instance [main] File is locked C:\Program Files (x86)\CA PAM Client\temp\.lock
at Source)
at Source)
at Source)
at Source)
at Source)
2017-02-27 22:47:56 INFO - Starting instance with params [CAPAMClient.exe] throught port 60605 [main]



The issue shall be addressed with CA PAM 3.0 release.