UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Hi All,
           I am trying to load data till update rules it is showing "GREEN" status but after update rules when it is updating from update rules to the Info cube it is not updating.
In Enviornment -> Short dump -> Data warehousing
i found What happened?
    The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
    terminated.
Now How shoukd i proceed to correct the issue.
Varun

Hello,
Which version and patch you are working on?
see the link:
http://documents.bmc.com/supportu/documents/07/07/50707/Output/TR4350_patch2.htm.
SAP has provided some patches for the same.
also see note 963760 or note 1157796 if it helps!
Reg,
Dhanya

Similar Messages

UNCAUGHT_EXCEPTION "CX_RSR_X_MESSAGE" when runnign BEx Query

Hi,
We have a user who is using the Accounts Payable report. User is able to access the BEx query, run the query but when the user is trying to move the company code from free characteristics to rows BEx is throwing the following error:
An error occurred in the communication with the BW server.
Due to this, the connection had to be closed
Detailed Description:
An exception occurred that was not caught.
When i checked the ABAP dumps for this user, there is a dump with UNCAUGHT_EXCEPTION "CX_RSR_X_MESSAGE" .
Can anyone hlep me understand this problem. The reports when executed by me works fine. We tried reinstalling the front end for the user but that did not resolve the problem.If any one has seen this problem for BEx reporting and if any notes are applicable
Any help is greatly appreciated.
Regards
Vijay

Hi,
please try this one:
- clean the system setup, temp files, temp internet files
- start query designer -> open this query -> check the query
- executing in BEx web
- go to RSRT2 -> generate query -> execute in SAP GUI
- start system trace while executing
Best regards
Sven

Business content error UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Hi all,
I am on 7.0 and when I install Business content I get the following dump.
Also when I monitor my job it in the job log I can see " The object is not allowed to be empty" coming up several times and then just abruptly dumps.
I have checked the notes and forums but nothing matches to my problem...also we understand that we are on a low SP package 10 which I guess is the big problem.
Any advice,
DUMP:
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RSR_X_MESSAGE
Date and Time          08.12.2008 15:05:52
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
     terminated.

Hi
Did you resolve this issue. Because we are facing the same problem. wheniam now installing demo content.
Thanks

Runtime Error-UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Hi All,
I am getting below runtime error when I am trying to load data from a flat file to Infocube.I am on Bi 7.0 and it is a totally new server.
Error message:
The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
terminated.
Information on where terminated
    Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 82
    of the (Include) program "LRRMSU13".
Please tell me what could be the issue.Is it related to some patch issue???
Regards,
Kshitij

Are you trying this load manually or through process chain?
if process chain , the file should be placed in application server.
chk if the file is closed b4 triggering the infopack.
try loading other flat file load for different datasource and chk.
Ramesh

BI Content data load - Caller 70 ST22 Error CX_RSR_X_MESSAGE

Hi All,
Currently, we have been in the process of activating BI Content mostly 3.x flows within our new development system.
including cubes 0FIAP_C02, 0FIAR_C05, 0FIAR_C02, 0FIGL_C01 etc. Activation of content through to source system has been successful though data loading has proved into the cube through the 3.x flow has proved to be an issue.
The problem being when the info package is run to update the specific cube the load remains in yellow pending status before eventually reaching its time-out limit and producing a caller 70 error as below:-
Short dump in the Warehouse
Diagnosis
The data update was not finished. A short dump has probably been logged in BI. This provides information about the error.
System Response
"Caller 70" is missing.
Further analysis:
Search the BI short dump overview for the short dump that belongs to the request. Pay attention to the correct time and date on the selection screen.
You access a short dump list using the wizard or the menu path "Environment -> Short dump -> In the Data Warehouse".
Error handling:
Follow the instructions in the short dump.
After checking ST 22 we obtain a number of exceptions as shown detailed below :-
   The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
   terminated.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"
   75   ELSE.
   76     DATA: l_text TYPE string,
   77           l_repid TYPE syrepid.
   78
   79     l_repid = i_program.
   80     l_text = i_text.
   81
>>>>>     RAISE EXCEPTION TYPE cx_rsr_x_message
   83           EXPORTING text = l_text
   84                  program = l_repid.
   85   ENDIF.
   86
   87 ENDFUNCTION.
I have looked through the many articles related the error including notes :- 551464, 850428, 615389
Though to no avail, there are no locked idocs in sm58 and also basis have checked the DB size and all is OK, also reactivating and dropping index's did not work
Just wondering if there could be any further issues to resolve the data loading issues?
Many Thanks

Hi,
Based on the provided details, please take a look at below detail in the short dump:
I_IOBJNM
   <Object>       (In the most of cases the impacted object is 0REQUEST)
So, check the version of the object: >> tcode RSD5 - <object> -> Display
-> 'Version Comparison' button -> display All Properties -> Active/Content Version
By these steps you can see what is different in the versions (A-Active and D-Delivered)
To solve the issue check the steps provided in note 1157796 (in the first part - Symptom item)
It should helps.
Regards,
Sinara

While trying to load data Runtime Err UNCAUGHT_EXCEPTION Except.CX_RSR_X_ME

Hi
We are on BI.7 patch SAPKW70015 BI_CONT 703 - 0007 SAPKIBIIP7 and multi source system BI server. One is for R/3 it is already working and another is for new IS Retail.
While trying to load data to inventory (Z-cube) for first time in production system we get the following error :
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RSR_X_MESSAGE
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
    "SAPLRRMS" or "LRRMSU13"
    "RRMS_X_MESSAGE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
Information on where terminated
    Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 73
    of the (Include) program "LRRMSU13".
    The program "SAPLRRMS" was started as a background job.
Line SourceCde
   43     BREAK-POINT.
   44     SET EXTENDED CHECK ON.
   45   ENDIF.
   46
   47   IF i_abend EQ rs_c_false.
   48 *... Nachricht an den Message-Handler schicken
   49
   50     DATA: l_type TYPE smesg-msgty.
   51
   52 *... S-Meldung wenn kein Handler initialisiert
   53     IF g_active IS INITIAL.
   54       l_type = 'S'.
   55     ELSE.
   56       l_type = 'W'.
   57     ENDIF.
   58
   59     CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
   60       EXPORTING
   61         i_class = 'BRAIN'
   62         i_type   = l_type
   63         i_number = '299'
   64         i_msgv1 = i_program
   65         i_msgv2 = i_text.
   66   ELSE.
   67     DATA: l_text TYPE string,
   68           l_repid TYPE syrepid.
   69
   70     l_repid = i_program.
   71     l_text = i_text.
   72
>>>>>     RAISE EXCEPTION TYPE cx_rsr_x_message
   74           EXPORTING text = l_text
   75                  program = l_repid.
   76   ENDIF.
   77
   78 ENDFUNCTION.
The other data loads are working fine in the production system.
We searched a lot on the forum and got various solutions But none of them are working fine for us.
Please suggest.
Thanks you for your help.
Ramana P

Are you trying this load manually or through process chain?
if process chain , the file should be placed in application server.
chk if the file is closed b4 triggering the infopack.
try loading other flat file load for different datasource and chk.
Ramesh

CX_RSR_X_MESSAGE Data load error in Quality system

Hi
We are on BI.7 and trying to load Technical content data for first time in Quality system .
We get the following error :
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_RSR_X_MESSAGE
for all the technical content data load.
The other data loads are working fine in the quality system.
We searched a lot on the forum and got various solutions like try out note 615389, 963760 etc.. But none of them are working fine for us.
Please suggest.
Thanks you for your help.
Gaurav

Hi
The error log is as follows -
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_X_MESSAGE
Date and Time          23.01.2009 10:06:08
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' 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.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
    "SAPLRRMS" or "LRRMSU13"
    "RRMS_X_MESSAGE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
It gives a error in the last step of executing infopackage wherein the data is to be updated to the infocube.
I checked with Basis team. There is no tablespace problem as well.
Regards
Gaurav

Runtime error on BI Dev (UNCAUGHT_EXCEPTION)

Hi Team,
We are getting time error pn BI DEV . please check the below log .
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_X_MESSAGE
Date and Time          28.02.2012 11:50:17
     The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
      and
     therefore caused a runtime error.
     The reason for the exception is:
     No text available for this exception
How to correct the error
     If the error occures in a non-modified SAP program, you may be able to
     find an interim solution in an SAP Note.
     If you have access to SAP Notes, carry out a search with the following
     keywords:
     "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
     "SAPLRRMS" or "LRRMSU13"
     "RRMS_X_MESSAGE"
SAP-Release 701
Application server... "pssapsbx"
Network address...... "10.10.32.114"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "00F6B2C64C00"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "pssapsbx"
Database type..... "ORACLE"
Database name..... "BD3"
Database user ID.. "SAPBP3"
Terminal.......... "inp-260888-1"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 701
created (date)... "Apr 1 2011 23:57:22"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "OCI_102 (10.2.0.4.0) "
Patch level. 137
Kindly suggest , this has to be check by BASIS or BI DEV team.

Hi,
About this dump please see the instructions given in the solution
part of note 1157796.
#1157796 - Characteristic 0REQUEST must reference 0REQUID
The root cause could be the missing reference of 0REQUEST to 0REQUID
as mentioned in this note.
In addition to please check Infoobject 0REQUID in transaction RSD5.
Please compare the delivered version with the active version and if
difference exist install the content version again
as it is given in the note.
Thank You.
Regards,
Deepika

CX_RSR_X_MESSAGE with 80SD_O01 standard

Hi Everyone, I am running RSA3 transaction in BW system (7.02) to check 80SD_O01 extractor, this one will be used for moving data from 0SD_O01 to 0SD_O03. When I ran the extractor checker, the system dumps UNCAUGHT_EXCEPTION, CX_RSR_X_MESSAGE, SAPLRRMS. I followed the instructions at OSS note 1157796, I checked the 0REQUEST and 0REQUID with transaction RSD5, but nothing changes, could you help me?

Hi,
check following thread
Short dump u201CCX_RSR_X_MESSAGEu201D with cube 0PS_C031
Exception CX_RSR_X_MESSAGE in manage screen of 0ic_c03 cube
URGENT: cx_rsr_x_message "uncaught_exception" in 0ic_c03
Thanks and regards
Kiran

Short dump while loading statistics data - 'CX_RSR_X_MESSAGE'

Hi all,
When I am loading statistics data with Init selection, system gives short dump error. Below is the message-
The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
terminated.
If anyone know the answer please share with me.
Regards,

Hi Preet,
Please find the details of short dump from ST22-
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
     and therefore caused a runtime error.
The reason for the exception is:
No text available for this exception
to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"
Regards,

UNCAUGHT_EXCEPTION on SAPLRRMS

Hi,
The dump arises during the load from PSA to infocube:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_X_MESSAGE
Date and Time          28.06.2011 15:20:35
    "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
    "SAPLRRMS" or "LRRMSU13"
    "RRMS_X_MESSAGE"
I_PROGRAM
    SAPLRRSI
I_TEXT
    INITIALIZE-1-
Please advice
Santi

Hello,
Usually, this problem might be caused by infoobject 0REQUEST.
Try to reinstall the infoobject 0REQUEST from business content
The instructions to reinstall 0REQUEST are mentioned in attached
Note 1157796:
"The content version of the characteristic 0REQUEST is usually correct.
You can see this in transaction RSD5 (dropdown content). If this is the
case, you can transfer the InfoObject from the content again:
Transaction RSOR -> BI Content -> Object Types -> under InfoObjects
select 0REQUEST and transfer it to the right (note the following
settings: "Only Necessary Objects"; collection mode: "Collect
Automatically")."
I hope it helps you.
Regards, Fran.

UNCAUGHT_EXCEPTION on load data for 0PU_C02 infocube

Hi Everybody, I am trying to load data into 0PU_C02 infocube from 0PU_O31 ODS, but the system shows me a problem in the log (ST22), the message includes:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"
Thanks for your help...

The below threads will help you to solve the issue.
Short dump while loading statistics data - 'CX_RSR_X_MESSAGE'
Short dump u201CCX_RSR_X_MESSAGEu201D with cube 0PS_C031
Loading 2lis_11_VAITM thowing error CX_RSR_X_MESSAGE

Loading 2lis_11_VAITM thowing error CX_RSR_X_MESSAGE

Hi Experts:
                I am loading 2lis_11_vaitm to 2 InfoCube and 1 ODS. It loads and activates but Reporting is not available and in monitor it shows Error. It thows short Dump as well.
Short Dump:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_X_MESSAGE
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught and therefore caused a runtime error. The reason for the exception is:
    No text available for this exception
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
    The main program was "RSMO1_RSM2 ".
In the source code you have the termination point in line 78
    of the (Include) program "LRRMSU13".
I can NOT even delete the Request. It is showing me error when I am trying to Delete Request.

Sonali,
first use SM21 to check if anything like the following info appears:
ORA-20000: Insufficient privileges#ORA-06512: at
"SYS.DBMS_STATS", line 2150#ORA-06512: at "SYS.DBMS_STATS",
line 14112#ORA-06512: at line 1
   If yes, please apply note 963760.
   Hope it helps.
Jin Ming

Short Dump Error while loading master data.

Hello All,
I am trying to load data from PSA to Info Object (0Material_Attr) via DTP, I am getting error and itu2019s giving the short dump.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_RSR_X_MESSAGE.
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE".
In Job overview, job is getting cancelled, with error message
"The object name is not allowed to be empty".
ABAP/4 processor: UNCAUGHT_EXCEPTION.
We have done the following steps, even then error persist.
Transaction RSRV > All Elementary Tests > Master Data > Compare Number Range and Maximum SID for the characteristic 0REQUID.
If the system reports an error here, correct the error using the "Correct Error" function.
Kindly suggest.
Thanks in Advance .

Error analysis from ST22
An exception occurred which is explained in The exception, which is assigned to class ' and therefore caused a runtime error.
The reason for the exception is: No text available for this exception
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"

Error in SQL Statement: SAPSQL_INVALID_TABLENAME

Hello all,
While displaying contents of infocube i am getting strange error ..
Error in SQL Statement: SAPSQL_INVALID_TABLENAME ABC
Message no. DBMAN256
( Table name length is 16 )
I am able to see the contents of Fact table.
Could not found any solution till now.. Any lights , views will be very much helpful.
Regards
Nimesh

hi Nimesh,
check oss note 835816
Symptom
When you execute a query, a data-mart, SEM, APO or similar access, an SQL error 4004 occurs "Unknown table name" Open SQL: Short dump with UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE in the ABAP Call Stack, you find the RSDRC_BASIC_DB_QUERY_DATA_GET function module.
Prior to this, relatively large datasets (more than 10%) were deleted from the InfoCube.
Other terms
Business Information Warehouse, Factview, DBMAN256, DBMAN
256, SAPLRSDRS, DELETE, DELETE_FACTS, RSDRD_DELETE_FACTS
Reason and Prerequisites
During the purge, the fact tables are rebuilt again as of a certain percentage, for performance reasons. The factview is then not created again.
Solution
Views that are already missing can be compiled again with the SAP_FACTVIEWS_RECREATE report.
The correction prevents the problem reappearing.
BW 3.0B
           Import Support Package 27 for 3.0B (BW3.0B Patch27 or SAPKW30B27) into your BW system. The Support Package is available whennote 0723258 with the short text "SAPBWNews BW3.0B Support Package 27", which describes this Support Package in more detail, is released for customers.
BW 3.10 Content
           Import Support Package 21 for 3.10 (BW3.10 Patch21 or SAPKW31021) into your BW system. The Support Package is available whennote 0723263 with the short text "SAPBWNews BW3.1 Content Support Package 21", which describes this Support Package in more detail, is released for customers.
BW 3.50
           Import Support Package 13 for 3.5 (BW3.50 Patch13 or SAPKW35013) into your BW system. The Support Package is available when note 0765114 with the short text "SAPBWNews BW Support Package 13 NetWeaver'04 Stack 13", which describes this Support Package in more detail, is released for customers.
In urgent cases you can use the correction instructions.
These notes may already be available before the Support Package is released, to make information available in advance. However, the short text then still contains the words "preliminary version".

UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Similar Messages

Maybe you are looking for