error occured while showing adobe form in abap webdynpro application

[Former Member]

Dear SAP-Masters ,

This is the mail regarding the error occured while showing adobe form in abap webdynpro application .

When i run the adobe form seperately it works fine but with abap web dynpro , i'll get following error .

Pls tell me how to resolve this problem .

The following error text was processed in the system D35 : WebDynpro Exception:

The error occurred on the application server DV35_D35_00 and in the work process 2 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: UPDATE_PDF of program CL_WD_ADOBE_SERVICES==========CP

Method: CREATE_PDF of program CL_WD_ADOBE_SERVICES==========CP

Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LADOBE==================CP

Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LADOBE==================CP

Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP

Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP

Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP

Method: CONV_VIEW_INTO_VE_ADAPTER_TREE of program CL_WDR_INTERNAL_WINDOW_ADAPTERCP

Method: SET_CONTENT_BY_WINDOW of program CL_WDR_INTERNAL_WINDOW_ADAPTERCP

Method: RENDER_WINDOWS of program CL_WDR_CLIENT_SSR=============CP

[IanStubbings]

We are also getting this error intermittently and the forms are always active. There is no pattern to the dumps but they are currently happening 9 times out of 10 tries to access any form.

Any ideas?

Regards

Ian

[Former Member]

Hai,

I have the answer for your question. The cause for your error is the form you have designed is not activated properly so that at run time you get a dump.To cross check this goto the view where you have interactive form double click on the templatesource property. this will take you to the form design page.At the top you see the page is still Inactive,You cannot make it active here. For this goto transaction SFP give the form interface name first and activate it,followed by activate by giving the form name. Now again activate your web dynpro application and test it you should get it now...

Give points if this was useful

Thanks & Regards

Ramesh Sivasamy

[arjun_thakur]

Hi Vishwas,

Go to transaction ST22 and check the source code extract and error analysis section and see from where the error is being triggered.

Regards

Arjun

[Former Member]

Hi Arjun ,

Thanx for ur reply ,

i got following results in ST22 dump analysis :

' An exception occurred that was not caught ' .

and

Source Code Extract

-

---

Line

SourceCde

-

---

79	x_xml = get_wd_context_as_xml( data_source = data_source ).
80	m_pdf_object->set_data( formdata = x_xml ).
81	catch cx_fp_exception into lr_fpexc.
82	raise exception type cx_wd_general
83	exporting
84	previous = lr_fpexc.
85	endtry.
86	if fillable = abap_true.
87	if m_version is initial.
88	m_version = m_pdf_object->get_version_info( ).
89	endif.
90	if version < ''.
91	set_usage_rights( m_pdf_object ).
92	endif.
93	endif.
94	endif.
95	endif.
96
97	only call the ads if requested
98	if execute_ads_call = abap_true.
99	try.
100	set document
101	m_pdf_object->set_document( pdfdata = pdf ).
102
103	execute, call ADS
104	m_pdf_object->execute( ).
105
106	get result
107	m_pdf_object->get_document( importing pdfdata = pdf ).
108	catch cx_fp_exception into lr_fpexc.
>>>>>	raise exception type cx_wd_general
110	exporting
111	previous = lr_fpexc.
112	endtry.
113	endif.
114
115	endmethod. and Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_WD_GENERAL', was not caught and
therefore caused a runtime error.
The reason for the exception is:
WebDynpro Exception:
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_FP_RUNTIME_SYSTEM", which was raised in the program
"CL_FP_PDF_OBJECT==============CP",
specifically in line 255 of the (include) program
"CL_FP_PDF_OBJECT==============CM02Y".
The cause of the exception was:
ADS: com.adobe.ProcessingException: PDF is not interactive. Data can only be

| imported into interactive forms.(201501).