No ratings

Sub-Workflow fails with error: An existing connection was forcibly closed by the remote host.

 

Sub-Workflow process fails with "1 Send failed with error: An existing connection was forcibly closed by the remote host."

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.

Issue

When trying to start/call a sub-workflow process from a main process, it fails with the following error:

1 Send failed with error: An existing connection was forcibly closed by the remote host.

1%20send%20failed%20with%20error

 

Symptoms

The main workflow will be unable to start any sub-workflow process and will be prevented from continuing further.

Resolution

 

This error was identified as a known issue and is being addressed in a future release of the K2 Product.

To prevent this error from occurring on any sub-workflow that is started, the characters in the 'Host' property inside Workflow Server and Workflow Management Server Connection strings needs to be limited to 13 characters or less.

 

This need to be done in 2 two locations in K2 Management:

1. Environmental Library

string1

 

 

2. Default String Table inside the Workflow server tree

string2

 

 

Examples:

Changed from:
Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=[ServerName].[domain].;Port=5252

Changed To:
Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=[ServerName];Port=5252

Labels: (1)
Version history
Last update:
‎10-18-2021 06:53 AM
Updated by: