Troubleshooting -
TLS 1.2 is not activated for the .NET Framework

In rare cases, the .NET Framework might use a different TLS version by default than the Servicetrace server.

In this case, the following errors occur if the configuration with TLS 1.2 described in this document is used.

The Design or Workflow Studio reports the error

Service availability check failed. Uri not available: https://<host name>/. Error details: WebException with Status 'SendFailure'

When you test the connection from the Bot Configurator or the Bot service is executed, the error

The underlying connection was closed: An unexpected error occurred on a send.

is reported.

For more information, refer to the Microsoft documentation How to enable TLS 1.2 and Transport Layer Security (TLS) best practices with the .NET Framework.

There are two ways to correct this error: You can either change the configuration of the Servicetrace client applications or change the registry values on the server for the .NET Framework.

If the errors still occur, please also refer to Activating TLS 1.2 for WinHTTP.

Adjusting the configurations of the Servicetrace client applications (AppContext switches)

To change the configurations of the Servicetrace client applications, add the text

<AppContextSwitchOverrides value="Switch.System.Net.DontEnableSchUseStrongCrypto=false"/>

to the runtime section of the configuration files of the X1 Design/Workflow Studio, the X1 Bot/Robot, and the X1 Bot/Robot Configurator:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
        <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSchUseStrongCrypto=false"/>
    </runtime>
</configuration>

You can use any text editor to open the file for editing.

Then restart the X1 Design/Workflow Studio and X1 Bot/Robot Configurator, as well as the X1 Bot/Robot service, so that the changes take effect.

You will find the files in the following locations:

X1 Design Studio

<path to X1DesignStudio>\bin\X1DesignStudio.exe.config

e.g.

C:\Program Files\Servicetrace\X1DesignStudio\bin\X1DesignStudio.exe.config

Workflow Studio

<path to WorkflowStudio>\bin\WorkflowStudio.exe

e.g.

C:\Program Files (x86)\Servicetrace\WorkflowStudio\bin\WorkflowStudio.exe

X1 bot

<path to X1Bot>ServicetraceX1Bot.exe.config

e.g.

C:\Program Files\Servicetrace\X1Bot\ServicetraceX1Bot.exe.config

Robot

<path to Robot>\ServiceTracerAgent.exe

e.g.

C:\Program Files\ServiceTracer\Agent\ServiceTracerAgent.exe

Due to legacy reasons, the Robot is sometimes still referred to as an “Agent” internally at Servicetrace.

X1 Bot Configurator

<path to X1Bot>X1BotConfigurator.exe.config

e.g.

C:\Program Files\Servicetrace\X1Bot\X1BotConfigurator.exe.config

Robot Configurator

<path to Robot>\ServiceTracerAgentConfigurator.exe.config

e.g.

C:\Program Files\ServiceTracer\Agent\ServiceTracerAgentConfigurator.exe.config

Adjusting the registry values of the server

To set the required values in the registry, copy the following text to a file with the format .REG and save it on the server.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001

Next, double-click to execute the file. The values are then automatically adopted in the registry.

Afterwards, you can delete the .REG file.

Please restart your computer so that the changes to the registry take effect.