PowerShell entries open but dont run and close automatically
PowerShell entries open but dont run and close automatically
Hello,
At one location where RDM is deployed, the PowerShell (local) entries with embedded scripts wont open. The entry launches and the PowerShell window shows briefly, but then closes even though the option for 'no exit' is enabled. Is there a debug level or something similar that can be used to troubleshoot the issue? Using RDM 2024.2.19, and have tried different data sources, different power shell versions, with admin and non admin users. There are no events recorded in antivirus software or windows event logs. PowerShell scripts outside of RDM seem to launch ok, with the exception of an occasional prompt for bypassing execution policy.
Thanks
Joe
67343214-0110-4e19-87fa-c3db57478911.png
72e18a35-7347-420a-932f-1debd2fd2069.png
All Comments (10)
Hello,
Could you try using the Debug level set to 1 in the Profiling tool in RDM?
https://docs.devolutions.net/rdm/commands/help/support/profiler/
Do you get any relevant information?
Best regards,
Érica Poirier
Hi Erica,
This is all that shows in the profiler when launching a powershell entry. Debug level is set to 1.
Joe
8f3869ac-0570-4dfc-b1ca-487ee9ab250e.png
Hello,
Thank you for your feedback.
We suspect something related to the Terminal configuration on this Windows machine.
What value is set for the Terminal parameter on this machine?
Best regards,
Érica Poirier
2468036d-edd7-4fff-b571-5cfdc739df6e.png
Hi Erica,
The machine is Windows Server 2016, so it doesnt have that setting.
Joe
ab1cda61-aa87-49ae-8cec-347371690797.png
Hello,
I have been able to reproduce this behavior on a Windows Server 2016; I cannot reproduce it on a Windows Server 2022.
I have submitted a ticket to the developer team. We will post it here once a fix is available.
Thank you for being so patient.
Best regards,
Érica Poirier
ok great, thanks Erica
Is there any way to make it work? Server 2016 and RDM 2025.1.30 and same error. PowerShell session tab appears but remains empty and closes automatically after ~25 seconds.
The terminal parameter is specifically set to 'Classic'
There is no such problem in Server 2022 or Windows 10
Hello Meelis,
Thank you for your feedback.
The issue hasn't been fixed yet, but I have asked the developer team to increase the priority on our internal ticket. There is no other workaround.
Thank you for being so patient.
Best regards,
Érica Poirier
Hello,
We have fixed PowerShell (Local) entry not starting in Windows Server 2016, it will be available starting with version 2025.1.35.0 of RDM.
Regards,
Perfect, thank you Olivier.