SAP Knowledge Base Article - Preview

3462431 - SAP Web Dispatcher trace file reports "ERROR => FtInsert(ftPipeAdm) failed"


The symptom observed by the end users can vary. For example, a blank page is received after logging on to the Fiori LaunchPad.

The "console" log of the browser developer tools shows one or more failed requests with "net::ERR_HTTP2_PROTOCOL_ERROR".

The SAP Web Dispatcher version in use is already higher than the one listed on the SAP Note 3025581.

The SAP Web Dispatcher trace file (dev_webdisp) has many entries like the ones below:

[Thr 10028] *** ERROR => FtInsert(ftPipeAdm) failed. [mpixx.c      1899]
[Thr 10028] *** ERROR => IcmConnInitBuffer: MpiCreate2 failed (rc=2) [icxxconn.c   7690]
[Thr 10028] *** ERROR => H2PlugHandleHeader: IcmConnInitBuffer() failed: 2 [h2_plg.c     2020]
[Thr 10028] *** ERROR => H2PlugHandleHeader: Failure: *** Unknown error *** (2)! Stream 41 will be canceled! [h2_plg.c     2210]

FtInsert(ftPipeAdm) failed"">


  • SAP Web Dispatcher release independent


ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Dispatcher all versions


net::ERR_HTTP2_PROTOCOL_ERROR, HTTP/2, H2, BW cockpit, blank page , KBA , BC-CST-WDP , Web Dispatcher , BC-MID-ICF , Internet Communication Framework , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , BC-CST , Client/Server Technology , BW4-UI , Maintenance & Monitoring User Interfaces , 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.