Message server query failed with return code -14

[#1]

Use SAP Business Connector 4.8.1

When SAP invokes an RFC with SAP Business Connector,

The following error is displayed in the SSAP Business Connector console.

Where can I find the cause related to Return Code -14 ?

2023-09-22 13:36:17,485 +0900 [B2B-SAP.0011.0001] BC HTTP Handler 111.111.111.111 | [JCoRFC] Message server query failed with return code -14: Logon group "SAP_HANA" is not RFC enabled at message server on host 10.11.11.11

[Ulrich_Schmidt1 · Accepted solution]

This is a known bug in early JCo versions, I think 3.1.2 or 3.1.3, so it looks like you did not yet install the latest "Service Release" on the SAP BC. See note 3346188. The current Service Release comes with JCo 3.1.8.

(And while you are at it, you should also install the latest "Core Fix". It has some useful updates e.g. for the latest TLS ciphers. See note 3304786.)

[Private_Member_667194 · Accepted solution]

I have updated both the service release and the core fix to the latest, but the same error appears in the console.

[Ulrich_Schmidt1 · Accepted solution]

Then we need an OSS ticket, so we can forward it to the Message Server Team. 😞

Workaround for now: use the direct App-Server Logon. (No load-balancing.)

[HAL9000]

"Logon group 'SAP_HANA' is not RFC enabled" means that this logon group was not set up by the administrator to be used for RFC logons. Only SAP GUI logons are allowed via this group.

If this configuration is a mistake and RFC logons via this logon group shall be permitted, an administrator needs to change the setting in transaction SMLG for that group "SAP_HANA" and tick the checkbox "Ext. RFC-enabled".

[Ulrich_Schmidt1]

This seems to be wrong. Gui-Groups (without the "Ext. RFC-enabled" flag activated), can also be used for RFC logon. (Just tested with latest Kernel release 917 and JCo 3.1.12) The flag "Ext. RFC-enabled" only has an influence on whether NAT works or doesn't work. See note 593058, point 4b.