Hi All,
I developed a Web Dynpro ABAp application and tested it through a user with SAP_ALL Profile, and am getting the following error message:
The URL http://sileccdev053.simondelhi.com:8000/sap/bc/webdynpro/sap/zadobe was not called due to an error.
Note
The following error text was processed in the system DEV : WebDynpro Exception:
The error occurred on the application server SILECCDEV053_DEV_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CONSTRUCTOR of program CL_WD_ADOBE_SERVICES==========CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/CADOBE==================CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/CADOBE==================CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C7STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program CL_WDR_VIEW_ADAPTER===========CP
Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_VIEW_ADAPTER===========CP
Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_WINDOW_CONTENT_ADAPTER=CP
Method: SET_CONTENT of program CL_WDR_NW7_INT_WIN_ADAPTER====CP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system DEV in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server SILECCDEV053_DEV_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server SILECCDEV053_DEV_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 300 -u: PWCABAP -l: E -s: DEV -i: SILECCDEV053_DEV_00 -w: 0 -d: 20110215 -t: 111729 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
In ST22 we get the following:
WHAT HAPPENED:
The exception 'CX_WD_GENERAL' was raised, but it was not caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_WD_ADOBE_SERVICES==========CP' has to be
terminated.
ERROR ANALYSIS:
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_API_REPOSITORY", which was raised in the program
"CL_FP_WB_HELPER===============CP",
specifically in line 7 of the (include) program
"CL_FP_WB_HELPER===============CM00V".
The cause of the exception was:
Object ZADOBE does not exist
Please Suggest something.
Cheers!!!
Umang 😊