Symptom
Several ABAP runtime error "MESSAGE_TYPE_X" dumps occur when running multiple and parallel automation scripts from same client within the SAP system for load tests and performance simulation purposes.
Below errors can be found in the SAP GUI session trace (main session components: automation, scripting, control manager) collected when triggering the "MESSAGE_TYPE_X" dump:
(Error): Exception fire by :SAP Frontend Server
(Error): Exception info:Cannot find window
(Error): Exception code:65535
(Error): Exception fire by :SAP Frontend Server
(Error): Exception info:Cannot create control
(Error): Exception code:65535
Error(DD.MM.AA HH:MM:SS): CMyUIThread::InitInstance(): Main windows is NULL
Error(DD.MM.AA HH:MM:SS): Failed to start UI-Thread (Frontend start failed)
Error(DD.MM.AA HH:MM:SS): Sapgui failed to initialize gui (rc=4)
Read more...
Environment
- SAP GUI for Windows
- ABAP Platform
- SAP NetWeaver
Product
Keywords
abap runtime error, message_type_x, sap gui scripting, exception window, error handling, st22 dump, sap gui for windows, control framework error, parallel scripts, load generator, resource bottleneck, memory bottleneck, sap gui patch level, sap gui 800, automation error, scripting restrictions. , KBA , BC-FES-GUI , SAP GUI for Windows , 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.
SAP Knowledge Base Article - Preview