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.
Similar Messages
-
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 -
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. -
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,
ManmitThanks 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. <b>8XYZABC</b> 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 :
<b>The package size corresponds to package size in source.
It is determined dynamically at runtime.</b>
Any idea how to solve this prob? -
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
CyrusHi 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. -
Error in rules while updating from PSA to ODS
Hi Experts,
I am trying to load data from PSA to ODS using DTP. For about 101 records I get the following error:
"Runtime error while executing rule -> see long text RSTRAN 301"
On further looking at the long text:
Diagnosis
An error occurred while executing a transformation rule:
The exact error message is:
Overflow converting from ''
The error was triggered at the following point in the program:
GP4808B5A4QZRB6KTPVU57SZ98Z 3542
System Response
Processing the data record has been terminated.
Procedure
The following additional information is included in the higher-level
node of the monitor:
o Transformation ID
o Data record number of the source record
o Number and name of the rule which produced the error
Procedure for System Administration
When looking at the detail:
Error Location: Object Type TRFN
Error Location: Object Name 06BOK6W69BGQJR41BXXPE8EMPP00G6HF
Error Location: Operation Type DIRECT
Error Location: Operation Name
Error Location: Operation ID 00177 0000
Error Severity 100
Original Record: Segment 0001
Original Record: Number 2
Pls can anyone help in deducing and pointing this error to the exact spot in the transformation rule
Thanks & Regards,
RajHi Kazmi:
Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Short text
Error when attempting to IMPORT object "HIST2".
What happened?
Error in the ABAP Application Program
The current ABAP program "RSORAT4M" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
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 "AKT_DAY_HIST2" "(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:
When importing the object "HIST2", the component no. 8 in the
dataset has a different type from the corresponding component
of the target object in the program "RSORAT4M".
The data type is "I" in the dataset, but "P" in the program.
How to correct the error
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 "RSORAT4M" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "RSORAT4M". Then activate the function 'Generate'.
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:
"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"
"RSORAT4M" or "RSORAT4M"
"AKT_DAY_HIST2"
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 wit
"AKT_DAY_HIST2" "(FORM)", or its possible occurren
RAISING clause of the procedure.
Hope this helps.
Thanks to you and all
Raj -
Development server performance is slow [ Review the error and help me,]
Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Date and Time 24.12.2007 07:02:58
Short text
Error when attempting to IMPORT object "HIST2".
What happened?
Error in the ABAP Application Program
The current ABAP program "RSORAT4M" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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 that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "AKT_DAY_HIST2" "(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:
When importing the object "HIST2", the component no. 8 in the
dataset has a different type from the corresponding component
of the target object in the program "RSORAT4M".
The data type is "I" in the dataset, but "P" in the program.
How to correct the error
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 "RSORAT4M" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "RSORAT4M". Then activate the function 'Generate'.
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:
"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"
"RSORAT4M" or "RSORAT4M"
"AKT_DAY_HIST2"
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
"AKT_DAY_HIST2" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "UBSDEV"
Network address...... "10.22.6.68"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4v"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "UBSDEV"
Database type..... "ORACLE"
Database name..... "UBD"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 1117168
EM...... 0
Heap.... 0
Page.... 93315072
MM Used. 638120
MM Free. 458608
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "RSORAT4M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAT4M" - in "AKT_DAY_HIST2".
The main program was "RSORAT4M ".
In the source code you have the termination point in line 163
of the (Include) program "RSORAT4M".
The program "RSORAT4M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 06004902
The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in
procedure "AKT_DAY_HIST2" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "RSORAT4M "; its source code begins in line
161 of the (Include program "RSORAT4M ".
Source Code Extract
Line
SourceCde
133
134
REFRESH HIST2_DAY.
135
CLEAR HIST2_DAY.
136
137
HIST2_DAY-SIZE = TD110-TSSI.
138
HIST2_DAY-FREE = TD110-TSFR.
139
HIST2_DAY-USED = 100 - TD110-TSFRP.
140
HIST2_DAY-TABLES = TD110-TANO.
141
HIST2_DAY-INDICES = TD110-TINO.
142
HIST2_DAY-TSIZE = TD110-TASI.
143
HIST2_DAY-ISIZE = TD110-TISI.
144
145
PERFORM new_analysis_db.
146
HIST2_DAY-DATE = DATE.
147
HIST2_DAY-TIME = TIME.
148
APPEND HIST2_DAY.
149
ENDFORM.
150
Beschaffung neuer Analyse-Daten für Historien <<<
151
152
Historie, Tage >>>
153
FORM DELETE_AKT_DAY_HIST2.
154
DATA: FLAG VALUE ' '.
155
LOOP AT HIST2.
156
IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.
157
ENDLOOP.
158
IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.
159
ENDFORM.
160
161
FORM AKT_DAY_HIST2. " Aktualisiere Tage-Historie
162
PERFORM PREPARE_MONIKEY USING 36. " Lese Historie
>>>>>
IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
164
IF SY-SUBRC <> 0.
165
REFRESH HIST2. CLEAR HIST2.
166
PERFORM LOGBUCH_INIT USING 1.
167
PERFORM TRANSFORM_ALL_HISTORIES. " Strukturaenderung fuer Dynami
168
PERFORM PREPARE_MONIKEY USING 36. " Lese Historie
169
IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
170
ENDIF.
171
READ TABLE HIST2 INDEX 1.
172
IF SY-SUBRC <> 0.
173
REFRESH HIST2. CLEAR HIST2.
174
PERFORM LOGBUCH_INIT USING 1.
175
ENDIF.
176
PERFORM DELETE_AKT_DAY_HIST2. " Delete aktuellen Tag
177
LOOP AT HIST2_DAY. " Füge neue Analyse an
178
MOVE-CORRESPONDING HIST2_DAY TO HIST2.
179
APPEND HIST2.
180
ENDLOOP.
181
ADD 1 TO LOGBUCH-ANZDAYS.
182
MOVE DATE TO LOGBUCH-LASTDAY.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071224
SY-UZEIT
070256
SY-XPROG
SAPMSSY0
SY-XFORM
NEW-LINE
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAT4M RSORAT4M 163
AKT_DAY_HIST2
1 EVENT RSORAT4M RSORAT4M 73
END-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name AKT_DAY_HIST2
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
MONIKEY
--UBD days h/2
0000000000000000000000
0000000000000000000000
2254422222667722226232
DD52400000419300008F20
MONI
DB--UBD days h/2 ## ##################################################################
00000000000000000000000000000F0083300C019880423CCCCBA185073210552E8C0334266086A470B60061642777
00000000000000000000000000000F1204000802DCF80B619C242588C81881810C0A70020645DC07BF1AFE070ECE1C
4422544222226677222262320022800003300001090100EE1161721CA580CAFEA65BC607333BC23214789666B6D8BC
42DD52400000419300008F20000076120120000F291C430000062325261E520B6388C203600303CA0830014245D093
MONI-CLUSTR
8912646
08
07
OBJ3
0000000000000000000000000000000
0000000000000000000000000000000
2222222222222222222222222222222
0000000000000000000000000000000
OBJ4[]
Table[initial]
HIST2[]
Table[initial]
SY-SUBRC
0
0000
0000
HIST2
00000000000000######################
000000000000000000000000000000000000
000000000000000000000000000000000000
333333333333330000000000000000000000
00000000000000000C000C000000000C000C
S2
0
0
2
0
KBYTES
0.0.0.0.0.0.0.1.
00000000
0000000C
No. 1 Ty. EVENT
Name END-OF-SELECTION
TSN
000000000000000
000000000000000
222222222222222
000000000000000
TYP
00000000000000000
00000000000000000
22222222222222222
00000000000000000
S3
0
0
2
0
LOGBUCH-LASTDAY
20070315
00000000
00000000
33333333
20070315
DATE
20071224
00000000
00000000
33333333
20071224
SY-REPID
RSORAT4M
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545453422222222222222222222222222222222
23F2144D00000000000000000000000000000000
S5
0
0
2
0
S7
0
0
2
0
ROOT
000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000
SEG_TYPE
00000000000000000
00000000000000000
22222222222222222
00000000000000000
S4
0
0
2
0
Internal notes
The termination was triggered in function "CheckSimpleComponent"
of the SAP kernel, in line 1183 of the module
"//bas/700_REL/src/krn/runt/abconne.c#16".
The internal operation just processed is "IMPO".
Internal mode was started at 20071224070256.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
DoStack2 ( 0x105c65dc0, 0xffffffff7fff9900, 0x1004ffecc, 0x0, 0x20, 0x10315f010 ), at 0x1004ff
CTrcStack2 ( 0x105c65dc0, 0x0, 0x18800, 0x1031a4d20, 0x100b21370, 0x10315f010 ), at 0x1004ffa6
__1cQrabax_CStackSave6F_v_ ( 0x103385400, 0x3385400, 0x103a0e490, 0x1021a9af0, 0x100000000, 0x
ab_rabax ( 0x100000000, 0x31a4c00, 0x103a0d000, 0x3a0d000, 0x2000, 0x0 ), at 0x100b21370
__1cUCheckSimpleComponent6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kCkL6kpknHAB_DATA_kI9D9D_i_ ( 0xf
__1cRConneCmpCheckList6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kppnMImportOpHead_kLpknHAB_DATA_kpk9
__1cNConneCmpCheck6FkpnICONNE_RD_pknHAB_DATA_kpnQDESCRIPTION_CNTL_ppnMImportOpHead_kLkpLII_i_
__1cMimport_check6FpnICONNE_RD_ppnMImportOpHead_kpCC_i_ ( 0xffffffff7fffa9a8, 0xffffffff7fffbb
__1cLab_connread6FIpnLIMPORT_INFO_kpkHpnHAB_DATA_pFpHLp6ppv_ipFppCpLInJEXPO_MODE__i_i_ ( 0xfff
__1cLexpo_import6F_v_ ( 0x0, 0xfffffffe324a90a4, 0xfffffffe324a90ac, 0x105be9e84, 0x0, 0x105ce
__1cIab_jimpo6F_v_ ( 0x100000000, 0x5c66400, 0x1, 0x0, 0x0, 0x94 ), at 0x1009d7f64
__1cIab_extri6F_i_ ( 0x100000000, 0x5cea400, 0x230, 0x1, 0x0, 0x46 ), at 0x1006f9298
__1cJab_xevent6FpkH_i_ ( 0xfffffffe324a9fe8, 0xfffffffe324a7398, 0x2ac, 0x0, 0x4c, 0x105c6648
__1cIab_trigg6F_i_ ( 0x105bea340, 0x105c69588, 0x10093cc48, 0x20, 0x215fc00, 0x0 ), at 0x1009
ab_run ( 0x1062f8288, 0x105c69000, 0x1021b23fc, 0x0, 0x105c6647c, 0x0 ), at 0x100b9346c
dynpmcal ( 0x106305708, 0x6, 0xc, 0x1035867c8, 0x100589628, 0x1031a4d14 ), at 0x100581e1c
dynppai0 ( 0x106305708, 0x106306d14, 0x0, 0x1031a4d78, 0x0, 0x105c86004 ), at 0x10057f120
dynprctl ( 0x106305708, 0x0, 0x103199024, 0x1300, 0x1, 0x128c ), at 0x10057d764
dynpen00 ( 0x0, 0x106305708, 0x106305708, 0x0, 0x106305708, 0x102a5fc00 ), at 0x100579c64
TskhLoop ( 0x0, 0xb, 0xffffffff6f408530, 0x0, 0x100288854, 0x0 ), at 0x10028f248
ThStart ( 0x1, 0x280800, 0x100280800, 0x100000000, 0x1, 0x10319a0c0 ), at 0x1002815f4
DpMain ( 0x37e6800, 0x3197400, 0x100000000, 0x1, 0x0, 0x0 ), at 0x1001b2e8c
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAT4M
0
21.03.2007
19:50:50
98304
E
1
Prg
SAPMSSY0
1
21.03.2007
19:51:33
90112
E
2
Prg
SAPMSSYD
1
21.03.2007
19:51:17
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
11264
E
4
Prg
RSDBRUNT
0
21.03.2007
19:50:43
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
21.03.2007
19:28:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
12
Prg
SAPLSABE
12
09.09.2004
14:18:36
13312
E
13
Prg
SAPLSECU
13
27.03.2007
17:41:57
87040
E
14
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
15
Prg
SAPLSTUP
15
08.03.2005
19:04:31
74752
E
16
Prg
SAPLCNDP
16
21.03.2007
16:17:37
193536
E
17
Prg
SAPLSCNT
17
18.02.2005
14:16:06
30720
E
18
Prg
SAPSHDTV
17
05.01.2005
16:26:16
36864
E
19
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
20
Prg
SAPLOLEA
20
05.07.2005
13:10:18
96256
E
21
Prg
SAPLSGUI
21
21.03.2007
19:51:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
SAPLSFES
24
27.03.2007
17:42:13
257024
E
25
Prg
SAPLTHFB
25
27.03.2007
17:38:01
392192
E
26
Typ
WPINFO
0
26.02.1999
14:49:01
6144
27
Prg
SAPLURFC
27
15.06.2005
11:39:01
22528
E
28
Prg
SAPLSPLUGIN
28
09.09.2004
14:18:36
8192
E
29
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
30
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
31
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
32
Typ
MONI
0
31.03.2004
16:41:21
5120
33
Prg
CX_SY_IMPORT_MISMATCH_ERROR===CP
33
05.07.2005
13:10:16
10240
E
34
Typ
SCX_SRCPOS
0
18.05.2004
14:07:11
2048
35
Prg
CX_DYNAMIC_CHECK==============CP
35
05.07.2005
13:10:16
10240
E
36
Prg
CX_ROOT=======================CP
36
05.07.2005
13:10:16
11264
E
37
Prg
CX_NO_CHECK===================CP
37
05.07.2005
13:10:16
10240
E
38
Prg
CX_SY_NO_HANDLER==============CP
38
05.07.2005
13:10:16
10240
E
39
Typ
SYST
0
09.09.2004
14:18:12
31744
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAT4M
SYST 09.09.2004 14:18:12 00004612
00000x00010000000000000000000
MONI . . : : 00002944
DB--UBD days h/2 00 x0087######00#0####
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
1841
BRAX
01
FFF2
RSORAT4M
157
1842
comp
00
0242
C000
00A2
RSORAT4M
158
1844
BRAF
05
0005
RSORAT4M
158
1845
ccqi
4C
0000
0000
2610
0001
0000
0000
2610
RSORAT4M
158
1849
ENDF
00
0000
RSORAT4M
159
1850
00
0000
RSORAT4M
159
1851
PERP
00
0000
RSORAT4M
161
1852
perf
00
000C
RSORAT4M
162
1853
PERP
80
0001
RSORAT4M
162
1854
PERP
80
00CC
RSORAT4M
162
1855
IMPO
00
0001
007B
007A
010C
0000
00EA
0000
RSORAT4M
163
1859
PAR2
06
0000
00EB
009B
RSORAT4M
163
>>>>>
IMPO
07
0000
0000
0000
0000
0000
0000
0000
RSORAT4M
163
1865
cmpr
00
00CA
00F8
0000
RSORAT4M
164
1867
BRAF
05
0016
RSORAT4M
164
1868
REFR
00
0000
009B
0000
RSORAT4M
165
1870
CLEA
00
009C
RSORAT4M
165
1871
perf
00
0035
RSORAT4M
166
1872
PERP
80
0001
RSORAT4M
166
1873
PERP
80
0006
RSORAT4M
166Hi,
Please apply the following correction manually.
1. Go to transaction ST03N
2. Change user from 'Administrator' to 'Expert Mode'.
3. Go to Collector and performance analysis -> Performance database
-> Monitoring database -> Contents
4. Search where further info contains the string "h/2"
like the following monikeys:
- 'days h/2'
- 'weeks h/2'
- 'months h/2'
5. Double click on each, so that they become red and show ** delete
6. Finally SAVE
This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.
How can I identify the monikey that has to be deleted?
When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:
"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".
To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or
'tabgrowth 2'...
You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.
997535 DB02: Problems with History Data.
Award points if helpful.
Thanks,
Tanuj -
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,
Ni3Solved 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
BhaskarHi,
check Note 657981 - CONNE_IMPORT_WRONG_COMP_TYPE in DB02 for RSORAUD1
also check Note 997535 - DB02: Problems with History Data.
regards
kaushal -
ABAP DUMP - CX_SY_IMPORT_MISMATCH_ERROR
Hello Everyone,
I got the abap dump with exception CX_SY_IMPORT_MISMATCH_ERROR.
In Error Analasys:
I got the message. When importing the object "15" , the component 3 in the dataset had the different length from the corresponding component of the target object in the program.
The length is 32 in the dataset, but 20 in the program.
In How to correct Error:
Try to find out why the length of the object is 32.
I tried to load the data from one SRM ODS to another SRM ODS. all the data load went fine. I was trying to logout then i got this abap dump. I dont know what was the issue. When i check in ST22 i saw this message which i mentioned above Error Analysis and How to correct Error.
Please help me out, Your inputs will be helpufl
Thanks,
Lasya.Hi,
Can you give solution to this problem.
Thank You,
SB. -
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....
ThanksHi,
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 -
Here is the short dump that I am getting while generating Z report transaction.
Can anyone please help me out to resolve the issue?
The current ABAP program "SAPLSTXD" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
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 "READ_TEXTLINES" "(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:
Missing RAISING Clause in Interface
Program SAPLSTXD
Include LSTXDFDB
Row 75
Module type (FORM)
Module Name READ_TEXTLINES
Trigger Location of Exception
Program SAPLSTXD
Include LSTXDFDB
Row 106
Module type (FORM)
Module Name READ_TEXTLINES
Source Code Extract
85 DATA: l_mod LIKE tcp0c-modifier.
86
87 refresh rt_lines.
88 move-corresponding rt_header to stxl_id.
89 * only for nonunicodesystems:
90 * the import-statment contains a conversion from internal cp
91 * to the codepage of language key.
92 * if the import-process can't assign a codepage it is using
93 * the actual systzem-codepage. So we make a SET LOCALE
94 l_unich = CL_ABAP_CHAR_UTILITIES=>charsize.
95 IF l_unich = 1.
96 GET LOCALE LANGUAGE l_sypr COUNTRY l_count MODIFIER l_mod.
97 CATCH SYSTEM-EXCEPTIONS localization_errors = 1.
98 SET LOCALE LANGUAGE rt_header-tdspras.
99 ENDCATCH.
100 IF sy-subrc 0.
101 SET LOCALE LANGUAGE l_sypr.
102 ENDIF.
103 ENDIF.
104
105 if rt_header-tdtexttype is initial. "SAPscript format
>>>>> import tline to rt_lines
107 from database stxl(tx)
108 client rt_client
109 id stxl_id
110 ACCEPTING TRUNCATION "important for Unicode->Nonunicode
111 IGNORING CONVERSION ERRORS.
112 else. "non-SAPscript text
113 import tline to rt_lines
Someone please help in finding the solution.
Regards,
VikasHi.,
The import parameter passing is mismatched from the dump error.,
check the tline has structure same as rt_lines and same fields are passing and get populating.,
Thanks & Regards,
Kiran -
Short Dump while checking DataSource contents in R3 (Transaction RSA3)
Hello all,
I am having trouble with a DataSource (2LIS_11_VAITM) in the R3 Source System (IDES 6.0). When I try to view the contents of this DataSource through Transaction RSA3, I get the following Short Dump Error.....
Could someone pls help me with this.
Thanks,
SD
============================================================================
Runtime Errors CONNE_IMPORT_WRONG_STRUCTURE
Except. CX_SY_IMPORT_MISMATCH_ERROR
Date and Time 18.03.2009 09:56:23
Short text
Error when importing object "MC11VA0ITM_TAB".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLMCEX" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
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 attempting to import data, the
structure of the complex object "MC11VA0ITM_TAB" was not compatible with the
target object. The error occurred with component no. 31.
Missing RAISING Clause in Interface
Program SAPLMCEX
Include LMCEXU06
Row 1
Module type (FUNCTION)
Module Name MCEX_BW_LO_API
Trigger Location of Exception
Program SAPLMCEX
Include LMCEXU06
Row 263
Module type (FUNCTION)
Module Name MCEX_BW_LO_APIHi SD,
The 11_Vaitm is a LO datasource, before checking its data setup tables need to be filled for it.
For filling the setup tables, first you have to delete the existing setup table data and ensure all the delta queues are empty.
Delete the setup tables: Go to TCODE LBWG and in the application give 11 and execute.
Delete all entries in Delta Queue, TCODE RSA7 for application 11.
Delete the entries in logistic queue: Check in TCODE SMQ1, if there are any entries for application .
Refill the setup tables: SBIW -> Settings for application specific datasources -> Logistics -> anaging extract strucutre -> Initilization -> Filling the setup table ->Application specific setup of data -> SD-Sales order perform setup.
Then try RSA3. Hope it helps.
Regards,
Pankaj -
Facing short dumps when trying to open session in CSA
Hi
All am facing Short dump when i am trying to open session in CSA
Error detials:
go to System Administration workcenter task management up CSA. Choose the Solution
got short dump:
Short text
Length error occurred in IMPORT statement.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
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 "LOAD" "(METHOD)", 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:
During import the system discovered that the target object has
a different length than the object to be imported.
Missing RAISING Clause in Interface
Program SAPLDSVAS_PROC
Include LDSVAS_PROCTAI
Row 1.431
Module type (METHOD)
Module Name LOAD
Trigger Location of Exception
Program SAPLDSVAS_PROC
Include LDSVAS_PROCTAI
Row 1.514
Module type (METHOD)
Module Name LOAD
Please help me to solve this problem
Regards,
NeniHello Neni
According to the information I saw in that post it could be caused by a sort of inconsistency of the program code vs a structure.
Wether that is a bug that is in your SAP Solution Manager release or something that is caused by administrative actions (perhaps solving SPAU entries after SP stack update or upgrade) I cannot tell.
I would recommend you either try and find a relative SAP note (narrowing down result to only your SAP Solution Manager system) and searching using the dump keywords. If you cannot find anything I would recommend you to open a customer message so SAP can take a look at the specific error.
If you give more information, perhaps someone on the forum can help you out abit better, which SAP Solution Manager version and so on.
You also didn't answer my question, any recent changes you are aware of ?
Kind regards
Tom -
Function module going for DUMP
Hi ALL,
I have import request and i got sucess .My 3 function modules are import to client system.2 FM are working properly but 1 function module is going for DUMP.
When iam Executing this FM through SE37 F8 its running but iam not able to display or change this ZFM.
In our DEV sytem it is working properly.but Client system it is going for DUMP.
I have gone dump analysis its saying
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
MO_IMPORT_MODIFICATIONS" "(METHOD
Length error occurred during the IMPORT statement
*The system found when importing that the target object was longer or
shorter than the object to be imported*
Thanks in Advance,
Madhu.
Edited by: madhubabu rao on Apr 23, 2009 10:34 AM
Edited by: madhubabu rao on Apr 23, 2009 10:36 AMHi sekhar,
I did not transport individually.I have transport 3 FM in a function group and it is assigned to a Package.
First i have 2 FM in my function group after that i have copied one more FM from another Function group.
in SE80 right click -->copy it asked me function group name only .not transport number.
After copy the FM i have transport total package.2 FM are working properly .The FM which i have copied it is not able to display or edit.
Madhu
Maybe you are looking for
-
Is there a driver so that a Belkin Thunderbolt port can work on Bootcamp - Windows 7?
I purchased a Belkin thunderbolt dock/hub at the apple store. It works well on my Yosemite OS X 10.10 2012 MBP 15", but not so well on Bootcamp running W7. The display via an TB to HDMI adaptor in the dock works, and the sound in and out works (some
-
Adobe LiveCycle Designer and Office 2010
Hi guys, I'm using Adobe LiveCycle Designer (version 9 / ES2). I try to open a MS Word file, but I receive an error message. Word (version XP or higher) cannot be found on the machine. OS: Windows 7 Enterprise Office: 2010 I read that the version 8.2
-
Helppppp meeeee pleaseeeeee
-
HT5534 Issues w/ Microsoft word! how do I reset and relaunch?
How do I reset and reload microsoft word on my Macbook Pro? Secondly, the adobe flash player stopped to function with message indicating "couldn't load plug-in". Any assistance?
-
I spent last week syncing 50GB of data in my cc folder and two computers. Now the cc app has updated and the folder has disappeared from my computer.Where have they gone?