Powershell scrip on entry
We find that PowerShell scripts that can be started from an entry by the user for various things in version 2025 give an error message but switching back to a 2024 version all just works.
I tested a simple script with this same behavior.
Script:
$remoteHost = "$HOST$"
$port = "$PORT$"
try {
$socket = New-Object System.Net.Sockets.TcpClient($remoteHost, $port)
Write-Host "Host is reachable.. You can connect."
}
catch {
Write-Host "Oepsssss."
}
Write-Host "Debug Info: remoteHost = $remoteHost, port = $port"
Select and execute this psscript via RightClick > Macros/Scripts/Tools on an Website entry with just http://www.google.com as input give below result in versions:
Version 2024.3.29:
Executing in Version 2025.1.27:
What could be the reason/cause of this? Setup/Parameters/PS changes?
1dab5bfe-e814-4fe3-be5a-255b6f21639a.png
a0ace094-8716-4661-9f39-98d7668b0547.png
All Comments (7)
Hello marcelgoossens2,
I have reproduced this issue and raised an internal ticket.
For the cause, I don't know yet, but I'll let you know as soon as I have more information.
Best regards,
Patrick Ouimet
Hi Patrick,
Is there perhaps already more information available about this? (problem persists even in the latest 2025 versions)
Regards, Marcel
Hello Marcel,
There is currently no estimated time of fix version on this internal ticket.
The development team is still working on it.
I'll inform you when it is fixed.
Best regards,
Patrick Ouimet
Fixed in 2025.2.14 ;-)
@Marcel G, are you sure? I've just upgraded to 2025.2.14 and I still have this issue.
Hello Marcel and Josh,
I checked our internal ticket, and no fixed version has been established yet.
We will repost the fixed version here.
Best regards,
Patrick Ouimet
Oops, I read under the latest release items at the bottom "Fixed winrm errors with remote tools" and from that I started a script which caused the previous message and it worked fine now, hence this response.
I now checked again and saw I executed this on a credential entry yesterday. Executing this script on a web entry does indeed still give this message.
Apologies for the confusion.