SAP Knowledge Base Article - Preview

2483210 - HTTP 500 error occurs when calling SAPGUI transactions - the call is stuck in the /sap/public/myssocntl service


When calling SAPGUI transactions that open the application in a browser window, an HTTP 500 error (or in earlier releases, a blank page) is displayed in the browser. The application is not loaded, and the browser's address bar does not show the expected application URL. Instead, the address bar shows a URL like http(s)://<host>:<port>/sap/public/myssocntl?sap-client=<client>. This may give the impression to the business user, that an "incorrect" URL is generated.

In the corresponding dev_icf* traces (visible in the transaction ST11), one of the below errors is logged:

<ErrorInfo URL="http(s)://<host>:<port>/sap/public/myssocntl"> 
<ErrorMessage>Ticket-Anmeldung fehlgeschlagen - siehe Trace (Hinweis 495911)</ErrorMessage>


<ErrorInfo URL="http(s)://<host>:<port>/sap/public/myssocntl"> 
<ErrorMessage>Es wurde kein Ticket per Header empfangen.</ErrorMessage>


<ErrorInfo URL="http(s)://<host>:<port>/sap/public/myssocntl"> 
<ErrorMessage>Message E00001 Cannot be processed in plugin mode HTTP(S)</ErrorMessage>

Affected transactions are for example: SOAMANAGER, NWBC, BRF+, SM_WORKCENTER, SOLMAN_SETUP, DBACOCKPIT, etc.

Note: This current KBA is only relevant if:

1. The browser call fails in the service /sap/public/myssocntl


2. The error returned is HTTP 500 Internal Server Error or a blank page without any error message.  The current KBA is only relevant if the call actually reaches the /sap/public/myssocntl service and it responds with HTTP 500 or a blank page. If the call terminates with errors like "This page can't be displayed",  INET_E_RESOURCE_NOT_FOUND etc., that indicates that the request does not reach the ABAP system, and the issue should be checked by the local network team.


3. One of the above error messages are logged in the dev_icf* traces. For the error message "Message E00001 Cannot be processed...", decisive is the part E 00 001 which shows the message type, class and number. For other error messages like "Message E WEBDYNPRO_RT 023 cannot be processed...", this KBA is not relevant - please check the KBA 2993748 for details.



  • SAP NetWeaver
  • SAP Web Application Server for SAP S/4HANA
  • ABAP Platform


ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions


ESH_COCKPIT , BRF+, SAP Web Dispatcher , HTTPS  , Active , Inactive , HTTP , SICF, Service , Services, 500 SAP Internal Server Error, white screen, white page, Es wurde kein Ticket per Header empfangen., Ticket-Anmeldung fehlgeschlagen - siehe Trace (Hinweis 495911), No ticket was received using header, /UI2/FLP. /n/UI2/FLP, /UI2/FLPD_CUST, /UI2/FLPD_CONF, "500 Internal Server Error" , "No ticket was received using header. (Message E 00 001)", SSO, myssocntl, can't reach this page, This page can't be displayed, OA2C_CONFIG, ILM_SB, STC01, secussl_read, oa2c_grant , KBA , es wurde kein ticket per header empfange , BC-MID-ICF , Internet Communication Framework , BC-MID-ICF-LGN , ICF System Login , 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.