- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
02-07-2024 05:28 AM
Exact error is below with attached screenshot.
PSM - Error on RDP connection: "Server Busy. This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and connect the problem."
02-07-2024 05:55 AM
what type of account are you trying to connect to? Does the connection work from the PSM to the target outside of Cyberark via RDP or another tool?
what happens when you following the instructions in the error?
-Matt
02-07-2024 06:42 AM
I haven't tried anything aside from deleting/recreating the account. I also mirrored the settings that I have from the working account with the failing account but still getting error. RDP will not work because this user is from external and not part of SYNLAB that's why he needs to do it from CyberArk. When clicking on switch to... it's not doing anything. Keep on coming back to this pop up.
02-07-2024 06:58 AM
what version are you using? I can see a similar error in 11.1 that's a known-issue. it could be this that you're seeing. From what I can find this was fixed in 11.3 and above.
Or you can try the following:
Issue: When the PSM server and the target are on Windows 2016 and "Always prompt for password upon connection" (in the GPO) is enabled, the user will receive the error "Server Busy. This action cannot be completed because the other program is busy". Choose 'Switch To' to activate the busy program and connect the problem. " and can't connect to the target
The same problem occurs if the account has an invalid password or empty password as well.
SOLUTION: Navigate to Computer Configuration | Administrative Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Security and then find the policy "Always prompt for password upon connection"
If the value is "Enable" or "Not configured" please change it to "Disable". Even if this value is set to "Not configured"
Run gpupdate /force and test again.
Let me know how it goes!
-Matt
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!

