‎2019 Aug 30 8:20 AM
dear all,
it almost drive me crazy!
ver.752,BW,when i want to install infoproviders it dumps!
can anybody tell me why?is there any setting i missed?


‎2019 Aug 30 9:34 AM
Hi Yoshi HERO,
The screenshots details is not much to analyse. You can download the dump & attach here. You can also check in SM21 for any obstacles occurring at that time. Generally for Infoprovider install, could you please cross-check the dependencies as well as version-compatibility.
Please also check the below,
https://answers.sap.com/questions/12203683/error-messagetypex-while-running-tcode-rsa1-for-th.html
https://answers.sap.com/questions/973448/messagetypex.html
https://answers.sap.com/questions/6932758/reset-controlling-area-in-user-profile.html
Thanks,
Kaushik
‎2019 Sep 02 4:15 AM
sorry,this is ST22 error report.
Category ABAP programming error
Runtime Errors MESSAGE_TYPE_X ABAP Program CL_FCOM_IP_HRY_READER=========CP
Application Component CO
Date and Time 2019.09.02 08:51:34
Short Text
The current application has triggered a termination with a short dump.
What happened?
The current application program has detected a situation that should not occur.A termination with short dump has therefore been triggered by the key word MESSAGE (type X).
What can I do?
Note which actions and entries caused the error to occur.
Consult your SAP administrator. Using transaction ST22 for ABAP dump analysis, you can view, manage, and retain termination messages for longer periods. 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
Short text of the error message:
Internal error; contact your system administrator Long text of the error message:
Technical information about the message:
Message class....... FCOM_PLANNING_CORE
Number.............. 002
Variable 1..........
Variable 2..........
Variable 3..........
Variable 4.......... " "
How to correct the error
If the error occurs in one of your own ABAP programs or an SAP program that you have modified, try to correct the error yourself. 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:
"MESSAGE_TYPE_X" "CL_FCOM_IP_HRY_READER=========CP" bzw. CL_FCOM_IP_HRY_READER=========CM "CONSTRUCTOR"
If you cannot solve the problem yourself, please send the following information to SAP:
1. The description of the problem (short dump) To do this, choose System -> List -> Save -> Local File (unconverted) on the screen you are in now.
2. The relevant 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: The source text of the programs To do this, please choose "Other Utilties -> Upload/Download -> Download".
4. Details regarding the conditions under which the error occurred or which actions and input caused the error.
System environment
SAP Release..... 752
SAP Basis level 0001
Application server... sapq01
Instance name....... sapq01_Q01_00
Operating system... Linux
Release.............. 4.4.73-7-default
Hardware type....... x86_64
Character length..... 16 Bits
Pointer length........ 64 Bits
Work process number... 25
ABAP load version.... 2326
Shortdump setting. full
Database server... hanadb02
Database type..... HDB
Database name..... Q01
Database user ID SAPABAP1
Terminal.......... PC201706081002
Character set C SAP kernel.......753
Created on....... Mar 12 2018 23:06:46
Created at....... Linux GNU SLES-11 x86_64 cc4.8.5 use-pr180312
Database version SQLDBC 2.02.023.1499440855
Patch level....... 100
Patch text.......
Database............. HANA 1.0, HANA 2.0
SAP database version. 753
Operating system... Linux
Memory consumption
Roll.... 0
EM...... 1521529146
Heap.... 0
Page.... 548864
MM used. 1489908856
MM free. 24705976
Information on where terminated
The termination occurred in ABAP program or include
"CL_FCOM_IP_HRY_READER=========CP", in "CONSTRUCTOR". The
main program was "RSAWBN_START".
In the source code, the termination point is in line 27 of program or
include "CL_FCOM_IP_HRY_READER=========CM001".
Line SourceCde
1 METHOD constructor.
2 DATA:
3 l_oltpsrc TYPE rsaot_oltpsource.
4
5
6 d_hieid = i_hieid.
7 "chanm must be set from the sub class!
8 MOVE i_parameters TO d_chanm.
9 "determine, which data source is used
10 d_datasrc_hry = get_datasrc( d_chanm ).
11 l_oltpsrc = d_datasrc_hry.
12
13 CALL FUNCTION 'RSA1_SINGLE_OLTPSOURCE_GET'
14 EXPORTING
15 * I_WITH_BUF = ' '
16 i_oltpsource = l_oltpsrc
17 i_objvers = 'A'
18 IMPORTING
19 e_s_oltpsource = ds_oltpsrc
20 EXCEPTIONS
21 no_authority = 1
22 not_exist = 2
23 inconsistent = 3
24 OTHERS = 4.
25 IF sy-subrc <> 0.
26 * Implement suitable error handling here
>>>>> MESSAGE x002.
28 ENDIF.
29
30
31 SELECT SINGLE * FROM roohiecat INTO ds_ohiecat
32 WHERE oltpsource = l_oltpsrc
33 AND objvers = 'A'.
34 IF sy-subrc <> 0.
35 "Internal error -> must exist in the system configuration
36 MESSAGE x002.
37 ENDIF.
38
39
40
41
42 ENDMETHOD.
‎2019 Aug 30 10:07 AM
‎2019 Sep 02 8:55 AM
If you search SAP notes (as explained in the short dump), you get these ones: