User launches Controller client. User receives an error.
Example #1 (Controller 10.2.1):
An error occurred while trying to access the server
The underlying connection was closed: An unexpected error occurred on a send
There are several known causes for this error.
- See separate IBM Technote #0741571 for more examples.
This Technote specifically relates to the scenario where the Controller application server's website (IIS) required connection protocol(s) have been disabled.
In one real-life example, the third-party (IBM) tool 'IIS Crypto' had been used to lock down the webserver so that only a very few protocols were enabled:
Most importantly, TLS 1.0 and 1.1 had been disabled (forcing the application server to only accept TLS 1.2 connections).
Resolving The Problem
Fix (Modern versions of Controller)
Reconfigure the client device so that it forces .NET applications to use TLS 1.2.
- TIP: For instructions, see separate IBM Technote #883036.
Workaround (Old/unsupported versions of Controller)
Re-enable the relevant/required IIS communication protocols.
Was this topic helpful?
16 September 2020