Views:
Behavior:
The Desktop Apps (most likely the Import module) are not able to connect to DocuWare, even though a connection can and is established.
The following DocuWare versions could be affected: 7.1 / 7.2 / 7.3

 
Solution:
This behavior is most likely caused by missing parts for TLS 1.2 in the registry.
Since DocuWare version 7.2 
TLS 1.0 is not supported anymore .

Please check if the following part in the registry is empty:
"
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols"

If the registry path is empty, please import the following file (the file contains parts of registry entries).
The import of this file is not going to delete any other entries that are already present in this registry folder.
Please note that it is going to replace any key with the same name in the folder "TLS 1.2" and its sub folders.

After the import the registry should look like this:
"Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2"

Now please restart the Desktop Service.

If the following steps did not resolve the issue, please create debug logs of the DocuWare Desktop App using the following KBA, and forward it to DocuWare Support.
Comments (1)
  • The same issue with occur with the Fortis to DocuWare migration tool. If TLS 1.2 is not properly set up in the registry, it will fail.  This solution fixed it.

    The logs and the error message on the screen read as follows:

    This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.