A short dump occurs when accessing SAP BI 7.0 using GUI 620

hi,
i'm getting this error while executing..DTP.
solve this .....

Hi,
BI 7.0 will not work with SAP GUI 6.20.
Take a look at this SAP note.
Maintenance strategy / deadlines 'SAP GUI'
SAP Note Number: [147519|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_fes/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d313437353139%7d]
Compatibility - 6.20
SAP GUI for Windows 6.20 is compatible with products based on SAP Web Application Server 6.40/7.00/7.01/7.02 and all earlier releases of SAP Software which are still supported by SAP (this includes extended maintenance).
Exceptions to this rule are
BI 7.0: Requires new frontend components shipped only together with SAP GUI for Windows 6.40 as of compilation 4. For BI 7.0 you definitely need at least this compilation CD. For further information on this please check the master guide for SAP NetWeaver 2004s components and documentation center at
http://service.sap.com/~sapidb/011000358700004970342005E/051024Instguides.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/b2/e50138fede083de10000009b38f8cf/frameset.htm
SCM 5.0: Requires a new frontend component which is integrated into SAP GUI for Windows 6.40 (also see note 889989).
SAP GUI for Windows 6.20 is not compatible with SAP Systems based on SAP Web Application Server 7.10 and higher.
Additional:
Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
and
Frontend requirements - page 11
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
and
Re: GUI 640
Regards
Andreas

Similar Messages

Runtime error SQL error 3114 occurred when accessing program CX_ w

Hi Friends,
Iam in a big mess . I have one query based on one my Zinfocube.This query ia attached in the workbook .. Previuolsy all was fine , but now whever iam executing this query it is throwing me the exception
Query 0: Runtime error SQL error 3114 occurred when accessing program CX_ with parallel processing via RFC.
and
Beim Lesen der Daten sind Fehler aufgetreten. Navigation ist mÃ¶glich
I am not able to get the cause of error ..
Can anybody help me in this regrd as its a bit urgent.
Thanks in advance..

Hi , thanks for replying ,
I have tried running query through RSRT also , its not working still it is giving me the same error .
In st22 it is showing me the follwing dump.
DBIF_REPO_SQL_ERROR
Short text
    SQL error 3114 occurred when accessing program
What happened?
    The system is no longer linked to an ORACLE instance.
    No further operations can be performed on the database.
What can you do?
    You cannot eliminate this error yourself.
    Please inform your database administrator.
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    The system attempted to access an ORACLE instance to which
    it is no longer linked.
    This situation may arise because the ORACLE instance
    has been stopped due to an error or an external operation.
How to correct the error
    Database error text........: "ORA-03114: not connected to ORACLE"
    Triggering SQL statement...: "CX_SQL_EXCEPTION==============CP "
    The current status of the ORACLE instance cannot be determined.
    It may be still inactive or the database administrator may have
    restarted it.
    In any case, all systems that have accessed the ORACLE instance
    must be restarted after the ORACLE instance has been restarted.
    If you were working on a central system, inform
    your system administrator.
    If you were working on an external local system, inform
    the person responsible for this system.
    If you were working on your own local system, restart
    the system yourself.
    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:
    "DBIF_REPO_SQL_ERROR" " "
    "CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
    "NEXT_PACKAGE"
    If you cannot solve the problem yourself and want to send an errornotification 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)".
2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to 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:
"DBIF_REPO_SQL_ERROR" " "
"CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
"NEXT_PACKAGE"
Thanks in Advance..

Error message in TRFC 'An SQL error occurred when accessing a table'

Hi all,
Can any one tell what this below error message is about in while go into TRFC
'An SQL error occurred when accessing a table'.
and please tell me how to solve this problem.

Hi
Try to see what all tables are accessed by data source. and see if there is any lock on that..
If some other job is accessing that table - then there might be lock on that which is causing failure..
1) Try looking at ST22 dump also..
2) Try to do RSA3 in R/3 and if see if its is fetching any records or not..
Hoep it helps
--SA

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
   select * from zint_data
             nto table izint_d2 . "PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
     w_date1 like sy-datum .
DATA:
     w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
             into table izint_data PACKAGE SIZE 3000
             where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
endselect.
select * from zint_msgs
             into table izint_msgs PACKAGE SIZE 3000
              where CREATED_ON <= w_date2.              " ZERO
endselect.
select * from zint_data
             into table izint_d2 PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.
select * from zint_msgs
             into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2.                            " VALUE
endselect.
select * from zint_data
            into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
            into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4 ,            cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

SQL Error 3114 occured when accessing program CX_

Hi there,
I have build an infoset on a infocube and ODS. On this infoset I've build a query using a calculated key figure: Availibility%
Inside this key figure I have 2 restricted key figures: Allocation and Availibility
When I execute this query I get the error: "SQL Error 3114 occured when accessing program CX_"
If I remove the calculated key figure from the columns it works fine. If I place one of the 2 restricted key figures in the query it also work fine. But If i place both the restricted key figures in the columns, I also get the error. Or If I place the calculated key figure in the columns, I also get the error. Does somebody know what the problem is?

No they don't show me the problem. I've executed with RSRT transaction and I;ve got this error with the ABAP-debugger:
error in >> l_repid       <<
            >> l_include     <<
            >> l_source_line <<

Short dump (CALL_FUNCTION_FORMAT_NOT_SUP) when testing RFC connection

Hello!
I'm trying to test a RFC connection through SM59, but I'm getting the following short dump: CALL_FUNCTION_FORMAT_NOT_SUP (RFC data format not supported).
This RFC will connect to Biztalk, and this dump started occurring when Biztalk changed their codepage from 1100 to 4102.
On my SAP system the codepage is set to 1100.
There is no option to set the system as Unicode or non-Unicode on SM59, since I don't have the "Special Options" tab (My release is 4.6C).
How can I make this connection even with the different codepages?
Thanks in advance!

Hello Pedro
This is the PI forum, which is for PI technical issues. This post is not related to PI.
P.S. Please also familiarise yourself with the forum Rules of Engagement - https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement. Please do not Cross post.
Regards
Mark Smyth
XI/PI Moderator

Short Dump Error when we check the Data Source in RSA3

Hi. Experts.
                   We are using Data Source 2Lis_13_VDITM and when we try to check in RSA3
for recorts it is going short dump. I am just providing the error information.
              An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
clause.
               Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exception is:
When importing the object "MC13VD0ITM_TAB", the component no. 96 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX".
                    The data type is "N" in the dataset, but "X" in the program.
        Since I don't have much knowledge in ABAP, Please help me out regarding this issue. Suggest me possible solution and let me know if you need any further information.

Hi,
Try adding a TRY CATCH block in the extractor function module to catch the exception.
For the type mismatch you will have to make sure the variables are of same type or they can be type converted.
Use the debug mode of RSA3 to find what data is being exchanged.
You will need to change your extractor to avoid the dump.. or ensure that the value being passed to that object is correctly being passed(correct format)
Cheers
Kiran

ABAP Short Dump Occurring

Hi All
We had do done a DBEXPORT of our R/3 4.6C while doing there was a increment conversion pending and we got error during the export, we finished the conversion and then started the DBEXPORT again and it completed successfully, however after this we are receiving ABAP Short dumps which says DBIF_RSQL_INTERNAL_ERROR, Internal error when accessing table "T179 ". Practically for any new entry we do in database.Kindly suggest how to go about.
Regards
Arun

Hi Micheal
we had done an incremental conversion for DBTABLOG table which is forbidden also was not complete,so we completed the conversion and removed a field which was added in the table (this was cause of error),we removed the field and activated teh table and the short dump was resolved.
Anyway thanks for your reply.
Arun

Short dump error when extracting from one of the datasource in R/3 to BW

When extracting from one of the datasource I am getting the short dump. below is the source code of the same.
Source code extract
Get boundaries of next TID block
L_FROM_INDEX = L_TO_INDEX + 1.
IF L_FROM_INDEX GT NFILL. EXIT. ENDIF.
L_TO_INDEX   = L_TO_INDEX + L_BLOCK_SIZE.
IF L_TO_INDEX GT NFILL.
L_TO_INDEX = NFILL.
L_BLOCK_SIZE = L_TO_INDEX - L_FROM_INDEX + 1.
ENDIF.
Create hashed index on TID of TID table
CLEAR L_TH_TID_IDX.
LOOP AT TIDTAB FROM L_FROM_INDEX TO L_TO_INDEX.
L_S_TID_IDX-TIDIX = SY-TABIX.
L_S_TID_IDX-TID   = TIDTAB-TID.
COLLECT L_S_TID_IDX INTO L_TH_TID_IDX.
ENDLOOP.
Select TID block from STATE table
SELECT * INTO TABLE L_T_STATE
       FROM ARFCSSTATE FOR ALL ENTRIES IN L_TH_TID_IDX
       WHERE ARFCIPID   EQ L_TH_TID_IDX-TID-ARFCIPID
         AND ARFCPID    EQ L_TH_TID_IDX-TID-ARFCPID
         AND ARFCTIME   EQ L_TH_TID_IDX-TID-ARFCTIME
         AND ARFCTIDCNT EQ L_TH_TID_IDX-TID-ARFCTIDCNT
       ORDER BY PRIMARY KEY.
Consistence check
DESCRIBE TABLE L_T_STATE LINES L_LINES.
IF L_LINES NE L_BLOCK_SIZE OR
   L_LINES EQ 0.
MESSAGE X097(SY).
ENDIF.
PERFORM DELETE_BATCH_JOB
        USING    L_T_STATE
        CHANGING L_S_TID1.
Update LUW-Status und Zeit
CLEAR L_T_STATE_IDX.
CLEAR L_TH_TID2_IDX.
CLEAR L_T_TID.
LOOP AT L_T_STATE INTO L_S_STATE.
L_S_STATE_IDX-TABIX = SY-TABIX.

Hi Pavan,
                 This is a table space error.
Regards,
rahul

Short dump OBJECTS_OBJREF_NOT_ASSIGNED when activating infoobjects

Hi Experts,
We are getting a short dump when activating bussiness content infoobject which contain attributes, for e.g. 0COSTCENTER.
We are not getting the same dump when activating infoobjects whith out attributes.
We found a note 1019055 that recomends install sp13 or install six or seven notes for an emergency issue.
The problem is that if we install sp13 we will get out of stack.
What is your recomendation in this case? we are afraid that the problems will continue until we don't implement the sp13.
Thanks!

use t-code SNOTE to implement the OSS note you mentioned ,if it doesnt work you can always revert back to old status by doing Reset.
Hope it Helps
Chetan
@CP..

Dump occures when deleting seletion value in selection tab

I created an infospoke and limited one of the fields in the selection tab ( only one plant ).
When I tried to delete the above limit, I was able to activate without errors, execute in background, but not execute dialog. (a dump occurred).
At the Monitor, the extraction ended successfully, But the transformation ended with errors with the message "process was cancelled without additional error message".

Hi Caspi,
Try this and let me know.
Set the filter value for 0RECORDTP (record type) to 1. In this way, all markers are extracted that are in the compressed data from the InfoCube. You can extract non-cumulatives in which you compress the InfoCube in regular intervals and, afterwards, extract with 0RECORDTP = 1.
Thanks
Ramu

How to Access SAP ECC 6.0 using HP model Omni 10 (with windows 8.1) tab

Dear Experts
can anybody guide me to access SAP using TAB, where it has windows 8.1 o/s and manufactures are claimed it support all applications.
which SAP client version to be loaded in this tab, what are the config steps to be followed etc
Kindly revert.
Thanks
Venugopal

Hi Ravidra
Have u solved the probelm I also have the same problem when i move the groups from node1 to node2 manually my 2 servrces 00 and 01 are failed not able to bring up again. If You solve the problem please guide me the solution to solve this.
THanks in advance

C++ Debug Assertion Failed! - when printing with LOCL method G and GUI 620

Hi all
I've just raised an OSS message with SAP but don't think they'll help as the GUI version is no longer supported... if anyone else has come across this though and has any suggestions that would be great...
Thanks
Ross
Hi
We recently upgraded a few users to the 720 SAP GUI and had issues with LOCL printing, as we were still using the older "F: Printing on Front End computer" method of printing. As per SAP Note "Note 821519 - Front-end printing with control technology" the solution is to use method "G: Front end printing with Control Tech".
However, we now get an issue with SOME users who are running the SAP GUI 620 patch 57. When they try and print to LOCL they get a pop up dialog box error:
"Microsoft Visual C++ Debug Library
Debug Assertion Failed!
Program: C:\Program Files\SAP\FrontEnd\SAPgui\saplogon.exe
File: fputs.c
Line: 48
Expressiom: steam != NULL"
I appreciate that this old GUI is no longer supported BUT the SAP note states that 620 patch 56 is the minimum level for method "G" to work - and previous testing showed that it DID work ok. It seems only some of the 620 patch 57 users are affected - just wondering if you can advise why and if there is a 'quick fix' for this, perhaps an updated fputs.c file or something?
The issue is that we literally have thousands of users on this version and cannot roll out 720 quickly enough & without some additional testing/costs etc. We have a 710 patch 18 version we can roll out but this can cause IE8 issues... neither do we wish to revert to control method "F" as this will then 'break' printing for those users.
We have created a LOCL_OLD printer with method "F" but some users (for various reasons, including hard coded printers in bespoke transactions) cannot select this and have to use LOCL...
If you are aware of the C++ debug assertion error and have any possible solutions that would be much appreciated.
Many thanks
Ross

> I appreciate that this old GUI is no longer supported BUT the SAP note states that 620 patch 56 is the minimum level for method "G" to work - and previous testing showed that it DID work ok. It seems only some of the 620 patch 57 users are affected - just wondering if you can advise why and if there is a 'quick fix' for this, perhaps an updated fputs.c file or something?
fputs.c is a source file that is used to compile the GUI. The assertion is thrown because an expected condition is not met. So even if you would take out the assertion, there's no guarantee it'll work because "something" on the operating system is not right.
I suggest you compare installed software and windows hotfixes on the affected PCs vs. those who don't show this error. The error may also be that after the installation of the SAPGUI another software product was installed that replaced certain DLLs that are also used by the SAPGUI.
Markus

RSPC is not accessing as Short dump occurs

Hi friends,
I am accessing the tcode : rspc and when i login for first time, i choose network instead of tree and so system went to dump .
i want to rectify it . plzz help me with solution.
Regards,
Rajesh

Hi,
Check the notes 946481 & 528408.
Hope it helps.

A short dump occurs when accessing SAP BI 7.0 using GUI 620

Similar Messages

Maybe you are looking for