UNCAUGHT_EXCEPTION

[Former Member]

Hi I am  getting this dump in my ECC production system.

can somebody help me.

An exception occurred that was not caught.                                                    |

-

---

-

---

What happened?

The exception 'CX_NWBC' 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_NWBC_SERVER_ASSIST=========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_NWBC', was not caught and

therefore caused a runtime error.

The reason for the exception is:

NWBC was called with invalid Parameters

System environment                                                                                |

SAP Release..... 702

SAP Basis Level. 0012

Application server... "*******"

Network address...... "10.*..1*"

Operating system..... "Linux"

Release.............. "2.6.16.60-0.85.1-smp"

Hardware type........ "x86_64"

Character length.... 8 Bits

Pointer length....... 64 Bits

Work process number.. 13

Shortdump setting.... "full"

Database server... "aa-sap01"

Database type..... "ORACLE"

Database name..... "ECP"

Database user ID.. "SAPERP"

Terminal.......... "10.87.*.*"

Char.set.... "en_US.ISO-8859-1"

SAP kernel....... 720

created (date)... "Dec 16 2012 19:37:06"

create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 "

Database version. "OCI_102, 10.2.0.4.0, V5, default"

Patch level. 400

Patch text.. " "

Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"

SAP database version. 720

Operating system..... "Linux 2.6, Linux 3"

Memory consumption

Roll.... 0

EM...... 4189880

Heap.... 0

Page.... 0

MM Used. 1507720

MM Free. 2679592

-

---

-

---

User and Transaction

Client.............. 030

User................ "HURSTL"

Language key........ "E"

Transaction......... " "

Transaction ID...... "527DAA4282890B48E10000000A420211"

EPP Whole Context ID.... "A0B3CCE36F361EE392E5CE683CB94A97"

EPP Connection ID....... "A0B3CCE36F361EE392E5CD94CC995E09"

EPP Caller Counter...... 1

Program............. "CL_NWBC_SERVER_ASSIST=========CP"

Screen.............. "SAPMHTTP 0010"

Screen Line......... 2

Debugger Active..... "none"

-

---

-

---

Server-Side Connection Information

Information on Caller of "HTTPS" Connection:

Plug-in Type.......... "HTTPS"

Caller IP............. "10.*.*.*"

Caller Port........... 8400

Universal Resource ID. "/sap/bc/nwbc/Z:CA_ESS_ALL/"

Program............. "CL_NWBC_SERVER_ASSIST=========CP"

Screen.............. "SAPMHTTP 0010"

Screen Line......... 2

Information on Caller ofr "HTTPS" Connection:

Plug-in Type.......... "HTTPS"

Caller IP............. "10.87.16.248"

Caller Port........... 8400

Universal Resource Id. "/sap/bc/nwbc/Z:CA_ESS_ALL/"

-

---

-

---

Chain of Exception Objects

-

---

Attrib. Name

Value

-

---

Level    1     Class    CX_NWBC

Program  CL_NWBC_SERVER_ASSIST=========CP Include  CL_NWBC_SERVER_ASSIST=========CM00N Row   5

Short Te NWBC was called with invalid Parameters

Long Tex

-

---

DOCUMENTATION_DATA
DOCUMENTATION_URL
IS_RESUMABLE
KERNEL_ERRID
NOTE_NR
NOTE_URL
V1
V2
V3

-

---

-

---

Information on where terminated

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

in "GET_PARAM_SAP_NWBC_HISTORY".

The main program was "SAPMHTTP ".

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

of the (Include) program "CL_NWBC_SERVER_ASSIST=========CM00N".

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---

1	method get_param_sap_nwbc_history.
2
3	rv_history = mo_server->request->get_form_field( if_nwbc_constants=>gc_s_parameter-histo
4	if rv_history cn '0123456789._-rot'.
>>>>>	raise exception type cx_nwbc
6	exporting
7	textid = cx_nwbc=>cx_invalid_parameter.
8	endif.
9
10	endmethod.

-

---

|                                             

[Former Member · Accepted solution]

Thank you everybody. My problem solved. I have deleted the instance in rz04 and recreated. It solved my problem.

[Former Member · Accepted solution]

Hi Tee,

Iam having same problem. I have followed your suggestion and recreated the instances in RZ04.

First  couple of days it was fine but now the dumps are re-occurring. Have you come across any other alternative.? iam not sure i might have to raise SAP message.

Regards

Raj

[Former Member]

Hi Tee,

Im using NWBC for HTML(3.5.2.23) and i have the same dump in my system. Before i go and play with my opmodes,  I just want to know how deleting and creating OP-Modes (Instance) has fixed the issue ?

Regards

Raj

[former_member182034]

hi Tee,

please go through this and those sap note which are mention in below SAP note.

Note 1378659 - NWBC known issues & what to check when opening a ticket

It might be helpful.

Regards,

[former_member264034]

Hi ,

Make sure that the system runs on the most current NWBC Runtime
Environment with applying the latest Patch Level Note and the Note for
update of SNOTE:

#875986 - Note Assistant: Important notes for SAP_BASIS up to 702

#1883635 - SAP NWBC ABAP Runtime Patch 32

After applying the recommended Notes, please check if the issue still
occurs.

Regards,

Aidan