Dump CONNE_IMPORT_WRONG_COMP_TYPE

Good Day Guru's I need your help please, I would appreciate some guidance on this that.
Errores tiempo ejec. CONNE_IMPORT_WRONG_COMP_TYPE
Excepción CX_SY_IMPORT_MISMATCH_ERROR
Texto breve
Error when attempting to IMPORT object "TS_CHECK".
The current ABAP program "SAPLSTD1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Anál.errores
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 "DB_ORA_CRIT_OBJ___FREESPC_STAT" "(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 "TS_CHECK", the component no. 4 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLSTD1".
The data type is "I" in the dataset, but "N" in the program.
Notas para corregir errores
Try to find out why the type of the object should be different.
There are various possible options:
1. The type of the imported field has changed in the Data Dictionary.
Make sure that the type of the imported field matches the type
of the field in the Data Dictionary.
If the data cannot be restored from another source, the data must be
read by the 'old' structure, converted und again eported with the new
structure, so that future IMPORTs will always function with the new
structure.
2. A new program version is active, which no longer fits the dataset.
Try to solve the error generating the program "SAPLSTD1" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "SAPLSTD1". Then activate the function 'Generate'.
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)".
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.
The exception must either be prevented, caught within proedure
"DB_ORA_CRIT_OBJ___FREESPC_STAT" "(FUNCTION)", or its possible occurrence must
be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
SAP-Release 700
Operating system..... "AIX"
Release.............. "5.3"
Database............. "ORACLE 10.2.0.."
Thanks in advance.

Then you may need to check the following note:
[Note 1347224 - CDMCCA:CONNE_IMPORT_WRONG_COMP_TYPE dump in Ext.Runtime Anal|https://service.sap.com/sap/support/notes/1347224]
[Note 1286192 - CDMC CA:CONNE_IMPORT_WRONG_COMP_TYPE during Ext. Runtime Ana|https://service.sap.com/sap/support/notes/1286192]
[Note 997535 - DB02: Problems with History Data|https://service.sap.com/sap/support/notes/997535]
[Note 941369 - upgrade of notes 738979 and 753876 to higher releases.|https://service.sap.com/sap/support/notes/941369]
Regards,
Dipanjan

Similar Messages

DUMP: CONNE_IMPORT_WRONG_COMP_TYPE /CX_SY_IMPORT_MISMATCH_ERROR

Hi guru,
i have this dump:
Errori run-time        CONNE_IMPORT_WRONG_COMP_TYPE
Eccezione              CX_SY_IMPORT_MISMATCH_ERROR
       Verific. il     18.04.2008 a 11:52:00
Error when attempting to IMPORT object "GT_YBKPF_ALV".
Causa dell'errore
Error in ABAP application program.
The current ABAP program "ZAUT_PAGAMENTO_NEW" had o be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data type of the stored data was not the same as that specified in the
program.
Possibili soluzioni
Print out the error message (using the "Print" function)and make a note of the actions and input that caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer termination messages, especially those beyond their normal deletion date.
Analisi errori
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
was neither
caught nor passed along using a RAISING clause, in the procedure "PRINT"
"(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When importing the object "GT_YBKPF_ALV", the component no. 97 in the
dataset has a different type from the corresponding component
of the target object in the program "ZAUT_PAGAMENTO_NEW".
The data type is "N" in the dataset, but "P" in the program.
Indic. per la correzione
The exception must either be prevented, caught within the procedure "PRINT"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Try to find out why the type of the object is different.
There are several possible reasons:
|
--- In the ABAP Dictionary, the type of the imported
|   field has changed. Make sure that the type of the imported
|   field matches the length of the Dictionary field.
|
|   If the data could not be restored from another source, this data
|   must be read with the "old" structure, then converted and exported
|   back with the new structure, so that future IMPORTs always work
|   with the new structure.
|
--- A new program version is active, and it no longer matches the
    dataset. Try to solve the error by generating the program
"ZAUT_PAGAMENTO_NEW" again
    as follows:
    In the SAP System, choose the transaction SE38. Enter the program
    name "ZAUT_PAGAMENTO_NEW". Then choose the "Activate" function.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
                                                                                2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
Informazioni punto di interr.
The termination occurred in the ABAP program "ZAUT_PAGAMENTO_NEW" in "PRINT".
The main program was "ZAUT_PAGAMENTO_NEW ".
The termination occurred in line 2922 of the source code of the (Include)
program "ZAUT_PAGAMENTO_NEW"
of the source code of program "ZAUT_PAGAMENTO_NEW" (when calling the editor
29220).
Processing was terminated because the exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in the
procedure "PRINT" "(FORM)" but was not handled locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "ZAUT_PAGAMENTO_NEW ". Its source code starts
in line 2777
of the (Include) program "ZAUT_PAGAMENTO_NEW ".
Can you HELP ME please!
Best regards.
Edited by: Diego Garofalo on Apr 18, 2008 4:52 PM

Hi All,
For the first time:
Try to import the data to the IT with old structure (say 32 fields)
         IMPORT ty_data = it_temp_old FROM DATABASE indx(sp) TO wa_indx ID obj.
   2. Append the data it_temp_old to new structure it_temp_new.
          EXPORT ty_data = it_temp_new TO DATABASE indx(sp) TO wa_indx ID obj.
For the next time:
Edit the IMPORT statement.
         Import the data to IT with new structure (40)
         IMPORT ty_data = it_temp_new FROM DATABASE indx(sp) TO wa_indx ID obj.
   2. Perform the required Operations and export the same data with new structure(40).
         EXPORT ty_data = it_temp_new TO DATABASE indx(sp) TO wa_indx ID obj.
Thanks,
Shameer.

Dump "conne_import_wrong_comp_type" during client copy

Hi gurus!!
Last week I tried to run a client copy with SAP_CUST profile but the next dump was generated:
Runtime Error CONNE_IMPORT_WRONG_COMP_TYPE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Error when attempting to IMPORT object "TLINE".
What happened?
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data type of the stored data was not the same as that specified in the program.
Error analysis
An exception occurred. This exception is dealt with in more detail below. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
was neither caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception to occur, the running program was terminated.
The reason for the exception is:
When importing the object "TLINE", the component no. 1 in the dataset has a different type from the corresponding component of the target object in the program "SAPLSTXD".
The data type is "N" in the dataset, but "C" in the program.
I checked that the report SAPLSTXD had not been changed and I can't found the reason of the error.
Can anybody help me?
Thank you very much in advanced.
Edorta.

Hi nick
I have already checked the note and executed the corresponding report and it shows an incorrect text filtering with the information extracted from the dump.
I have eliminated this wrong text in STXL and rescheduled the client copy for toningth. Tomorrow we will see the results.
Thank you very much in advanced,
Edorta.

CONNE_IMPORT_WRONG_COMP_TYPE

Hi all,
After upgrading our R/3 system to ECC6, I am getting this dump CONNE_IMPORT_WRONG_COMP_TYPE with the message -
Error when attempting to IMPORT object "TB_TSP"
This happens with our monitoring tool Remedy when it tries to access database information.We are on Oracle 10.
I followed SAP note 533020 and it selected Group TB and deleted all lines from MONI foor this group but this error comes back.
What am i doing wrong?
Thanks
Cyrus

Hi Cyrus.
I would appreciate it if you could tell me if you ever managed to sort this issue out and if you did, could you point me in the right direction please?
Thanks for your time.
Mick.

DBIF_RSQL_SQL_ERROR - while dataloading from PSA to InfoCube!

Hi Friends,
I know this topic has been posted before too and i have gone through almost all the threads related to this topic but could not find the solution for this issue. Here is the details:
I am in Production and loading data to one the cube through PSA. Data comes fine till PSA (arround 1 million records). But when I am updating data to Infocube through DTP I am getting the following error:
Dump: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
when i click on the error it says the following:
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB'
According the previous threads on this issue its a Table space issue in Database. But I am sure its not table space issue as my other loads are successfull with much more number of records. I checked in DB02 too and see no problem with the table space.
I tried selective loading through DTP and my data load was successfull. But this is not the way we want to load the data. we dont want to give any selections in InfoPacakge.
I tried to see in ST22 and see the following dumps:
CONNE_IMPORT_WRONG_COMP_TYPE CX_SY_IMPORT_MISMATCH_ERROR
OBJECTS_OBJREF_NOT_ASSIGNED
CX_SY_REF_IS_INITIAL
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
I tried to delete infocube index first before load from PSA. but it did not work for me.
i would highly appriciate any help from ur side and will awarded with points.
Thanks,
Manmit

Thanks Srinivas. I can not reduce the package size because i am loading data from PSA to InfoCube through DTP. This DTP is created upon a data source which is a genereted export datasource i.e. 8XYZABC which does not allow me to change the package size and this is decided at run time. I can see the following under the Extraction Tab of DTP :
The package size corresponds to package size in source.
It is determined dynamically at runtime.
Any idea how to solve this prob?

CONNE_IMPORT_WRONG_COMP_TYPE short dump in DB02OLD transaction

Hi,
We have recently upgraded to SAP ECC 6.0 and in solution manager system, I am getting CONNE_IMPORT_WRONG_COMP_TYPE short dump for DB02OLD transaction (Program RSORAT5M).
I searched few notes like 657981 and others but all are applicable for DB02 transaction. If anyone encountered same problem, please let me know how to resolve the issue.
Thanks in advance,
Ni3

Solved on my own

Dump error in db02 CONNE_IMPORT_WRONG_COMP_TYPE

Dear All,
When use the t-code db02 and press refresh button for database + history check it give abap runtine error dump.
it gives this error as runtime error:
CONNE_IMPORT_WRONG_COMP_TYPE.
please guide me, it is happening both in Devlopment and well as in production server.
Thanks
Bhaskar

Hi,
check Note 657981 - CONNE_IMPORT_WRONG_COMP_TYPE in DB02 for RSORAUD1
also check Note 997535 - DB02: Problems with History Data.
regards
kaushal

Short Dump in Prod system in RSA3 for Datasource 2LIS_18_I0NOTIF...Help Pls

Dear Guru's
In our porod System in Tcode RSA3 when i give Dsource 2LIS_18_I0NOTIF and click on Extract i get Follwing Dump
I searched for the note but i did not found any thing proper
Here r Dump Details:-------
Runtime Error          CONNE_IMPORT_WRONG_COMP_TYPE
Exception              CX_SY_IMPORT_MISMATCH_ERROR
       Occurred on     13.08.2008 at   14:21:57
Error when attempting to IMPORT object "MC18I00NTF_TAB".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLMCEX" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data
type of the stored data was not the same as that specified in the
program.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_E
was neither
caught nor passed along using a RAISING clause, in the procedure
"MCEX_BW_LO_API" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When importing the object "MC18I00NTF_TAB", the component no. 2 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLMCEX".
The data type is "D" in the dataset, but "F" in the program.
How to correct the error
The exception must either be prevented, caught within the procedure
"MCEX_BW_LO_API"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Try to find out why the type of the object is different.
There are several possible reasons:
|
--- In the ABAP Dictionary, the type of the imported
|   field has changed. Make sure that the type of the imported
|   field matches the length of the Dictionary field.
||   If the data could not be restored from another source, this data
|   must be read with the "old" structure, then converted and exported
back with the new structure, so that future IMPORTs always work
with the new structure.
A new program version is active, and it no longer matches the
dataset. Try to solve the error by generating the program "SAPLMCEX" again
as follows:
In the SAP System, choose the transaction SE38. Enter the program
name "SAPLMCEX". Then choose the "Activate" function.
Can any one please kindly help....
Thanks

Hi,
so did you change anything at your datasource? Before transporting to prod, you need to delete the setup tables and then you need to run a delta to pick the latest delta records, then transport, replicate and activate the comm-structure. That will not effect your delta in prod. But again, for me the dump looks like a mismatch between the extract structure and the setup tables. You might have changed something after the setup tables have been filled. And additionally usually rsa3 is doing a full and so pulling the data out of the setup tables.
regards
Siggi

CONNE_IMPORT_WRONG_COMP_TYPE error

hello guyz were having a problem, where implementing a function module and a datasource to be extracted to used by BW, we have 4 different Cluster Dev Boxes, namely: CD1, GDD, TD1, and QD1, the said function Module works in the 3 boxes excpt the CD1 box, the function module dumps and return this error, the function module works well on 3 boxes, GDD, TD1 and QD1. Ive also check and the Function Module is also in the CD1 box already.. thank you very much in advance....
ABAP runtime errors CONNE_IMPORT_WRONG_COMP_TYPE
Occurred on 21.12.2005 at 09:48:26
Error when attempting to IMPORT object "MC12VC0ITM_TAB".
What happened?
The current ABAP/4 program "SAPLMCEX " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
When attempting to import data, it was discovered that the data
type of the stored data was not the same as that specified in the
program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.

hi,
take a look oss note 328181
Symptom
If you change an extract structure in the Customizing Cockpit (Transaction LBWE) by importing a support package, a transport or by carrying out an upgrade, this can cause various errors if it had already been activated for update for quite some time:
The initialization on data that was generated before the change no longer works (CONNE_IMPORT_WRONG_COMP_LENG).
Delta requests terminate (CONNE_IMPORT_WRONG_COMP_LENG).
The V3 update is no longer processed.
The update from the extraction queue (update mode "Delta Queued", as of PI(-A) 2002.1) does not finish.
The protocol terminates(CONNE_IMPORT_WRONG_COMP_TYPE)
A change to one of the LIS communication structures which are the basis for the extract structure or, in individual cases, also to further application tables (e.g. MSEG, inventory management) may lead to the same symptoms.
Other terms
LBWE, CONNE_IMPORT_WRONG_COMP_LENG, CONNE_IMPORT_WRONG_COMP_TYPE, IMPORT_ALIGNMENT_MISMATCH, CONNE_IMPORT*, IMPORT, V3, SM13, update, MCEX_UPDATE_02, MCEX_UPDATE_03, MCEX_UPDATE_04, MCEX_UPDATE_05, MCEX_UPDATE_05_1, MCEX_UPDATE_08, MCEX_UPDATE_11, MCEX_UPDATE_12, MCEX_UPDATE_13, MCEX_UPDATE_17, MCEX_UPDATE_17_1, MCEX_UPDATE_18, MCEX_UPDATE_18_1, MCEX_UPDATE_40, MCEX_UPDATE_43, MCEX_UPDATE_44, MCEX_UPDATE_45, MCEX_UPDATE_45_1, MCEX_BW_LO_API
Reason and Prerequisites
When you change a structure, the data which is stored in the old form of the structure can no longer be interpreted correctly.
Since changes can be also be made to extract structures (or to other update-relevant structures) as well as to basic data definitions for an R/3 upgrade or plug-in upgrade and (in very seldom cases) when importing an R/3 standard or plug-in Support Package, the precautions mentioned below should also be followed beforehand.
Solution
You should carry out the following steps before you change a structure:
1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
3. Load all data of the respective DataSource into the BW System.
Now you can make the change.
After a change you can no longer use the statistical data already recreated. If such data still exists, you should delete it (Transaction LBWG).
We recommend in particular to upload the data immediately after a restructuring and (after checking in BW) delete them from the restructuring tables.
Moreover, the update log (Transaction LBWF) can no longer be read. Post a document in this case so that the last log entry is overwritten. This log entry then has the correct new format of the extract structure.
As of PI 2000.2 the program RMCEXDELETELOG is available. It can be used to delete log entries.
Remark:
The program RMCEXDELETELOG is available in the current PI 2000.1 patch.
However, no success message is displayed.
You can also import the program from the sapserv computers. It can be found in the directory /general/R3server/abap/note.0328181. However, only German texts have been maintained.
If you forget to process the V3 update before a change the only option is to delete the records that still exist, that is, this data is lost.
To do this,
for V3 update methods, go to the update overview (Transaction SM13), select the records (user *, V2 executed, set date), and select Update records -> Delete -> All records. Do not forget to deactivate the flag "Only incorrect".
for update method "Delta Queued" (as of PI(-A) 2002.1) go to the logistics queue overview (Transaction LBWQ). Mark the queues for the applications concerned one after the other (MCEXnn, nn = number of the logistics application, see Transaction LBWE), and choose the display function. Then choose the display function again to list all entries of the queue. Then select and delete all entries that had been stored before the structure change. In case of a very large number of entries in a queue it may be required to delete the entire contents of the queue. This is possible already on the initial screen of Transaction LBWQ.

Function Module READ_TEXT short dump

Hi All,
I've created a bespoke long text object so I can save some long text to it. I created it by copying the SAP standard long text object for CATS (timesheets) in SE75. I save to this object using the function module SAVE_TEXT and I read it back using the function module READ_TEXT. I get a short dump during READ_TEXT which says:
"CONNE_IMPORT_WRONG_COMP_TYPE
Error when attempting to IMPORT object "TLINE".
When importing the object "TLINE", the component no. 1 in the dataset has a different type from the corresponding component of the target object in the program "SAPLSTXD ".
The data type is "I" in the dataset, but "C" in the program."
I've looked on OSS (as it's a SAP standard program) but can't find anything. I get no errors when trying to read the standard object CATS only when I try and read my new object, so I'm thinking that I haven't set it up correctly. An entry in table STXH occurs for both objects so I know I have saved some long text in my object.
Can anyone help?
Gill

Hi,
have you passed the correct parameters to the FM.
try to check the sample...
data: it_lines like tline occurs 0 with header line.
    CALL FUNCTION 'READ_TEXT'
         EXPORTING
              CLIENT                  = SY-MANDT
              ID                      = 'Z056'
              LANGUAGE                = 'E'
              NAME                    = L_NAME
              OBJECT                  = 'VBBP'
         TABLES
              LINES                   = IT_LINES
        EXCEPTIONS
             ID                      = 1
             LANGUAGE                = 2
             NAME                    = 3
             NOT_FOUND               = 4
             OBJECT                  = 5
             REFERENCE_CHECK         = 6
             WRONG_ACCESS_TO_ARCHIVE = 7
             OTHERS                  = 8
i think it is because of it_lines declaration.
Regards
vijay

Express Document: Update Terminated in VL02n -CONNE_IMPORT_WRONG_COMP_TYPE

Hello friends,
Am an abaper (fresher).
Actually i wanted spool to be generated when my delivery document is saved in transaction VL02n.
But when i save it and come out , am getting an error telling "Express document: Update terminated."
When i issue output to the delivery type am getting no response. But the status of the output type inside the document is processed (Green)
I have pasted below the SM13 error log.
Module Name Type Update Return Code
1 RV_DELIVERIES_SAVE V1 (no retry) Error
When i further look into it i get this error looking in ST22 it shows as mentioned below
00 671: ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE
( My print program has no syntax errors. I have passed the control parameters for preparing my smartform for spool to be generated when i save the delivery document. )
Could you please help me in solving this issue ?
Thanks and Regards
Kausthub

Hi Kausthub,
although the print programs has no errors, it is possible that the output itself causes an update error. I remember when I created a sapscript form I forgot to define firstpage as follow-up-page of firstpage. Whenever more than one page was created, I got a dump in update processing - like you got it now.
On the other hand, CONNE_IMPORT_WRONG_COMP_TYPE should not be related to this - there are some SAP notes applicable.
Regards,
Clemens

Dump in st22

Name of runtime error : CONNE_IMPORT_WRONG_COMP_TYPE
this error comes everyday, as basis user. It is related to database MONI,
can anybody help
Thanks in advance
B

A quick search for oss notes shows that there are several causes for this error. If your system was recently updated (or support packages where applied), oss note 997535 might be worth a try.
If this does not match your problem, post more information here (most of this information is written in the short dump):
- name of the ABAP causing this error
- name of the table affected
- history of you system (recent upgrades, recently applied basis support packages, ...)
Best regards,
Elmar.

Lock ups and dumping psyical memory!!!

Hi i have just installed a new pc most of the stuff im useing is from my old computer so i know they work fine im running a:
P4 3GHZ Prescot 800MHz, HT-Enabled
865PE Neo2-P
512 DDR-400 Twin moss
ATI Radeon 9000 pro
PSU-400
XP Pro
My computer locks up alot when running intense games (games have worked before no problem) i also get a error saying dumping pysical memory, i have looked about and tried to solve this myself, i found that someone was haveing the exact same problem as me and he fixed it by turning the FSB down as his memory wasnt compatable with his motherboard if doing that works how do i do it ?
Many thanks Jonathan

Flappa, Your memory " clock" is fine and there is no need to "underclock it" as long as you did not mess with the Bios.
I had the same problems. I could not even get thru a Clean install of windows as it would Blue Screen
1- are you running in " Dual Channel Mode"?
2- If so is your memory a " match Set"?
some times memory even thought it has the same markings is not matched . Dual channel sets are matched and made to run together in "Dual Channel Mode"{
( Even though I had the same manufacturer memory my set would not run in Dual Channel without " Blue Screening" I bought a Matched Set of Kingston Valueram and have not had a problem since
3- If it is not a matched set, pull one stick out and run it for a while , if it still bluescreens try the other stick
4- raise your memory voltage to 2.7 or 2.8 ( which ever is the lowest that it runs stable)
5- If all this does not work , run MEMTEST to see if there is a problem with both sticks
6- you are running a Bios Version that supports the " Prescott Microcode" right?
Let us know what your findings are
Good Luck
Dave

Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
    When changing or deleting one or more lines of the internal table
    "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
    the line index. An index less than or equal to zero is not
    allowed.
    The error can occur when using the following options:
    1. "INDEX idx" for specifying the line number in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
       where you want to change, insert or delete.
    2. "FROM idx" for specifying the start index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    3. "TO idx" for specifying the end index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    At the time of the termination, the table contained 17008 lines.
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove 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:
    "TABLE_INVALID_INDEX" " "
    "J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
    "FILTER_DATA"
    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)".
    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".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...

Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash

Short dump 'Table does not exist in database'

Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
    Table does not exist in database.
What happened?
    The table or view name used does not
    exist in the database.
    The error occurred in the current database connection "DEFAULT".
What can you do?
    Check the spelling of the table names in your report.
    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 that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
     caught in
   procedure "DYN_LIC_SEL_TOT" "(FORM)", 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:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.

Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.

Dump CONNE_IMPORT_WRONG_COMP_TYPE

Similar Messages

Maybe you are looking for