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.

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 the Connection string needs to be limited to 13 characters. This need to be done in 2 two locations in K2 Management:

1. Environmental Library

2. Default String Connections inside the Workflow server tree

Examples:

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

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