Question Re: Access request : error The ASSERT condition was violated. (termination: RABAX_STATE) in Additional Q&A

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

Former Member — Wed, 28 Sep 2016 15:32:04 GMT

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,

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

alessandr0 — Wed, 28 Sep 2016 15:34:05 GMT

AV,

please share ST22 dump.

Regards,

Alessandro

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

Former Member — Wed, 28 Sep 2016 15:41:42 GMT

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

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

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

alessandr0 — Wed, 28 Sep 2016 18:27:56 GMT

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

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

plaban_sahoo6 — Thu, 29 Sep 2016 03:48:18 GMT

Hi,

Could you provide SLG1 log, as well.

Regards

Plaban

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

Former Member — Thu, 29 Sep 2016 07:09:05 GMT

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_A	V1100	0013	SAPK-V1113INGRCFNDA	GRC Foundation ABAP
GRCPINW	V1100_731	0014	SAPK-11514INGRCPINW	SAP GRC NetWeaver Plug-In

Child systems

GRCPINW

V1100_731

0013

SAPK-11513INGRCPINW

SAP 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,

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

Former Member — Thu, 29 Sep 2016 07:09:53 GMT

Hi Plaban,

No SLG1 log generated for this issue.

Regards,

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

Former Member — Thu, 29 Sep 2016 07:39:34 GMT

Hello Akhil,

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

Regards,

Zoltan

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

Former Member — Thu, 29 Sep 2016 08:13:16 GMT

Hi Zoltan,

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

Regards,

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

Former Member — Fri, 30 Sep 2016 06:17:06 GMT

Hi Alessandro,

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

Thanks a lot for your help on this.

Regards,

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

Former Member — Fri, 30 Sep 2016 06:20:19 GMT

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,