ERROR- The ASSERT Condition was violated- RABAX_STATE-- GRC PC 10.X

[Former Member]

Got this issue where if user is logging into the GRC PC10.0 as internal control manager & straightaway this message is thrown.

We could fix the issue with additional authorization but it enabled the user to have access to other workcenters, which we dont want to provide.

ST22 dump shows there may be a program error- But if that's the case it should occur for each user- But the issue is only with couple of users & not all.

Could the Gurus help to understand this error & the troubleshooting steps & their experience if they faced the same error.

[rajeshwari_akkamgari]

Hello Sanjeev,

To check this further we would need more details as where exactly you are getting this error along with St22 screenshot.

Thanks

Rajeshwari

[Former Member]

Please find the dump information below- This is not the full dump.

Let me know if you need/looking for some particular information-

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.

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

How to correct the error Probably the only way to eliminate the error is to correct the program. If the error occurs in a non-modfied SAP program, you might be able to find a solution in the SAP Notes system. If you have access to the SAP Notes system, check there first using the following keywords: "ASSERTION_FAILED" "CL_GRPC_MODEL_SETUP===========CP" bzw. CL_GRPC_MODEL_SETUP===========CM082 "FILL_PROCESS_HIER_BUFFER" If you cannot solve the problem yourself, please send the following information to SAP: 1. This description of the problem (short dump) To do this, choose System -> List -> Save -> Local File (unconverted) on the screen you are in now. 2. A suitable system log To do this, call the system log in transaction SM21. Restrict the time interval to ten minutes before the short dump and five minutes after it. In the display, choose System -> List -> Save -> Local File (unconverted). 3. If these are programs of your own, or modified SAP programs: Source code of these programs To do this, choose More Utilities -> Upload/Download -> Download in the Editor. 4. Details regarding the conditions under which the error occurred or which actions and input caused the error.

RFC Caller Information Information on caller of "HTTP" connection: Plug-in type......... HTTP Caller IP.............. 10.41.69.37 Caller port............ 8000 Universal resource ID /sap/bc/webdynpro/sap/zgrc_pc_ext_ep2 Program.............. CL_GRPC_MODEL_SETUP===========CP Screen.............. SAPMHTTP 0010 Screen line.......... 2 Information on caller of "HTTP" connection: Plug-in type......... HTTP Caller IP.............. 10.41.69.37 Caller port............ 8000 Universal resource ID "/sap/bc/webdynpro/sap/zgrc_pc_ext_ep2"

Information on where terminated The termination occurred in ABAP program "CL_GRPC_MODEL_SETUP===========CP", in "FILL_PROCESS_HIER_BUFFER". The main program was "SAPMHTTP". In the source code, the termination point is in line 43 of (Include) program "CL_GRPC_MODEL_SETUP===========CM082".