Symptom
- After activating SNC in RFC destination type 3 (ABAP Connection), the 'Authorization Test' & 'Remote Logon' are returning message: "An error occurred while making a Remote Function Call.".
- The runtime error CALL_FUNCTION_SNC_NAME_NOT_FND is raised in the target system:
-
Category Internal error
Runtime Errors CALL_FUNCTION_SNC_NAME_NOT_FND
Application Component BC-MID-RFC
...
-------------------------------------------------------------------------------------
|Short Text |
| An error occurred while making a Remote Function Call. |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|What happened? |
| Sysid "<System ID>" in target system in table SNCSYSACL is not allowed. SNC |
| name="<SNC name>" |
-------------------------------------------------------------------------------------
-
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- NetWeaver Application Server ABAP
- ABAP Platform
Product
Keywords
CALL_FUNCTION_SNC_NAME_NOT_FND, An error occurred while making a Remote Function Call, SNC, Connection Test, Authorization Test, Remote Logon, RFC system error: An error occurred while making a Remote Function Call. , KBA , BC-MID-RFC , RFC , BC-SEC-SNC , Secure Network Communications , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.