Hi,
After upgrading NW04s from SP07 to SP11, one of my web dynpro for ABAP application gives the following error on execution.
I am also getting a system dump. I have checked all the necessary services in SICF & most of the required services are active. Does any one have some idea of how I can resolve this error.
***********************************************************************************************
Error when processing your request
What has happened?
The URL http://ustca644.kcc.com:8086/sap/bc/webdynpro/sap/zvmkc_tsvm_main/ was not called due to an error.
Note
The following error text was processed in the system PGW : Metadata of Controller >EMPTYVIEW< Is Not
Consistent. "View Controller" Does Not Contain a "View"
The error occurred on the application server ustca644_PGW_20 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CONTROLLER_KIND_TO_TEXT of program CL_WDY_RG_META_SERVICE========CP
Method: CONSTRUCTOR of program CL_WDY_RG_CONTROLLER==========CP
Method: GET_CONTROLLER_PARTS of program SAPLWDR_RUNTIME_REPOSITORY
Method: SAVE_COMPONENT of program SAPLWDR_RUNTIME_REPOSITORY
Method: SAVE of program SAPLWDR_RUNTIME_REPOSITORY
Function: WDR_SAVE_REPOSITORY of program SAPLWDR_RUNTIME_REPOSITORY
Method: SAVE of program CL_WDR_RR_DB==================CP
Function: WDY_WB_GENERATE_INTERNAL of program SAPLWDY_WB_ACTIVATION_SERVICES
Function: WDY_WB_GENERATE of program SAPLWDY_WB_ACTIVATION_SERVICES
Method: CONSTRUCTOR of program SAPLWDR_RUNTIME_REPOSITORY
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
PGW 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 ustca644_PGW_20 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 ustca644_PGW_20 . 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: 400 -u: C14216 -l: E -s: PGW -i: ustca644_PGW_20 -w: 0 -d: 20070222 -t: 222514 -v: RABAX_STATE -e:
UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
***********************************************************************************************
System Dump
***********************************************************************************************
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_WDY_RG_MD
Date and Time 02/22/2007 22:25:14
-
-
-
-
Short text |
An exception occurred that was not caught. |
-
-
-
-
What happened? |
The exception 'CX_WDY_RG_MD' 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_WDY_RG_META_SERVICE========CP' has to be |
terminated. |
-
-
-
-
What can you do? |
Note down which actions and inputs caused the error. |
|
|
To process the problem further, contact you SAP system |
administrator. |
|
Using Transaction ST22 for ABAP Dump Analysis, you can look |
at and manage termination messages, and you can also |
keep them for a long time. |
-
-
-
-
Error analysis |
An exception occurred which is explained in detail below. |
The exception, which is assigned to class 'CX_WDY_RG_MD', was not caught and |
therefore caused a runtime error. |
The reason for the exception is: |
Metadata of Controller >EMPTYVIEW< Is Not Consistent. "View Controller" Does |
Not Contain a "View" |
|
-
-
-
-
How to correct the error |
|
If the error occures in a non-modified SAP program, you may be able to |
find an interim solution in an SAP Note. |
If you have access to SAP Notes, carry out a search with the following |
keywords: |
|
"UNCAUGHT_EXCEPTION" "CX_WDY_RG_MD" |
"CL_WDY_RG_META_SERVICE========CP" or "CL_WDY_RG_META_SERVICE========CM001" |
"CONTROLLER_KIND_TO_TEXT" |
|
|
If you cannot solve the problem yourself and want to send an error |
notification to SAP, include the following information: |
|
1. The description of the current problem (short dump) |
|
To save the description, choose "System->List->Save->Local File |
(Unconverted)". |
|
2. Corresponding system log |
|
Display the system log by calling transaction SM21. |
Restrict the time interval to 10 minutes before and five minutes |
after the short dump. Then choose "System->List->Save->Local File |
(Unconverted)". |
|
3. If the problem occurs in a problem of your own or a modified SAP |
program: The source code of the program |
In the editor, choose "Utilities->More |
Utilities->Upload/Download->Download". |
|
4. Details about the conditions under which the error occurred or which |
actions and input led to the error. |
|
-
-
-
-
System environment |
SAP-Release 700 |
|
Application server... "ustca644" |
Network address...... "165.28.85.39" |
Operating system..... "Windows NT" |
Release.............. "5.2" |
Hardware type........ "4x AMD64 Level" |
Character length.... 16 Bits |
Pointer length....... 64 Bits |
Work process number.. 0 |
Shortdump setting.... "full" |
|
Database server... "PGWA" |
Database type..... "DB2" |
Database name..... "PGW" |
Database user ID.. "SAPR3" |
|
Char.set.... "C" |
|
SAP kernel....... 700 |
created (date)... "Oct 30 2006 00:08:55" |
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00" |
Database version. "DB2CLI.DLL 08.02.0003 " |
|
Patch level. 83 |
Patch text.. " " |
|
Database............. "DB2 for OS/390 7.1, DB2 for OS/390 8.1, DB2 for OS/390 |
9.1" |
SAP database version. 700 |
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2" |
|
Memory consumption |
Roll.... 16192 |
EM...... 16759360 |
Heap.... 0 |
Page.... 0 |
MM Used. 12837904 |
MM Free. 3918160 |
-
-
-
-
User and Transaction |
Client.............. 400 |
User................ "C14216" |
Language Key........ "E" |
Transaction......... " " |
Program............. "CL_WDY_RG_META_SERVICE========CP" |
Screen.............. "SAPMHTTP 0010" |
Screen Line......... 2 |
|
Information on Caller ofr "HTTP" Connection: |
Plug-in Type.......... "HTTP" |
Caller IP............. "165.28.239.30" |
Caller Port........... 8086 |
Universal Resource Id. "/sap/bc/webdynpro/sap/zvmkc_tsvm_main/" |
|
-
-
-
-
Information on where terminated |
Termination occurred in the ABAP program "CL_WDY_RG_META_SERVICE========CP" - |
in "CONTROLLER_KIND_TO_TEXT". |
The main program was "SAPMHTTP ". |
|
In the source code you have the termination point in line 20 |
of the (Include) program "CL_WDY_RG_META_SERVICE========CM001". |
-
-
-
-
-
-
-
-
1 | method CONTROLLER_KIND_TO_TEXT . |
2 | |
3 | data: |
4 | cref_View type ref to cl_wdy_md_view, |
5 | ctlr_Type type Wdy_Md_Controller_Type. |
6 | |
7 | ctlr_Type = controller->get_type( ). |
8 | |
9 | case ctlr_Type. |
10 | |
11 | when wdyn_ctlr_type_custom. |
12 | controller_type_as_text = 'CUSTOM'. |
13 | |
14 | when wdyn_ctlr_type_view. |
15 | controller_type_as_text = 'VIEW'. |
16 | if ( ABAP_FALSE eq Controller->Has_View( ) ). |
17 | " view controller must have a view |
18 | gi_Cx_Text = Controller->Get_Name( ). |
19 | gi_Cx_Hint = '"View Controller" enthält keine "View"'(NVW). |
>>>>> | raise exception type Cx_Wdy_Rg_Md |
21 | exporting |
22 | TextId = Cx_Wdy_Rg_Md=>Controller_Data |
23 | Controller = gi_Cx_Text |
24 | Reason = gi_Cx_Hint. |
25 | |
26 | else. |
27 | gi_Cx_Text = Controller->Get_Name( ). |
28 | if ( gi_Cx_Text eq 'EMPTYVIEW' ). |
29 | return. |
30 | endif. |
31 | |
32 | " sanity check against illegal CL_WDY_MD_EMPTY_VIEW |
33 | try. |
34 | cref_View ?= Controller->Get_View( ). |
35 | if ( cref_View is initial ). |
36 | gi_Cx_Text = Controller->Get_Name( ). |
37 | gi_Cx_Hint = '"View Controller" enthält keine "View"'(NVW). |
38 | raise exception type CX_Wdy_Rg_Md |
39 | exporting |
-
-
-
-
Contents of system fields |
-
-
-
-
SY-SUBRC | 0 |
SY-INDEX | 1 |
SY-TABIX | 2 |
SY-DBCNT | 0 |
SY-FDPOS | 7 |
SY-LSIND | 0 |
SY-PAGNO | 0 |
SY-LINNO | 1 |
SY-COLNO | 1 |
SY-PFKEY | |
SY-UCOMM | |
SY-TITLE | HTTP Control |
SY-MSGTY | |
SY-MSGID | |
SY-MSGNO | 000 |
SY-MSGV1 | |
SY-MSGV2 | |
SY-MSGV3 | |
SY-MSGV4 | |
SY-MODNO | 0 |
SY-DATUM | 20070222 |
SY-UZEIT | 222514 |
SY-XPROG | |
SY-XFORM | |
-
-
-
-
-
-
No. Ty. Program Include Line |
Name |
-
-
22 METHOD CL_WDY_RG_META_SERVICE========CP CL_WDY_RG_META_SERVICE========CM001 20 |
CL_WDY_RG_META_SERVICE=>CONTROLLER_KIND_TO_TEXT |
21 METHOD CL_WDY_RG_CONTROLLER==========CP CL_WDY_RG_CONTROLLER==========CM001 25 |
CL_WDY_RG_CONTROLLER=>CONSTRUCTOR |
20 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF11 684 |
LCL_SAVE_REPOSITORY=>GET_CONTROLLER_PARTS |
19 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF11 91 |
LCL_SAVE_REPOSITORY=>SAVE_COMPONENT |
18 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF11 29 |
LCL_SAVE_REPOSITORY=>SAVE |
17 FUNCTION SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYU02 27 |
WDR_SAVE_REPOSITORY |
16 METHOD CL_WDR_RR_DB==================CP CL_WDR_RR_DB==================CM002 3 |
CL_WDR_RR_DB=>SAVE |
15 FUNCTION SAPLWDY_WB_ACTIVATION_SERVICES LWDY_WB_ACTIVATION_SERVICESU04 279 |
WDY_WB_GENERATE_INTERNAL |
14 FUNCTION SAPLWDY_WB_ACTIVATION_SERVICES LWDY_WB_ACTIVATION_SERVICESU01 84 |
WDY_WB_GENERATE |
13 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF12 77 |
LCL_REPOSITORY=>CONSTRUCTOR |
12 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF01 17 |
LCL_COMPONENT=>CONSTRUCTOR |
11 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF01 669 |
LCL_COMPONENT=>IF_WDR_RR_COMPONENT~GET_USED_COMPONENT |
10 METHOD SAPLWDR_RUNTIME_REPOSITORY LWDR_RUNTIME_REPOSITORYF01 245 |
LCL_COMPONENT=>IF_WDR_RR_COMPONENT~CREATE_COMPONENT_USAGE |
9 METHOD CL_WDR_MESSAGE_WINDOW=========CP CL_WDR_MESSAGE_WINDOW=========CM001 30 |
CL_WDR_MESSAGE_WINDOW=>CONSTRUCTOR |
8 METHOD CL_WDR_APPLICATION_WINDOW=====CP CL_WDR_APPLICATION_WINDOW=====CM00K 6 |
CL_WDR_APPLICATION_WINDOW=>INITIALIZE |
7 METHOD CL_WDR_CLIENT_COMPONENT=======CP CL_WDR_CLIENT_COMPONENT=======CM004 59 |
CL_WDR_CLIENT_COMPONENT=>DISPLAY_TOPLEVEL_COMPONENT |
6 METHOD CL_WDR_CLIENT_APPLICATION=====CP CL_WDR_CLIENT_APPLICATION=====CM00L 30 |
CL_WDR_CLIENT_APPLICATION=>INIT |
5 METHOD CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00I 40 |
CL_WDR_MAIN_TASK=>EXECUTE |
4 METHOD CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00J 69 |
CL_WDR_MAIN_TASK=>IF_HTTP_EXTENSION~HANDLE_REQUEST |
3 METHOD CL_HTTP_SERVER================CP CL_HTTP_SERVER================CM00I 524 |
CL_HTTP_SERVER=>EXECUTE_REQUEST |
2 FUNCTION SAPLHTTP_RUNTIME LHTTP_RUNTIMEU02 929 |
HTTP_DISPATCH_REQUEST |
1 MODULE (PBO) SAPMHTTP SAPMHTTP 13 |
%_HTTP_START |
-
-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.