ABEND BRAIN (299)

Hello together,
running a Query raises the following Error:
ABEND BRAIN (299): Systemfehler in Programm CL_RSR_HIERARCHY_BUFFER und Form ADJUSTRESTPATH-1- (Langtext beachten)
  MSGV1: CL_RSR_HIERARCHY_BUFFER
  MSGV2: ADJUSTRESTPATH-1-
Any Ideas ?
Thanks
Armin

Hello,
That's really hard to give you a tip.
Check if your query is using a hierarchy. Probably the H table of one of the hierarchy is empty.
You have to detect which one is, DELETE and reload.
Kind regards,
Edward John

Similar Messages

  • BRAIN 299 System error in program CL_RSR_RRK0_ATTR_C and form when executin

    Hi,
    I get the following error message when trying to execute a query in production.
    System error in program CL_RSR_RRK0_ATTR_C and form...
    BRAIN 299.
    This error does not occur in development or quality.
    I tested through RSRT and in Technical Information i found the following entry
    Query can use Aggregates NO
    The entry in development and quality is
    Query can use Aggregates Yes
    How is the entry Query can use aggregates determined and how can i change it.
    Please help to resolve this issue. It is very urgent.
    Points will be rewarded for helpful answers.
    regards,
    Ashish

    Hi!
    I dont know what happens in RSRT1 (may be any troubles with cookie at server) but I can help you.
    First, if you have created query and didn't test it in RSRT1 you have to first test it with button "ABAP web" or call query explicitly in Internet Browser. If you test query with button "Execute" message BRAIN 299 will appear with subsequent calls query in Internet Browser or with button "ABAP web". (You can copy your old queries to new and that'll be ok).
    After that, you push button "Generate Report". So your query tested in different mode without any errors!
    Good luck!
    Best Regards,
    Antoshkin Vitaly.

  • BRAIN 299: QUERY_CUBE- _REPAIR_FF_MISMATCH-02

    Hello,
    Background:
    Two weeks ago we rolled out an upgrade of our BW systemu2026
    Current ABAP Patch Level :
    SAP_ABA     701     0005     SAPKA70105     Application Component
    SAP_BASIS     701     0005     SAPKB70105     SAP Basis Component
    PI_BASIS     701     0005     SAPK-70105INPIBASIS     Basis Plug-In
    ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
    SAP_BW     701     0005     SAPKW70105     SAP Business Warehouse
    BI_CONT     703     0005     SAPKIBIIP5                          Business Intelligence Content
    Our Problem:
    Since two weeks I have strange system logs in the sm21 (sometimes / not every day) like the following:
    X MESSAGE BRAIN 299: QUERY_CUBE->_REPAIR_FF_MISMATCH-02- FFID:4B66D0F5387F0129E100800
    X MESSAGE BRAIN 299: QUERY_CUBE->_REPAIR_FF_MISMATCH-05- QCUBE FFID:-QUERY_CUBE->_REP
    X MESSAGE BRAIN 299: QUERY_CUBE->_REPAIR_FF_MISMATCH-05- CACHE FFID:l4B66D0F5387F0129
    X MESSAGE BRAIN 299: QUERY_CUBE->_REPAIR_FF_MISMATCH-05- QCUBE FFID:l4B6672E538B50167
    X MESSAGE BRAIN 299: QUERY_CUBE->_REPAIR_FF_MISMATCH-05- CACHE FFID:-4B6672E538B50167
    Our frontend is an arcplan solution... Different users told me now that they sometimes get the following error message: "Aggregate from ZQMNTFR was compressed. Data packet is not consistent."
    So I have to assume that we have a little problem with our cache, but how can I fix this error?
    I can't find any SAP Notes for our release...
    Thanks in advance,
    Alex

    Hello,
    does anybody solved this problem.
    We have it also in our System Landscape of BW systems.
    Our package level is:
    SAP_ABA     701     0006
    SAP_BASIS     701     0006
    PI_BASIS     701     0006
    ST-PI     2008_1_700     0003
    SAP_BW     701     0006
    BI_CONT     704     0006
    ST-A/PI     01M_BCO700     0001
    Best regards
    Petra Wöritz

  • Error MESSAGE BRAIN 299: CL_RSDM_READ_MASTER_DATA _CLEAR_TABLES-01-

    Dear Gurus,
    Recently, there was a user who was running something, we're not sure what he/she was running at the moment but it seemed to have generated a lot of the following messages in SM21.
    MESSAGE BRAIN 299: CL_RSDM_READ_MASTER_DATA CLEARTABLES-01-
    Any idea what this error is about???
    Regards,
    Keat

    Read,
    SAP Note 1232644 - Termination CLEARTABLES-01 in CL_RSDM_READ_MASTER_DATA
    Please do some research before posting
    Regards
    Juan

  • BRAIN 299 on multiprovider after Upgrade BI 7

    Hi after
    upgrade from BW 3.5 to 7.0 (sp18) some multiprovider not works.
    When I try to check and active it the following errors occurs
    =========
    System error in program CL_RSR and form INITIALIZECOB_PRO-1-
    Message no. BRAIN299
    Diagnosis
    This internal error is an intended termination resulting from a program state that is not permitted.
    Procedure
    Analyze the situation and inform SAP.
    If the termination occurred when you executed a query or Web template, or during interaction in the planning modeler, and if you can reproduce this termination, record a trace (transaction RSTT).
    For more information about recording a trace, see the documentation for the trace tool environment as well as SAP Note 899572.
    =========
    I don't found some note to resolve it.
    Any idea to active the multiprovider?
    tnks

    Hi,
    I'm facing a similar problem. While attempting to execute a query, which was working in the past, the following error occurs:
    Program error in class SAPMSSY1 method: UNCAUGHT_EXCEPTION
    System error in program CL_RSR and form GET_COB_PRO-01-(see long text)
    Entering the query, via Query Designer, and performing a check, the description of the error is the following
    Diagnosis
    This internal error is an intended termination resulting from a program state that is not permitted.
    Procedure
    Analyze the situation and inform SAP.
    If the termination occurred when you executed a query or Web template, or during interaction in the planning modeler, and if you can reproduce this termination, record a trace (transaction RSTT).
    For more information about recording a trace, see the documentation for the trace tool environment as well as SAP Note 899572.
    Do you have any ideia of whats the solution to solve this issue?
    Many thanks
    Joana

  • 500 Server Error when executing Query in Portal

    When I run a query in the ABAP Web all the components (the pulldowns) work as well as the query executes.
    When I run the query in the Java WebI get a 500 Internal Server Error
    com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
    ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
      MSGV1: SAPMSSY1
      MSGV3: UNCAUGHT_EXCEPTION
    ABEND BRAIN (299): System error in program BICS_PROV_GET_INITIAL_STATE and form Variables are not submitted (see long text)
      MSGV1: BICS_PROV_GET_INITIAL_STATE
      MSGV2: Variables are not submitted
    We are using Netweaver 7.0 sp 13.
    Any help is appreciated.... Point rewarded !!!
    Mike

    Yes I get that and it has been installed and everythign is worked awesomly. I can export queries to the portal. SSO, SSL and the whole bit it installed.
    The nwa default trace tool doesn't give me much to go on. Err looks like i described it above however it says its in
    Category: /Applications/BI
    Location: com.sap.ip.bi.base.application.message.impl.MessageBase
    Application: sap.com/irj
    The other err is in
    Category: /Applications/BI/Application_Framework
    Any ideas of where I should look?

  • ERROR: Brain 174

    Hi,
    I have an urgent problem: I use a planning query to input some data into an BI 7.0 system. When I execute this query with only one input-enabled column it works. If I add a second row it doesnt.
    The connection in Excel Business Analyzer breaks down without any notice, whereas the Portal gives the message ABEND BRAIN 174
    Does anyone know what this message means?
    Any help would be appreciated.
    Best regards
    Steffen Breuer

    Check out hese threads:
    How to resolve error "brain 225"?
    Error brain 284 impossible to solve
    Re: Brain errors
    Thanks...
    Shambhu
    Edited by: Shambhu Kumar Gupta on Aug 1, 2008 2:00 PM

  • Message Brain in SM21

    Hi,
    On my Solman 7.01 SP25 system, I've now started facing Brain messages in SM21:
    BI  0 X MESSAGE BRAIN 299: CL_RSR GET_COB_PRO-01-
    The culprit is SMD_RFC
    There are several of these daily:(
    All the notes recommend the latest BW SP..but I'm already on SAPKW7017.
    Pls. help.
    Thanks,
    -S.

    Hi Saba,
    I am also facing the same problem in 2 queries for only  few selections.
    In my situation also while running a stock report Program error occured in class SAPMSSY1 method : UNCAUGHT_EXCEPTION as result of the error Bex disconnecting from the BI server.
    In SM21 : X MESSAGE BRAIN 299: CL_RSR_RRK0_CACHE CREATE_NEW_FFID-01
    Please reply me if u got any solution for how to solve.
    thanks in advane,
    regards,
    <BMP>

  • Error while running a report

    Hi all,
    I am getting this particular error while running a report. The error is:
    <b>SQL Error: 604
    System error in program SAPLRRK0 and form RSRDR;SRRK0F30-01-
    Diagnosis
    This internal error is a targeted termination since the program has an
    incorrect status.
    Procedure
    Analyse the situation and inform SAP.
      Notification Number BRAIN 299 </b>
    Could anyone tell me what that means?
    Thanks In advance,
    Raj

    Hi Raj,
    There are a few OSS Notes for your issue.
    If your Query has hierarchy in it then check 734184
    If your query is based on Infoset then check Note 784502 and 701941.
    Also check 668921.
    Bye
    Dinesh

  • Error while executing Report

    Hi,
    Am getting very strange error while running a report.
    It gives me an 'Autopass' error while inserting some variables in the filter screen.
    Also it shows "system error in program CL RSR WWW RENDERER and form GET VARDEF FOR F4:03.
    Kindly provide your insights on this.
    regards,
    Omprakash

    Hi , could you please check note 1166294 and check if the issue will be fixed ?
    1166294-BRAIN 299 in CL_RSR, form GET_CHANMID-02-
    In case if you are executing the the report on a multiprovider then check this note below
    Note 1166241 - BRAIN 299 in CL_RSR, form GET_COB_PRO-01-
    hope this helps
    santosh

  • Characteristics Remittance information not available in infoprovider

    Hi All,
    When I run query from portal it get error : 500 Internal Server error                                                  Bex Web Application
    FAILED TO PROCESS REQUEST, CONTACT YOUR SYSTEM ADMINITRATOR
    ROOT CAUSE:
    Characteristics Remittance information not available in infoprovider
    ABEND BRAIN(635) QUERY COULD NOT BE OPENED.
    NOTE: THIS QUERY RUNS ON MULTIPROVIDER., ANY URGENT HELP WILL BE APPRECIATED, POINT WILL BE ASSIGNED
    Thanks in advance
    Hunna

    Hi,
    Try activating multiprovider and underlying infocubes, using following programs.
    Multiprovider: RSDG_MPRO_ACTIVATE
    Infocube: RSDG_CUBE_ACTIVATE
    DSO: RSDG_ODSO_ACTIVATE
    InfoObject: RSDG_IBOJ_ACTIVATE
    Then try to run the query, alternately you can use transaction RSRT.
    Regards,
    Durgesh.

  • System error in opening a query

    hi guys,
    this is the error i'm getting when opening this query which i need for my CR
    Abort System error in program in SAPLRR12 and form cell_fuellen_acell-01
    Diagnosis:
    This internal error is a targeted termination since the program has an
    incorrect status.
    what is needed to be done here
    Your help will be rightly appreciated
    Thanks

    Hi Vj,
    Please check the SAP notes as below, which seems to be relevant for your issue.
    Assign points it useful.....
    Symptom
    There are errors in Business Explorer components such as Analyzer, Browser, Form Reporting, Web Application Designer, Query Designer, Map, OLE DB for OLAP Provider
    Solution General information
    This note contains information about BW 3.0A front end patch 3. Here, you will find the most important information on:
    Installation
    Error corrections
    New features
    Additional general information that is not specifically for this BW front end patch.
    Procedure
    Downloading BW front end patches via FTP from sapserv
    Downloading a BW front end patch via Online Correction Support (SAPnet)
    Preparing the Installation Server
    Checking the Installation Server
    Installation on PC
    Checking the PC
    Problems during the installation of the BW front end Patch
    Distributing a patch per script (for administrators only)
    Installation
    During the installation of the BW front end patch, note the following:
    (This area is constantly updated)
    The BW 3.0A front end patch 3 is based on the SAP GUI 6.10 Presentation CD 1 (6.10 Final Compilation 3, material number 50051811) and the SAP GUI 6.10 patch 12 or higher.
    The BW 3.0A front end patch 3 contains all files, to convert a BW 2.0B/2.1C front end into a BW 3.0A front end.
    The BW 3.0A front end is downward-compatible to BW 2.0B/2.C.Thus, it can also be used on BW 2.0B/2.1C backend systems.
    When you use the Web Application Designer, implement at least BW 3.0A Support Package 03 (see note 425995).
    Error corrections
    This BW front end patch corrects the following errors in particular:
    in SAP Business Explorer Analyzer
    Displaying document links on filter cells and text elements
    Improved performance for low-speed connections (WAN)
    Bug:Incorrect language when starting documents in the Web browser (refer to note 450200)
    Bug:Import of missing styles does not import the color palette anymore (refer to note 450194)
    Bug:Various problems during the server logon as of Release 2.0 (incorrect list of Goto destinations, incorrectly indented hierarchy symbols...)
    Bug: Starting jump destinations in the Web does not work
    in BEx Query Designer
    The system does not correctly interpret characteristics that were selected as being unique in each cell and when it checks these characteristics, it mistakenly reports them as being defined non-uniquely.
    After you called the cell editor, you had to press the toolbar buttons twice to call the required function.
    In the cell editor, you could change the formula cells but not the formulas of the columns or of the rows because the system displayed all references to other columns or rows as 25 digit numbers.
    When you use Save as ... for queries with formula cells, these cells are not copied.
    When you used the Save as ... function for queries with cells, the copied query sometimes displayed the message "Brain 299 SAPLRRI2 Form CELL_FUELLEN_ACELL-01-" when it was executed.
    When you used the Save as ... function for queries with formula cells, these cells were not copied.
    in Variable Editor
    Formula variables that were replaced with the "To" value in intervals, were displayed without the "To" selection when you changed them.
    in SAP Business Explorer Browser
    Drag&Drop of Japanese file names on Japanese WinNT computers is now supported
    Temporary files are automatically deleted when the BEx Browser is exited
    New features
    New features delivered with this BW front end patch:
    SAP Business Explorer Analyzer
    Delete function in dialog "Open -> Views"
    Displaying documents for text elements and filter values
    Now the BW front end is installed in a separate program folder in the start menu. The folder is called 'Business Explorer'.The setup only allows you to change the name of the folder of the SAP front end.
    Procedure
    1. Downloading the BW front end patch via FTP or SAPnet
    2. Preparing and checking the installation server
    3. Installing and checking on the PC
    Note that you cannot install a BW front end patch directly on a PC (also see the 'Distribution of a patch by script' section).
    The check of every step with SAPBEXC.XLA avoids unnecessary subsequent problems.
    Downloading BW front end patches via FTP from sapserv
    Downloading patches from the sapserv is described in note 96885, "Downloading a front end patch from SAPSERVx".
    The BW 3.0A front end patches and the SAP GUI 6.10 patches are in the directory
       sapservX/general/frontend/patches/rel610/Windows/Win32
    The file name of the BW front end patch is
       BW30A_n.EXE (where 'n' is the number of the BW front end patch)
    The file name of the SAP GUI patch is
       GUI610_n.EXE (where 'n' is the number of the SAP GUI patch)
    In general, you can use the highest existing SAP GUI patch.The above-mentioned number of the SAP GUI patch is the minimum requirement.
    Downloading a BW front end patch via Online Correction Support (SAPnet)
    You can also download BW front end patches in the SAPnet.The URL for the SAP Online Correction Support is:
       http://service.sap.com/swcenter-main
    After you select SAP BW/SAP BW 3.0A/Binary Patches/SAP GUI for Windows 6.10/Win32 in the tree on the right side, the SAP Download Area appears on the left side.
    Here you can select BW30A.EXE and, if necessary, GUI610.EXE for downloading.
    In general, you can use the highest existing SAP GUI patch.The above-mentioned number of the SAP GUI patch is the minimum requirement.
    Preparing the Installation Server
    The installation of patches on the installation server is described in note 361222. Follow the instructions in this note.
    A BW front end patch contains all files from the previous patches, so that you only need to install the latest patch.
    Checking the Installation Server
    Note 197460, "BW front end Checktool sapbexc.xla", describes how easily and quickly you can check the installation server.
    Installation on PC
    The BW front end patch is installed by executing the SAP GUI setup.In the setup, you must select the BW add-ons component to install the BW front end.
    See also the section distribution of a patch per script.
    Checking the PC
    Note 197460, "BW front end Checktool sapbexc.xla", describes how simple and fast the local installation checks a PC
    The local execution of SAPBEXC.XLA is necessary if you sent problems to the SAP Support (see note 142705).The status of a PC can be checked with the result of SAPBEXC.XLA.
    Problems during the installation of the BW front end patch
    If problems occur during the installation of the BW front end patches, you should install the BW front end patch again and use the following method for this:
    First, remove the BW front end with "Remove" menu option under "SAP front end" from your local PC.
    Afterwards you can install the front end programs again with the setup program of your setup server.The setup program has been delivered with the front end CD.You must have administrator rights on the local PC.During the setup, no other programs (for example, Excel) should run.
    Certain programs save information on OLE components in special files.These files are not updated automatically during a new installation, therefore, when you change the OLE component during the installation, old information may remain in the system.We recommend you delete all files with the extensions ".EXD" and ".OCA" before you carry out the new installation.
    Distributing a patch per script (for administrators only)
    There is a large number of products for the distribution of software (for example, Microsoft SMS, IBM Tivoli, NetSupport NetInstall), so that no individual Support is possible when you use SAP and BW.There are two general notes about the front end installation (153341 and 194859), to which the system also refers.
    The following remarks are intended for administrators who want to distribute a BW front end patch with such a software.
    A BW front end patch consists of several files in different directories. These directories correspond to the directories on the installation server or on the CD.The files are usually distributed into the following directories on the local PC:
    c:\program files\common files\sap\system
    c:\program files\sappc
    c:\winnt\system32 or c:\windows\system
    In the sapbexc.xla file on the "Version" tab, there are notes about where the file must be copied to and whether it must be registered.
    For the preparation of a script, first you should make a normal installation on a local PC from the installation server which must be checked with sapbexc.xla (see note 197460).Afterwards you can localize the corresponding directory of a file using this PC.In general, each DLL and each OCX must be registered if it can be registered.After the installation per script, a deinstallation may no longer work, therefore, before registering a file with regsvr32.exe <Path\File>, you should execute the script for an unregistration with regsvr32.exe /U <path\file>.
    Currently, the sapbexc.xla checktool may not be able to recognize certain installation errors (copy without registrations) (see note 206609).
    SAP offers support for problems with incorrect scripts for distributing patches.
    Best Regards,
    DMK
    Assign Points if it helps....

  • Error while checking/executing a bex query

    Hello,
    I am executing a report made on a multiprovider, on checking the query gives an error (BRAIN 299)
    'System error in program CL_RSR_LFMM & form GET_CHANM-01-'
    What could be the problem?

    hi,
    chk the links that could help
    Brain Errors in query
    /thread/196115 [original link is broken]
    BW Explorer: BRAIN 632 error message when calling a query
    Ramesh

  • Error while checking and executing a report

    Hello,
    I am executing a report made on a multiprovider, on checking the query gives an error (BRAIN 299)
    'System error in program CL_RSR_LFMM & form GET_CHANM-01-'
    What could be the problem?

    HI,
    This is a SAP program error.
    Please check if the note helps as i dont have information about your SP levels and BW version.
    Check this note 973345.
    Regards,
    Nitin Pardeshi

  • Error  while executing query through rsrt

    hello experts,
    I am facing following error while executing one HR query through rsrt.
    "System error in program SAPLRRI2 and form REP_ASSIGN_INITIAL_OPT-01- (see long text) "
    while executing query through rsrt it automatically goes to debug mode, coming out of debug mode i get the screan showing above error message.
    What would be an issue?
    Regards,
    Nirav
    Edited by: Nirav Shah on Apr 21, 2008 8:19 AM

    Hi ramesh,
    I havent kept any execlusion selection. Though i saw long text, it is like this:
    "Diagnosis
    This internal error is an intended termination resulting from a program state that is not permitted.
    Procedure
    Analyze the situation and inform SAP.
    If the termination occurred when you executed a query or Web template, or during interaction in the planning modeler, and if you can reproduce this termination, record a trace (transaction RSTT).
    For more information about recording a trace, see the documentation for the trace tool environment as well as SAP Note 899572.
      Notification Number BRAIN 299 "
    Regards,
    Nirav

Maybe you are looking for