As of SAP GUI 7.20, 7.30 and 7.40, there is a security check before starting the SAP GUI. If the you click on 'Deny' or if in the SAP GUI security settings the option is set to 'Deny', you will get the same dump. When the sapgui.exe delegates, it always starts SAP Logon, no matter whether SAP Logon Pad is already running or not.
When the service worker logon account is SAP user and that user has enabled setting->“Activate guixt” , it
always starts SAP Logon, no matter whether SAP Logon Pad is already running or not.
Possible Reason 3
RFC connection fails in NAT environment.
No SAP GUI resources available any more on frontend PC.
Lot of parallel threads in ECTR can call SAPGui transactions e.g. when opening the structure tab of a document.
[15:06:55.113] FJ-08 Calling: /DSCSAG/DOC_GET_LATEST_STR4.[apilog @ stateless.txt#115] (using SAPGui)... [15:06:55.113] FJ-03 Calling: /DSCSAG/DOC_GET_LATEST_STR4.[apilog @ stateless.txt#114] (using SAPGui)... [15:06:55.113] FJ-05 Calling: /DSCSAG/FOL3_CLASS_READ.[apilog @ stateless.txt#113] (using SAPGui)... [15:06:55.113] FJ-02 Calling: /DSCSAG/DOC_WHEREUSED_ALLVERS2.[apilog @ stateless.txt#112] (using SAPGui)... [15:06:55.113] FJ-04 Calling: /DSCSAG/OBJ_GET_MULTIDETAIL2.[apilog @ stateless.txt#1
Possible reason 5
The "Log On" user of "Service Worker" should not be SAP user as recommended. In case, if "Log On" user is SAP user then "Activate GuiXT" must be unchecked for that user. The user should logon on SAP GUI on service worker machine and uncheck "Settings->Activate GuiXT" option.