search cancel

After upgrading to CA PAM 4.1 login through the PAM Client returns to login screen


Article ID: 242988


Updated On:


CA Privileged Access Manager (PAM)


After the upgrading to CA PAM v 4.1, login through the client results in a blank screen instead of the Dashboard and after a few seconds the Windows closes and the initial PAM Client login screen is back

The following error is present in the CA PAM Client logs

2022-05-30 12:42:08 ERROR - Error unlocking file [RMI TCP Connection(2)-]
java.nio.channels.ClosedChannelException: null
 at ~[?:1.8.0_322]
 at Source) ~[updater__V4.1.0.81.jar:?]
 at Source) ~[updater__V4.1.0.81.jar:?]
 at Source) ~[updater__V4.1.0.81.jar:?]
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_322]
 at sun.reflect.NativeMethodAccessorImpl.invoke( ~[?:1.8.0_322]
 at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:1.8.0_322]
 at java.lang.reflect.Method.invoke( ~[?:1.8.0_322]
 at sun.rmi.server.UnicastServerRef.dispatch( ~[?:1.8.0_322]
 at sun.rmi.transport.Transport$ ~[?:1.8.0_322]
 at sun.rmi.transport.Transport$ ~[?:1.8.0_322]
 at Method) ~[?:1.8.0_322]
 at sun.rmi.transport.Transport.serviceCall( ~[?:1.8.0_322]
 at sun.rmi.transport.tcp.TCPTransport.handleMessages( ~[?:1.8.0_322]
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0( ~[?:1.8.0_322]
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0( ~[?:1.8.0_322]
 at Method) ~[?:1.8.0_322]
 at sun.rmi.transport.tcp.TCPTransport$ [?:1.8.0_322]
 at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_322]
 at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_322]
 at [?:1.8.0_322]
2022-05-30 12:42:08 INFO  - Correct application closing. All instances are closed [RMI TCP Connection(2)-]


Observed in CA PAM 4.1. Other releases may be affected as well


One of the possible causes for this behavior is the Antivirus software running in the CA PAM Client workstation preventing it from operating properly


Disable Antivirus operation or, since this is no likely possible, create an exception for the CA PAM Client binaries and installation and operation folders (generally  C:\Program Files (x86)\CA PAM Client or C:\<user_home_directory>\CA PAM Client)