cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime error in Adobe forms

Former Member
0 Kudos

Hi,

I am getting a run time error when i create ADOBE form and try to save. I am using SAP GUI 7.10 and ADOBE livecycle version 7.1. I did tried with ADOBE livecycle version 8.0 and getting same problem.

NOTE: This is the first ADOBE form i am trying to create in company.

Below are the dump details ...Please let me know if any of you have faced similar problem....Thanks

Short text

The current application triggered a termination with a short dump.

What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

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.......... " "

Trigger Location of Runtime Error

Program SAPLOLEA

Include LOLEAU02

Row 29

Module type (FUNCTION)

Module Name AC_SYSTEM_FLUSH

Source Code Extract

Line SourceCde

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 OTHERS.

37 RAISE CNTL_ERROR.

38 ENDCASE.

39

40 ENDFUNCTION.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Chandra,

you can try following.

Before saving PDF form, put external breakpoint in FM

AC_FLUSH_CALL_INTERNAL.

Save PDF Form, i guess it should go to this FM. Check which exception is setting sy-subrc = 2.

(There are different checks in this FM for checking ActiveX, javabeen support etc).

Hope this will help.

Although, I never encountered the error you mentioned

Regards,

Mohaiyuddin

Former Member
0 Kudos

Hi,

I tried external break-point in the function module, but it is not stopping in the function module.

I tried all scenarios mentioned in the tread, nothing worked out....please let me know if any one has any other options.

Thanks,

Chandra

Answers (1)

Answers (1)

former_member188685
Active Contributor
0 Kudos

I faced the similar situation. That time i Uninstalled the Designer and GUI, then First installed Desinger 7.1 and then Installed the SAP GUI. nd restarted the system.

there is some problem with the GUI patches. it usually happens with my Designer. I am not sure what exactly the problem . But wait for some more solutions..

some times i dont uninstall or install , simply restart the system will help in some cases

Former Member
0 Kudos

Thanks Vijay..

As i dont see any reply i tried installing designer 8.0 first and then GUI 7.10...but still getting same problem. Please let me know if you have any other options.

Thanks,

Chandra

former_member188685
Active Contributor
0 Kudos

First i installed 8.0 , then i unistalled it and Installed 7.1

Now it is working fine for me. From above post you have to check those conditions also. ADOBE Acrobat Reader version should be latest.