K2 Connect connection-related errors
kbt135403
PRODUCTK2 connect 4.7
BASED ONK2 connect 4.7
TAGSK2 SmartObject Integration
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
Process instances which execute a K2 Connect SmartObject intermittently get connection-related errors.
For example:
- Type 'ERPConnect.CommunicationException' in Assembly 'ERPConnect35, Version=4.39.4.3, Culture=neutral, PublicKeyToken=737201975e95eeee' is not marked as serializable.
-
RfcInvoke failed(RFC_INVALID_HANDLE): Invalid RFC connection handle: 486516512;
-
RfcInvoke failed(RFC_COMMUNICATION_FAILURE):
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR program state check for conversation 82710016
TIME Tue Aug 15 11:22:41 2017
RELEASE 721
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 471
MODULE r3cpic.c
LINE 6078
DETAIL called function STSEND in state state=BUFFER_DATA2
COUNTER 297
- RfcInvokeFailed(RFC_INVALID_HANDLE): An invalid handle was passed to the API call;