Short dump RABAX_STATE assert condition violated

[Former Member]

Hi Folks,

I am getting a shortdump while calling any menu-header in role SAP_PLMWUI_MENU in NWBC 3.0 .

The following lines are what's been displayed:

Error while processing your request!

What has happened?

The call of URL https://xxx.xxx.xxx:1443/sap/bc/webdynpro/plmu/wda_generic_wcc has been terminated due to an error.

Note

The following error text was processed in system XXX : The ASSERT condition was violated.

The error occurred on application server xxxxxx_xxx_00 and in work process 0 .

The termination type was: RABAX_STATE

The ABAP call hierarchy was:

Method: /PLMB/IF_SPI_METADATA_BASE~GET_NODE_DEFINITION of program /PLMB/CL_SEA_QUERY_MP=========CP

Method: GET_NODE_DEFINITION of program /PLMB/CL_SPI_METADATA=========CP

Method: GET_INSTANCE of program /PLMB/CL_SPI_METADATA=========CP

Method: GET_PROVIDERS of program /PLMB/CL_SPI_FACTORY==========CP

Method: CONSTRUCTOR of program /PLMB/CL_SPI_CONNECTOR========CP

Method: GET_INSTANCE of program /PLMU/CL_FRW_APPL_MODEL=======CP

Method: WDDOINIT of program /1BCWDY/8RZ0RU0GQZSQIAOXYT9D==CP

Method: IF_WDR_COMPONENT_DELEGATE~WD_DO_INIT of program /1BCWDY/8RZ0RU0GQZSQIAOXYT9D==CP

Method: DO_INIT of program CL_WDR_DELEGATING_COMPONENT===CP

Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP

What can you do?

In the case of termination type RABAX_STATE, you will find in system XXX in transaction ST22 more information on the cause of termination.

In the case of termination type ABORT_MESSAGE_STATE, you will find on application server xxxxxx_xxx_00 in transaction SM21 more information on the cause of termination.

In the case of termination thype ERROR_MESSAGE_STATE, you can search for more information in the trace file for the work process 0 in transaction ST11 on application server xxxxxx_xxx_00 . An analysis of trace files for other work processes may be necessary.

If you do not yet have any user ID, contact your system administrator.

Short Dump contains:

Short text

The ASSERT condition was violated.

What happened?

In the running application program, the ASSERT statement recognized a

situation that should not have occurred.

The runtime error was triggered for one of these reasons:

- For the checkpoint group specified with the ASSERT statement, the

activation mode is set to "abort".

- Via a system variant, the activation mode is globally set to "abort"

for checkpoint groups in this system.

- The activation mode is set to "abort" on program level.

- The ASSERT statement is not assigned to any checkpoint group.

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

The following checkpoint group was used: "No checkpoint group specified"

If in the ASSERT statement the addition FIELDS was used, you can find

the content of the first 8 specified fields in the following overview:

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

" (not used) "

...

We're using SAP ERP 6.0 EHP 4 / NW 7.0 EHP 1 on a Wndows Server 2003 x86_64 bit System,

PLM-Release: 700 SP 9

Any ideas or help for solving this problem?

THX beforehands

regards

C:Peifer

Edited by: Carsten Peifer on May 18, 2011 2:21 PM

[steven_bier · Accepted solution]

Hi Carsten,

have you generate you BC and Webdynpro Application using Transaktion sgen ?

have a look at this thread it can be helpful.

best regards

Steven

Edited by: Steven Bier on May 19, 2011 10:10 AM

[Former Member · Accepted solution]

Hi Steven,

Thank you for your quick reply and greetings from Trierer Str. in SB ;).

I generated BC and Web Dynpro Loads via SGEN, with no effect.

I'm still getting the error while launching any application of Role SAP_PLMWUI_MENU in NWBC. The Thread was not really helpful too, i checked the note 1343806, but it's not relevant and not helpful because we have PLM 700 SP 9 in our system and the correction in the node is delivered with sp 5.

Do you have any other ideas or hints? Is there maybe a problem with non-unicode System?

THX

regards

C.Peifer

[Former Member · Accepted solution]

Hello Carsten,

How did you solve the issue? We have the same problem with PLMWUI_MENU.

Thanks and best regards,

Ana.

[mckenzie_cutshall · Accepted solution]

Anyone have an update on this?  Any resolution?

[jyotiprakash_das4 · Accepted solution]

Hi ,

I am getting this error in SRM-> strategic purchasing ->sourcing->perform sourcing.

But it's not happening when I am using the standard roles.

It's only appearing for customized ones. Means if I am copying the sourcing part into a new portal role.

Can you please suggest how to resolve this.