<{{Subtitle_Weight}} class="prominent-subhead {{Show_Subtitle}}"> {{Header_Subtitle}}

K2 Connect: RfcOpenConnection failed, max no of 200 conversations exceeded error appears

~~repeating-content.html~~
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.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

A process goes into an error state and the following error message appears:

"RfcOpenConnection failed(RFC_COMMUNICATION_FAILURE): LOCATION CPIC (TCP/IP) on local host with Unicode ERROR max no of 200 conversations exceeded."

Symptoms

After upgrading to K2 Connect 4.7, the connect service starts showing the following error intermittently:

"RfcOpenConnection failed(RFC_COMMUNICATION_FAILURE): LOCATION CPIC (TCP/IP) on local host with Unicode ERROR max no of 200 conversations exceeded" error.

In addition, it is confirmed that the SAP server has the "CPIC_MAX_CONV" connection set to more than 200.

Resolution

Please log a ticket with K2 Support to obtain the latest fix to resolve this issue.