cancel
Showing results for 
Search instead for 
Did you mean: 

Access request : error The ASSERT condition was violated. (termination: RABAX_STATE)

Former Member
0 Kudos

Hi,

I am currently setting up GRC AC and PC 10.1 and have completed all the post install steps and configurations.

In the Access Request form,  while trying to add the roles, I'm getting the following error (even before selecting or submitting the form) :

"The ASSERT condition was violated. (termination: RABAX_STATE)"

Any idea on the source of this issues? All settings seem to be in place.

Thanks,

AV

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Akhil,

As your basis is NW 7.50, check SAP notes 2299562 and 2331111.

Regards,

Zoltan

Former Member
0 Kudos

Hi Zoltan,

2299562 does seem to be applicable. I'll ask my BASIS team to check it and get back to you.

Regards,

AV

Former Member
0 Kudos

Hi Zoltan,

We applied 2331111 and 2184361,2291533 from 2299562 (the others were incompatible) and that did it.

Thanks a lot for your help on this.

Regards,

AV

Answers (1)

Answers (1)

alessandr0
Active Contributor
0 Kudos

AV,

please share ST22 dump.

Regards,

Alessandro

Former Member
0 Kudos

ST22 dump:

Category               ABAP programming error

Runtime Errors         ASSERTION_FAILED

ABAP Program           CL_FPM_GUIBB_SEARCH_DATA_MGR==CP

Application Component  BC-WD-CMP-FPM

Date and Time          28.09.2016 15:21:34

Short Text

     The ASSERT condition was violated.

What happened?

     The current application program has detected a situation with the

     ASSERT statement that should not occur.

     The reason for this runtime error was one of the following:

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

     activation mode is "abort".

     - A system variant has been used to set the activation mode to "abort

     globally for all checkpoint groups in this system.

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

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

Error Analysis

The following checkpoint group was used: No checkpoint group specified

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

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

  (not used)

  (not used)

  (not used)

  (not used)

  (not used)

  (not used)

  (not used)

" (not used) "

Information on where terminated

    The termination occurred in ABAP program or include

     "CL_FPM_GUIBB_SEARCH_DATA_MGR==CP", in "CONSTRUCTOR". The

    main program was "SAPMHTTP".

    In the source code, the termination point is in line 11 of  program or

    include "CL_FPM_GUIBB_SEARCH_DATA_MGR==CM001".

Note: There is no SLG1 error for this in system. More details in the attachemnt

alessandr0
Active Contributor
0 Kudos

seems like org values / entities are missing. What is your current SP? Try to apply note 2291796 and let us know if it helps.

Regards,

Alessandro

plaban_sahoo6
Contributor
0 Kudos

Hi,

Could you provide SLG1 log, as well.

Regards

Plaban

Former Member
0 Kudos

HI Allesandro,

In GRC system - Foundation component is at SP13 but I see that the plugin is SP14.

The connected child systems have the plugin component GRCPINW at SP13.

Could there be any issue because of the difference??


GRC

GRCFND_AV11000013SAPK-V1113INGRCFNDAGRC Foundation ABAP
GRCPINWV1100_7310014SAPK-11514INGRCPINWSAP GRC NetWeaver Plug-In

Child systems

GRCPINWV1100_7310013SAPK-11513INGRCPINWSAP GRC NetWeaver Plug-In

I'll ask BASIS to apply the note that you have suggested in the meanwhile to see if it corrects it

Thanks,

AV

Former Member
0 Kudos

Hi Plaban,

No SLG1 log generated for this issue.

Regards,

AV

Former Member
0 Kudos

Hi Alessandro,

2291796 was actually incompatible for our system. So we could not apply it.


Thanks a lot for your help on this.


Regards,

AV