Skip to Content

RFC Server with SAPNCo 3.0.18 - No broken connection status anymore?

Feb 21, 2017 at 07:57 AM


avatar image
Former Member

Hi all,

we are using SAPNCo for a long time in a really big environment.

We had some trouble with broken connections before, if NCo acts as RFCServer. This happens if something between the SAP system and the SAPNCo system (aka the network) failed. Because this is not often the case we had no big deal.

We updated from 3.0.15 to 3.0.18 some weeks ago, because the additional connection ping that was described in Change History.

But now the problem seems to be even bigger. One of our SAP machines restarted every Sunday.

With Version 3.0.15 SAPNCo recognized the broken connection and reconnects.

With the new Version 3.0.18 SAPNCo does not show any action - no event and no reconnect. So we have to restart the SAPNCo part to establish the connections.

Is there any new parameter to set with V3.0.18?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers