3437244 - How to enable the SNC for external commands started by sapxpg?

External commands started by sapxpg fail when SNC is enabled in the system. The following symptoms may appear:

• Error "Message incomplete (severity, area, number, or exception missing)" in SNOTE (Note Assistant) during SAP Note download or upload
• "Unknown error 902" in SM49/SM69 when executing external commands
• RFC trace (dev_rfcXX) contains one of:
  • GW_SNC_START_EXT_DIS (thRc=730) — "Not allowed to start non-SNC connections"
  • GW_SECURITY_ERROR (thRc=676) — "Program cannot be started on the host; no authorization"
  • FORK_FAILED (thRc=635) — "Partner program fork failed" — with RC 667 / GwStartProgram in dev_wXX (Windows)

Note: The GW_SNC_START_EXT_DIS scenario is addressed by the snc/permit_insecure_start parameter described in this KBA. The GW_SECURITY_ERROR and FORK_FAILED scenarios indicate a secinfo file blocking sapxpg — a second independent condition. Setting snc/permit_insecure_start = 1 will not resolve the secinfo condition. Both conditions may be active at the same time. See the Resolution section.

• SAP NetWeaver / ABAP Platform
• SNC enabled (snc/enable = 1)
• Operating system: All platforms (Linux, Unix, Windows NT)
• Note: Behaviour on Windows may differ from Linux — see Resolution for platform-specific guidance.

snc/permit_insecure_start, snc/enable, SNC, sapxpg, external commands, SNOTE, Message incomplete, Unknown error 902, secinfo, gw/sec_info, GW_SNC_START_EXT_DIS, FORK_FAILED, RC 667, GwStartProgram, gwntrd, Windows NT, PROGRAMSTARTERROR, SM49, SM69, not allowed to start non-SNC connections, SAPCAR , KBA , BC-CCM-BTC-EXT , External and Logical Commands , BC-SEC-SNC , Secure Network Communications , BC-UPG-NA , Note Assistant , BC-OP-LNX , Linux , BC-OP-NT , Windows , How To