Error in SM59 TCP/IP connection SERVER_EXEC after kernel upgrade to 215

[Former Member]

Hi

We recently upgraded our kernel to patch 215(NW 7.0)..We built the kernel by first taking the entire kernel stack( level 201)

and then patched it with dw, enserver, lib_dbsl, tp, r3trans, r3inlpgm, saposcol with level = 215 except for lib_dbsl, which is 214 and enserver which is 207...

After the upgrade to this new level, we have a SM59 TCP/IP SERVER_EXEC connection which calls an rfcexec program. (start on application server radio option), which has stopped working...

Now this RFC doesn't work anymore...

When we test it, it shows us the following:

Logon Cancel

Error Details Could not open file ../../SYS/exe/run/KERNELLIB/SEC.FILE/RFCEXEC.MBR

In the trace file, this is what shows up:

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3339

CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=223

CPIC program connection ended (read error)

Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1833

• Trace file opened at 20091121 125953 EST SAP-REL 700,0,215 RFC-VER nU 3 1079069

======> Could not open file ../../SYS/exe/run/KERNELLIB/SEC.FILE/RFCEXEC.MBR

ABAP Programm: RSRFCPIN (Transaction: SM59)

Called function module: RFC_PING

User: AGUPTA (Client: 300)

Destination: rfcexec (handle: 2, 26892245, {4B07B96E-F299-019B-E100-80000A36FF6D})

Any one has faced any issues like this??

Thanks

sap ques..

[Former Member · Accepted solution]

Hi sap ques,

as you wrote in the error already:

The file SEC is miising in your kernel ...

=> copy it from the old one and run an apply again ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[Former Member · Accepted solution]

Hi Volker

Thank you for the promt help.

But there is no SEC file even in my old kernel library, from which I can copy this one.

I am assuming that SEC is a PF, of which RFCEXEC is a Member.

How and where do I get this file from? We do not know where to copy this file from?

Isn't this SAP would keep in a kernel stack, if we download a full kernel stack?

Thanks

sap ques...

[volker_gldenpfennig · Accepted solution]

Hi sap ques,

this file is never in the kernel, as it is a security feature. If you do need that, you have to create that ... therefore, I'm pretty sure, that it is in the old kernel when you were using the same kernel release before. You can copy it over and good.

Otherwise, you have to create one with the proper contents yourself ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[Former Member · Accepted solution]

Hi Volker

I have a few other system where we have not yet applied the new kernel and the RFC works great.

But they also do not have SEC.FILE..

As far as I believe, the file is rfcexec.sec locacted inside .../../sys/exe/run.

I have compared the contents of the file between two system( one which is working and one which is broken)...

Have the same values of :

/F//U//T//S//C/*/O/ /

Not sure what's going on ?/

have opened up a message with SAP...

Thank you for your help

Thanks

Abhi

[volker_gldenpfennig · Accepted solution]

Hi sap ques,

I'm looking forward to the solution with SAP ... but to me, it needs to be the following with the later RFCEXECs (the very old ones had the check on the file missing)

CRTSRCPF FILE(krn/SEC)

EDTF FILE(krn/SEC) MBR(RFCEXEC)

Just this contents:

/U//C//T//F//O/ /S/*/

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi,

Just letting you know that I have recently installed a new Solution Manager NW 7 EHP1 system (distributed DB & CI) and have also encountered this issue. As yet I do not have a resolution but have logged a call with SAP. Will update when we have solved it.

Cheers,

Jim.

[Former Member]

Hello,

We also had this issue when we upgraded our kernel and all we did was change the Program name on the RFC itself. Instead of pointing to the kernel directory for the program name, we just entered in the program name on the RFC as RFCEXEC. That worked for us with the new kernel.

Hopefully that will be an easy fix, but not sure if this would apply to you.

[Former Member]

Hi,

I also resolved my issue by changing the way in which the program was called. Using Notes 94836 & 638701 I forced the RFC call to use the gateway instead of the work process on the local server. I suspected that my issue was being caused by a timeout rather than any incorrect program name. So I set parameter rfc/use_gwstart = 1 in my instance profile. Works like a charm.

Cheers,

Jim.

[Former Member]

Hi All

Yes, we alos resolved the issue by setting the profile parameter rfc/use_gwstart = 1 in our instance profile...

i think somehow in the new kernel it timeout while trying to use the wp to go out...so telling it explicitly to use the gateway works...Don't know why, but the solution works....

Thanks all