UNCAUGHT_EXCEPTION - CX_WD_CONTEXT - Could not find attribute STACK_NR

[Former Member]

Hi,

Title: UNCAUGHT_EXCEPTION - CX_WD_CONTEXT - Could not find attribute STACK_NR

I got this Dump in our Solution Manager system, i couldnt find any Note in Marketplace, do you have any idea what is this about? Thank you.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_WD_CONTEXT

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_WD_CONTEXT' 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_WDR_CONTEXT_NODE_INFO======CP' has to be

1. terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

1. 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_WD_CONTEXT', was not caught and therefore caused a runtime error.

The reason for the exception is:

Could not find attribute STACK_NR

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

"CL_WDR_CONTEXT_NODE_INFO======CP" or "CL_WDR_CONTEXT_NODE_INFO======CM002"

"IF_WD_CONTEXT_NODE_INFO~GET_ATTRIBUTE"

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

Information on where terminated

Termination occurred in the ABAP program "CL_WDR_CONTEXT_NODE_INFO======CP" -

in "IF_WD_CONTEXT_NODE_INFO~GET_ATTRIBUTE".

The main program was "SAPMHTTP ".

In the source code you have the termination point in line 19

of the (Include) program "CL_WDR_CONTEXT_NODE_INFO======CM002".

Regards,

Mohan.

[chengalarayulu]

Krishna,

It clearly says that, there is no attribute(STACK_NR) exists under your context node.

check either mapping is correctly done or not. if mapping is already done then go to view and check with update mapping of the node.

[farooq_basha]

Hi Mohan,

1) Check with the BASIS team whether they have implemented any SAP NOTE recently if so then check is there any manually changes need to be done at table/class/..etc level in that SAP NOTE document.

2) If any SAP NOTE has implemented check for dependent NOTE is there? If so then try to implement that also.

May be this can be route cause of the above DUMP.

Regards,

Farooq

[Former Member]

Hi Farooq,

there is no Note been immplemented in the system. Any other idea?

[farooq_basha]

Hi Mohan,

Is it standard application?

Check whether the attribute - STACK_NR is available or NOT. If so then check for the data element of this attribute is available or not.

Regards,

farooq

[Former Member]

Hi Farooq,

iam a basis man, i dont know how to check whether the attribute is available or not, data element is available or not. For checking Data element, i think it is Data Type in SE11 transaction?

Regards,

Mohan.

[farooq_basha]

Hi mohan,

Please consult with ur webdynpro ABAP or ABAP consultant they can understand the DUMP.

Ask them to check attribute and Data element for that attribute.

Regards,

Farooq