SAPXPG command timeout

[Former Member]

We are getting the below error.  I havent found any specific note particular to CPIC return code 020, SAP return code 456.

This timeout is happening intermittently. I suspect it is an kernel Issue. But, however I dint find any spect note for my PL.

We are only Kernel 720 PL 300.

SAPXPG version is 720 PL 215.

R4  9 Communication error, CPIC return code 020, SAP return code 456

              R5  A > Conversation ID: 81130872

              R6  4 > CPI-C function: CMSEND(SAP)

              LC  2 Error 1006 when executing external command powershell.exe on %_TCPIP_%1 (xpgid=0,convid=.)

              R4  9 Communication error, CPIC return code 020, SAP return code 456

              R5  A > Conversation ID: 81129673

               R6  4 > CPI-C function: CMSEND(SAP)

LC  2 Error 1006 when executing external command powershell.exe on %_TCPIP_%2 (xpgid=0,convid=.)

              R4  9 Communication error, CPIC return code 020, SAP return code 456

           R5  A > Conversation ID: 81167698

              R6  4 > CPI-C function: CMSEND(SAP)

             LC  2 Error 1006 when executing external command powershell.exe on %_TCPIP_%2 (xpgid=0,convid=.)

          R2  G HTTP/RFC session has been deleted following timeout

       R2  G HTTP/RFC session has been deleted following timeout.

I looked into 1891781 - error occurs when you execute an external command

But it is not relevant in our case.

Regards,

Pavan Gunda

[feng_shi]

Hi,

The following sap note does relevant to our case.

1891781 - error occurs when you execute an external command

the sporadic timeout will be fixed after implementing the following sap notes.

   1569335 - Sporadic timeout when executing external commands

   1743472 - Sporadic timeout when executing external commands (2)

   1927940 - Further improvement in retry mechanism

   1896935 - Improvement to retry mechanism from SAP Note 1569335

   1963297 - Improvement to SAP Note 1927940

Thanks and best regards,

Shi

[Former Member]

Hi Fen,

The above notes are not relevant in my case. I dint found a combination of

CPIC return code 020 & SAP return code 456.

Regards,

Pavan Gunda

[isaias_freitas]

Hello Pavan,

The error entries you posted indicate that SAP is trying to start the command "powershell.exe", not sapxpg.

Is any SM59 destination being used to start the sapxpg?

Why the application is trying to start "powershell"? This is a Windows executable and it is not "RFC-enabled". A connection to "powershell.exe" would never work.

Regards,

Isaías

[Former Member]

I Tried to extract the WP log during that time. I see below. SAPXPG is the exe that is being triggerd below.

L  SXPG:

L  SXPG: Begin of ABAP Callstack

L  SXPG: rc = Error 1006

L  SXPG: SAPLSSXP LSSXPF01 FORM WRITE_CALLSTACK

L  SXPG: SAPLSSXP LSSXPF01 FORM SYSLOG_COM_EXEC

L  SXPG: SAPLSSXP LSSXPU01 FUNCTION SXPG_STEP_XPG_START

L  SXPG: SAPLSSXP LSSXPU03 FUNCTION SXPG_STEP_COMMAND_START

L  SXPG: SAPLSXPT LSXPTU02 FUNCTION SXPG_COMMAND_EXECUTE_LONG

L  SXPG: SAPLSXPT LSXPTU03 FUNCTION SXPG_COMMAND_EXECUTE

L  SXPG: ZFAPRUK_RFFOGB_T ZFAPRUK_RFFOGB_T FORM SUB_EXTERNAL_COMMAND

L  SXPG: ZFAPRUK_RFFOGB_T ZFAPRUK_RFFOGB_T FORM SUB_EXECUTE_SSH_SCRIPT

L  SXPG: ZFAPRUK_RFFOGB_T ZFAPRUK_RFFOGB_T FORM SUB_PROCESS_BACS

L  SXPG: ZFAPRUK_RFFOGB_T ZFAPRUK_RFFOGB_T FORM SUB_PROCESS_BACS_DATA

L  SXPG: ZFAPRUK_RFFOGB_T ZFAPRUK_RFFOGB_T FORM CHECK_PRINT_BACS

L  SXPG: ZFAPRUK_RFFOGB_T ZFAPRUK_RFFOGB_T EVENT END-OF-SELECTION

L  SXPG: End of ABAP Callstack

L  SXPG:

L  SXPG_COMMAND_EXECUTE(LONG):

L  <timestamp>: 20160623114417

L  COMMANDNAME: Z_BACS_AP_SSH

L  ADDITIONAL_PARAMETERS: \\HOSTNAME\XYZ\GB\F\Outbound\Data\BACS\AP\GB_B

L  ADDITIONAL_PARAMETERS: ACS_GB02_AP_GBA1E_20160623_114355

L  LONG_PARAMS:

L  OPERATINGSYSTEM: Windows NT

L  TARGETSYSTEM: HOSTNAME

L  DESTINATION:

L  SY-SUBRC:  902

[isaias_freitas]

Hello Pavan,

It seems that the target host, where the program is to be executed, is a Windows server.

Is it the same server where SAP is running?

Because if it is a remote server, then you would have to install an rsh or ssh server at the target (Windows) server, and maybe an rsh  ssh client at the source (SAP) server.

But instead of using an rsh/ssh server at a Windows machine, I would recommend installing a Standalone Gateway at the target server, and then pointing the destination to start the program using that Standalone Gateway.

Regards,

Isaías