Skip to Content
0
Jun 20, 2014 at 03:41 PM

RABAX_STATE error in SOLMAN_SETUP step 6.6

47 Views

Hi all,

I'm doing the Solman_setup, step "System Preparation" for a new Solution Manager 7.1 sp 14.

As I try to get into the task 6.6 "Connect Diagnostics" the system generates a short dump :

Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_UNKNOWN
ABAP Program CL_WDR_MESSAGE_MANAGER========CP
Application Component BC-WD-ABA-RUN
Date and Time 20.06.2014 11:26:31
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short text |
| Message type "e" is unknown. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "CL_WDR_MESSAGE_MANAGER========CP" had to be |
| terminated because it has |
| come across a statement that unfortunately cannot be executed. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|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. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Error analysis |
| Only message types A, E, I, W, S, and X are allowed. |
| There is probably an error in the program |
| "CL_WDR_MESSAGE_MANAGER========CP".

All the previous tasks were performed successfully.

It seems to be a program error, but I can't find any Oss Note for it.

Any advise ?

regards