Hi
after upgrading to 2026.3.0 are my api endpoints there are using internal commands like get-psujob or invoke-psuscript started failing with this error
Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1789719790.110000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\client_channel.cc","file_line":3218,"referenced_errors":[{"created":"@1789719790.110000000","description":"failed to connect to all addresses","file":"..\..\..\src\core\lib\transport\error_utils.cc","file_line":165,"grpc_status":14}]}")
my set up is 2 PSU Servers running on IIS with a Netscaler LB in front
Seeing the same thing but with implicit secrets that one of our scripts call... Same IIS setup but no LB
Hello @jol and @Michael Taylor
Thank you for reporting this.
Since the issue started after upgrading to PSU 2026.3.0 and the failure is occurring when internal PSU commands attempt to communicate through gRPC, the most useful next step will be reviewing the PSU logs around the time of a failed request.
Could you please reproduce the issue once and send us the PSU logs from both IIS nodes covering that time window? Please include the approximate timestamp and time zone of the failed request.
For security, please do not post the complete logs publicly. You can send them directly to:
ruben.tapia@ironmansoftware.com
Please reference case #56321 in the message.
If possible, also let us know whether the same behavior occurs on both PSU nodes and whether the failure happens consistently or intermittently.
Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.
Best regards,
Ruben Tapia
I just want to point out, this is likely the same issue as this: All apps/scripts not working on 2026.3.0 - Devolutions Forum
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions
Hello @jol l and @Michael Taylor
Thank you, @Adam Driscoll for pointing us to the related report.
Best regards,
Ruben Tapia