RFC with SNC ends with dump CALL_FUNCTION_SNC_NAME_NOT_FND

[former_member246738]

Hi All,

Iam trying to create a type 3 RFC between 2 systems based on NW 7.4 SPS12. Kernel patch is 300. Connection test without activation of SNC works perfectly. However, when I activate SNC, connection test ends with the message " An error occurred while making a remote function call". In the target system the Short dump with the title CALL_FUNCTION_SNC_NAME_NOT_FND occurs. The dump reads as follows:

Short Text

    An error occurred while making a Remote Function Call.

What happened?

    Sysid "XXX     " in target system in table SNCSYSACL is not allowed. SNC

    name="p:SAPServiceXXX@CORP.XXX.COM"

What can you do?

    Note which actions and entries caused the error to occur.

    Consult your SAP administrator.

    Using transaction ST22 for ABAP dump analysis, you can view, manage,

    and retain termination messages for longer periods.

Error analysis

    A Remote Function Call was made and the SNC connection (Secure Network

    Communications) was used. In this case, a check is performed in the

    target system to see whether an entry with the SNC name, SNC ID and the

    RFC type of the original system exists in the table SNCSYSACL and if

    this entry is activated for RFC.

    This was not the case.

    The following information was used to search SNCSYSACL: Type.....

    (Field SNC-TYP)....>E<

    System ID.(Field SNC-SID)....>XXX     <

    SNC name..(Field SNC-PNAME)..>p:SAPServiceXXX@CORP.XXX.COM<

How to correct the error

    You must make a corresponding entry (including SNC name and system ID

    of the source system) in table SNCSYSACL of the target system and then

    mark it for use with RFC.

Of course, the solution of adding an entry to the table SNCSYSACL also does not help. I have done this using tcode SNC0.

Any inputs will be highly appreciated.

Regards

Joyee

[Sriram2009 · Accepted solution]

Hi

Could you share the target system version details?

Regards

SS

[former_member246738 · Accepted solution]

The target system is SRM 7.0 EHP3, based on NW 7.4 SPS12. Kernel patch level is 300.

[isaias_freitas · Accepted solution]

Hello Joyee,

I assume that you have added the (correct) entry at the table SNCSYSACL at the target system, right?

(it doesn't hurt to ask! )

You will be able to see at which work process the dump was raised at the "system environment" section of the dump.

Please share the entries you see at the corresponding dev_wXX file around the time of the dump.

Regards,

Isaías

[former_member246738 · Accepted solution]

Hi Isaias,

Well, I did add the entry in SNCSYSACL. Unfortunately, there is no info about the workprocess in the system information part of the dump. See this here:

Application server... XXXXXXXX

Network address...... xx.xx.xx.xx

Operating system... Windows NT

Release.............. 6.3

Hardware type....... 4x AMD64 Level

Character length..... 16 Bits

Pointer length........ 64 Bits

Work process number... 4

Shortdump setting. full

Database server... XXXXXXXX

Database type..... MSSQL

Database name..... XXX

Database user ID xxx

Terminal.......... XXXXXXX

Character set C

SAP kernel....... 742

Created on....... Oct 30 2015 17:22:51

Created at....... NT 6.1 7601 x86 MS VC++ 16.00

Database version SQL_Server_9.00

Patch level....... 300

Patch text.......

Database............. MSSQL 9.00.2047 or higher

SAP database version. 742

Operating system... Windows NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT

6.3

Memory consumption

Roll.... 0

EM...... 1497472

Heap.... 0

Page.... 0

MM used. 1300768

MM free. 193344

Regards

[isaias_freitas · Accepted solution]

Hello Joyee,

Actually, there is .

Work process number... 4

So, the dump was raised at the work process 4. You can share the entries at the dev_w4 trace file of the instance where the dump was created.

You could also "zip" the trace file and attach it to this thread.

We would need at least the entries around the timestamp of the dump (e.g., 50-100 lines before and after the timestamp).

Regards,

Isaías

[former_member246738 · Accepted solution]

Hi Isaias,

The issue is now resolved. I had raised a message with SAP and they told me to bump up the trace levels for component security. In the detailed trace I saw the line: "dy_snccheck: R/3 RFC(E) not accepted, pname not found in SNCSYSACL: p:SAPServiceXXX@CORP.XXX.COM.

So, on a hunch, I changed the SNCSYSACL entry via SNC0 to p:sapservicexxx@CORP.XXX.COM(basically all lowercase for sapservicesid) and it worked.

Regards

Joyee

[isaias_freitas · Accepted solution]

Hello Joyee,

Nice to hear the good news!

You can then mark this thread as answered .

Regards,

Isaías