The above error is caused since the logon to the first RDP session is in progress and a second RDP session to yet another Windows Server is initiated.
Release: 3.3.x, 3.4.x
Component: PRIVILEGED ACCESS MANAGEMENT
Product Engineering does not consider this as a product defect. The only resolution is to establish one RDP session, wait for the login to be completed, and only thereafter a new RDP session to any other Windows host is to be initiated. This problem happens only when the RDP sessions are performed for hosts that are on different pages in the Access Tab.
Steps to replicate this problem: (Assumption there are 100's of Windows hosts configured for automatic login using CA PAM)
1. Initiate an RDP session to a Windows host that is listed on page 1 in the Access Tab.
2. Before the login process completes, go the second page under the Access Tab.
2.1 Either go to a different page or filter the Windows hostname present on the first page itself and perform RDP.
3. Initiate an RDP session to yet another Windows host from the second page, the error message is encountered.