This website is not affiliated with, sponsored by, or approved by SAP AG.

RABAX_STATE error in GRC AC 10

SAP Security

Moderators: Snowy, thx4allthefish, jurjen

RABAX_STATE error in GRC AC 10

Postby techcreater » Wed Dec 19, 2012 11:59 am

Hi All,

I am facing error when i activate MSMP workflow conf in the access control in GRC 10

• The following error occurred in system <System Name> : The ASSERT condition was violated.
• The error occurred on application server <System Name> and in work process 3.
• The termination type was: RABAX_STATE
• The ABAP call stack was:
Method: GET_MAPPED_PATHIMG of program CL_GRFN_MSMP_CONFIGURATION= = = =CP Method: _CHECK of program CL_GRFN_MSMP_CONFIGURATION=== =CP Method: CHECK of program CL_GRFN_MSMP_CONFIGURATION== = =CP Method: CHECK of program CL_GRFN_MSMP_CONFIGURATION====CP Method: GENERATE_VERSION of program CL_GRFN_MSMP_GENERATE_VERSIONSCP Method: GENERATE_VERSION of program /IBCWDY/002TI4SPKVHCDC482T3W==CP
Method: IF_GRFNMVCSAVE_C1R1..vGENERATE_VERSION of program /113CWDY/002TI4SPKVHCDC482T3W ==CP

What can I do?
• If the termination type is RABAX_STATE, you will find more information on the cause of termination in system<System Name> in transaction ST??.
• If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server chazgrdOl_GRD_00 in transaction 5M2I.
• If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 3 in transaction ST lion the application server.
Last edited by techcreater on Tue Jan 08, 2013 8:26 am, edited 1 time in total.
techcreater
 
Posts: 22
Joined: Wed Oct 21, 2009 8:55 am

Re: RABAX_STATE error in GRC AC 10

Postby Al. » Fri Dec 21, 2012 4:54 pm

What does the ST22 log say. RABAX_STATE error is a common one.
http://www.turnkeyconsulting.com/
Al.
 
Posts: 3050
Joined: Tue Feb 25, 2003 5:35 am
Location: London

Re: RABAX_STATE error in GRC AC 10

Postby techcreater » Mon Dec 24, 2012 5:13 am

Logs as follows: -

Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program CL_GRFN_MSMP_CONFIGURATION====CP
Application Component GRC

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.

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

Information on where terminated
Termination occurred in the ABAP program "CL_GRFN_MSMP_CONFIGURATION====CP" -
in "GET_MAPPED_PATH_IMG".
The main program was "GRFNMW_GENERATE_VERSIONS ".

In the source code you have the termination point in line 41
of the (Include) program "CL_GRFN_MSMP_CONFIGURATION====CM01F".
techcreater
 
Posts: 22
Joined: Wed Oct 21, 2009 8:55 am


Return to SAP Security

Who is online

Users browsing this forum: No registered users and 3 guests





loading...


This website is not affiliated with, sponsored by, or approved by SAP AG.