Skip to Content
0
Former Member
Oct 12, 2011 at 01:54 PM

Solution Manager error "The termination type was: RABAX_STATE "

63 Views

Hello All,

I was tasked with setting up security for our new SAP Solman Project Managment solution and ran into the following errors while testing.

BACKGROUND:

User type was application consultant and was prompted by business test users that this type of user should be allowed to create issues in issue management but not allowed to delete issues in issue management. Only Project Managers should. Removed the 06 delete authorization from CRM_ORD_PR auth_obj and instead of getting "you are not authorized" error message (what is expected) user is thrown to the below exception page:

===================================================

Error when processing your request

What has happened?

The URL http://##############.com:####/sap/bc/webdynpro/sap/dswp_ci_issue_management was not called due to an error.

Note

The following error text was processed in the system DM1 : An exception occurred

The error occurred on the application server sapdc004_DM1_00 and in the work process 1 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: DELETE_CRM_ORDER of program CL_DSWP_CI_CRM_BUFFER=========CP

Method: DELETE_ISSUE of program CL_DSWP_CI_CRM_BUFFER=========CP

Method: DELETE_ISSUE of program CL_DSWP_CI_IM_MODEL_ASSIS4====CP

Method: DELETE_ISSUE of program /1BCWDY/E9JDCLCGWZ4H2NCZR2J4==CP

Method: IWCI_DSWP_CI_IM_MODEL~DELETE_ISSUE of program /1BCWDY/E9JDCLCGWZ4H2NCZR2J4==CP

Method: ON_DELETE_ISSUE of program /1BCWDY/E9JCYB3ZPWFCW42TLIUK==CP

Method: ON_DELETE_ISSUE of program /1BCWDY/E9JCYB3ZPWFCW42TLIUK==CP

Method: IF_WDR_COMPONENT_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/E9JCYB3ZPWFCW42TLIUK==CP

Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_COMPONENT===CP

Method: FIRE_EVENT of program CL_WDR_COMPONENT==============CP

What can I do?

If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system DM1 in transaction ST22.

If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapdc004_DM1_00 in transaction SM21.

If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server sapdc004_DM1_00 . In some situations, you may also need to analyze the trace files of other work processes.

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

Error code: ICF-IE-http -c: 100 -u: TRAIN30 -l: E -s: DM1 -i: sapdc004_DM1_00 -w: 1 -d: 20111011 -t: 140639 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

==================================================

Ran ST22 and reviewed the following dump:

=====================================================

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_DSWP_CI_OBJECT

Date and Time 10/11/2011 14:06:39

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_DSWP_CI_OBJECT' was raised, but it was not caught anywhere

along

the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program

'CL_DSWP_CI_CRM_BUFFER=========CP' has to be

terminated.

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.

=================================================================

I did some searches on possible notes but none seemed to be appropriate and I would like to get as much information as possible before sending this over to the Basis team for resolution.