Hello Experts - This issue has been posted many times . But it seems there may be many root causes for this issue. So the solution must be different. For our case, we have been searching for long, but did not find a solution . Here is the situaion.
1) We developed a custom report which is using ALV report. Anyone running that report in our company (using our company SAP GUI, Windows ,laptops) are getting this dump.
2) However, I strongly belive there is no issue with custom report , as consultants outside our company , say Accenture, Infosys (whose GUI and laptop provided by other company) are not getting this error. They are able to run the report with out any issues. This tells me that there is some thing worng with our GUI installation or environment or some cause at our end. If it is issue with custom code, it should happen irrespective, from where we are testing.
3) We are currently on GUI 7.30 with patch 7. However, we tried latest patch on 7.30 which is 11 and also we tried latest GUI 7.40 with hot fix . Every where we are getting this error. Out partner consultants also on SAP GUI 7.30 with patch 7. For that matter, out side consultants are on different levels of GUI.
4) when we are on 7.30 with patch 7, we used to get this DUMP, after running the report for certain time, say 1 min or so. what we noticed when we are 7.40 is , the moment we execute the report, we are getting this DUMP.
5) For refernce , we are providing , dump information below.
6) Many posts of this type,referring to uninstall and reinstall the GUI, however, we tried this many time with differnet version. To avoid any registered key issues, we took a fresh loaner laptop and installed SAP GUI 7.40 (with hot fix) from SAP site directly . Still we are getting this dump.
7) Dump documentation on ST22, says some thing about mathcing kernal but I am not sure, what kernel we need to be on. Any expert suggestions on that are very helpful.
8) Some posts are referring some DLL are missing in installation. however, we tried many GUI's and even on a fresh laptop.
9) Any expert ideas on why this is happeneing in our systems, is highly appreciated.
System environment
SAP-Release 700
Operating system..... "Windows NT"
Release.............. "6.1"
Hardware type........ "2x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 3
Shortdump setting.... "full"
Database type..... "MSSQL"
Database name..... "DEV"
Database user ID.. "dev"
Terminal................. "LAP-JCKSCS1"
Char.set.... "C"
SAP kernel....... 720
created (date)... "Mar 10 2014 00:00:41"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "SQL_Server_9.00 "
Patch level. 600
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 720
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT 6.3"
Memory consumption
Roll.... 0
EM...... 12569376
Heap.... 0
Page.... 32768
MM Used. 2890608
MM Free. 1296512
1 FUNCTION AC_SYSTEM_FLUSH .
2 *"----------------------------------------------------------------------
3 *"*"Lokale Schnittstelle:
4 *" IMPORTING
5 *" VALUE(CALLED_BY_SYSTEM) TYPE C OPTIONAL
6 *" EXCEPTIONS
7 *" CNTL_SYSTEM_ERROR
8 *" CNTL_ERROR
9 *"----------------------------------------------------------------------
10 data: sysubrc like sy-subrc.
11
12 CALL FUNCTION 'AC_FLUSH_CALL'
13 EXPORTING
14 SYSTEM_FLUSH = 'X'
15 CALLED_BY_SYSTEM = CALLED_BY_SYSTEM
16 IMPORTING
17 MESSAGE_NR = sysubrc
18 MESSAGE_TEXT = SY-MSGLI.
19
20 sy-subrc = sysubrc.
21
22 CASE SY-SUBRC.
23 WHEN 0.
24 WHEN 1.
25 * system_error
26 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
27 WHEN 2.
28 * method_call_error
>> MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
30 WHEN 3.
31 * property_set_error
32 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
33 WHEN 4.
34 * property_get_error
35 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
36 WHEN 8.
37 * maximal number of modi reached
38 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 011 RAISING CNTL_SYSTEM_ERROR.
39
40 WHEN OTHERS.
41 RAISE CNTL_ERROR.
42 ENDCASE.
Error analysis
Short text of error message:
Control Framework : Error processing control
Long text of error message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
system
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Technical information about the message:
Message class....... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
"MESSAGE_TYPE_X" " "
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
