While running a GSX Robot User on the same host as GSX Monitor scanning ADFS, some processes may collide due to HTTPS traffic using different TLS (Transport Layer Security) protocol versions or ciphers, generating errors referring to the underlying connection being closed.
Follow this article for a workaround preventing interferences when running a GSX Robot User on the same machine as GSX Monitor.
- The underlying connection was closed: An unexpected error occurred on a send.
- Robot User(s) Unreachable
Failed to scan:
- Scenarioname on servername (serveralias) with the error:
'<<GUID> as '<...>' @ 'https://vmgregoire.ent.gsx.com:'>' is not reachable on port 8444: One or more errors occurred. -> An error occurred while sending the request. -> The underlying connection was closed: An unexpected error occurred on a send. -> There is no Runspace available to run scripts in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The script block you attempted to invoke was: $true
How to Solve the Issue
We strongly advise not to deploy a Robot User on the same machine running GSX Monitor.
If you have a GSX Monitor configuration with ADFS (Active Directory Federation Services) servers, the following workaround can resolve the unexpected errors:
- Stop GSX Monitor, including the background service if running.
- Navigate to the following directory:
- \GSX Monitor\Config\SKE\ADFS\
Observe that you no longer receive the unexpected GSX User Experience Manager alerts referencing to the underlying connection being closed.