SAP Knowledge Base Article - Preview

2458553 - max no of 100 conversations exceeded while using SAP NCo API

Symptom

The .Net applications which maintain RFC communication via NCo API with ABAP systems are failing.

The traces (e.g. dev_nco_rfc.log) show errors with max no of 100 conversations exceeded.

e.g.:

"...
message: Connect to SAP gateway failed
Connection parameters: TYPE=B DEST=<Java Rfc client> MSHOST=mshost.sample.com MSSERV=sapmsSID R3NAME=SID GROUP=PUBLIC PCS=1

LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       max no of 100 conversations exceeded
..."


Read more...

Environment

.Net application which uses NCo API to send/retrieve information to/from NW AS ABAP system.

Keywords

max, 100, 200, conversations, exceeded, RfcException, gateway, RFC_FAILURE, RFC_ERROR_COMMUNICATION, CPICMaxConnections, CPIC_MAX_CONV , KBA , BC-MID-CON-NCO , SAP .Net Connector , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.