Import ABAP - Error during the ERP installation

[Former Member]

Hello,

I´m doing an installation of a SAP ERP 6.0 EHP7 in Windows Server 2012 (x64) and MS SQL Server 2012. Now I´m facing with an error during the installation in phase "Import ABAP". I checked some log files:

-> sapinst.log:
...

INFO 2013-11-04 11:01:36.963
Working directory changed to C:/Program Files/sapinst_instdir/BS2013/BS2013/ERP607/MSS/INSTALL/BS2013/ERP607/MSS/STD/ABAP.

INFO 2013-11-04 11:01:37.322
Switched to user: WINTESTSAP\jmdadm.

INFO 2013-11-04 11:01:37.541
Creating file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\import_monitor.java.log.

INFO 2013-11-04 11:01:37.557
Switched to user: WINTESTSAP\jmdadm.

INFO 2013-11-04 11:01:37.588
Output of C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.2912.1383560638\jre\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.

WARNING 2013-11-04 11:02:08.495
Execution of the command "C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.2912.1383560638\jre\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 6.1.051)
SAP Java Server VM (build 6.1.051 23.5-b05, May 30 2013 00:49:05 - 61_REL - optU - windows amd64 - 6 - bas2:197575 (mixed mode))
Import Monitor jobs: running 1, waiting 3, completed 26, failed 0, total 30.
Import Monitor jobs: running 2, waiting 2, completed 26, failed 0, total 30.
Import Monitor jobs: running 3, waiting 1, completed 26, failed 0, total 30.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 26, failed 1, total 30.
Loading of 'SEOCOMPODF' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 26, failed 2, total 30.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 3, total 30.

ERROR 2013-11-04 11:02:08.511
CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2013-11-04 11:02:08.620
FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).

-> import_monitor.java.log:

...

java version "1.6.0_45"

Java(TM) SE Runtime Environment (build 6.1.051)

SAP Java Server VM (build 6.1.051 23.5-b05, May 30 2013 00:49:05 - 61_REL - optU - windows amd64 - 6 - bas2:197575 (mixed mode))

Import Monitor jobs: running 1, waiting 3, completed 26, failed 0, total 30.

Import Monitor jobs: running 2, waiting 2, completed 26, failed 0, total 30.

Import Monitor jobs: running 3, waiting 1, completed 26, failed 0, total 30.

Loading of 'SAPSSEXC' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 26, failed 1, total 30.

Loading of 'SEOCOMPODF' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 26, failed 2, total 30.

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 26, failed 3, total 30.

-> import_monitor.log:

...

INFO: 2013-11-04 11:01:37
Import Monitor is started.

CONFIG: 2013-11-04 11:01:37
Application options:
collectLogicalPackages=false
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=C:\SAP\51046679_1\DATA_UNITS\EXPORT_1;C:\SAP\51046679_1\DATA_UNITS\EXPORT_2;C:\SAP\51046679_1\DATA_UNITS\EXPORT_3;C:\SAP\51046679_1\DATA_UNITS\EXPORT_4;C:\SAP\51046679_1\DATA_UNITS\EXPORT_5;C:\SAP\51046679_1\DATA_UNITS\EXPORT_6;C:\SAP\51046679_2\DATA_UNITS\EXPORT_7;C:\SAP\51046679_2\DATA_UNITS\EXPORT_8;C:\SAP\51046679_2\DATA_UNITS\EXPORT_9;C:\SAP\51046679_2\DATA_UNITS\EXPORT_10;C:\SAP\51046679_2\DATA_UNITS\EXPORT_11
installDir=C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP
jobNum=3
loadArgs=-loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes

CONFIG: 2013-11-04 11:01:37
List of packages with table structure: 'SAP0000'.

CONFIG: 2013-11-04 11:01:37
List of packages with views: 'SAPVIEW'.

TRACE: 2013-11-04 11:01:37 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\DDLMSS.TPL' template file is started.

INFO: 2013-11-04 11:01:37 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.

INFO: 2013-11-04 11:01:38
Data codepage 1100 is determined using TOC file 'C:\SAP\51046679_1\DATA_UNITS\EXPORT_1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.

INFO: 2013-11-04 11:01:39
Version table 'SVERS' is found in STR file 'C:\SAP\51046679_2\DATA_UNITS\EXPORT_10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.

INFO: 2013-11-04 11:01:39
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\SAP\51046679_2\DATA_UNITS\EXPORT_10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.

INFO: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 3, completed 26, failed 0, total 30  Package Group  max threads: 3 current running threads : 0 processing package: SAPSSEXC

INFO: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 2, waiting 2, completed 26, failed 0, total 30  Package Group  max threads: 3 current running threads : 1 processing package: SAPAPPL0

TRACE: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.

INFO: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 3, waiting 1, completed 26, failed 0, total 30  Package Group  max threads: 3 current running threads : 2 processing package: SEOCOMPODF

TRACE: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' starting import package into database:
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast

TRACE: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.

TRACE: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' starting import package into database:
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast

TRACE: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SEOCOMPODF' import package is started.

INFO: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask processPackage
Task file 'C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SEOCOMPODF.TSK' from package 'SEOCOMPODF' contains no tasks with data type (D).

TRACE: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SEOCOMPODF' starting import package into database:
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SEOCOMPODF.cmd -dbcodepage 4103 -l SEOCOMPODF.log -loadprocedure fast

INFO: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 2, waiting 1, completed 26, failed 1, total 30  error processing of package SAPSSEXC

ERROR: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

INFO: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 1, waiting 1, completed 26, failed 2, total 30  error processing of package SEOCOMPODF

ERROR: 2013-11-04 11:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SEOCOMPODF' import package is interrupted with R3load error.
Process 'C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SEOCOMPODF.cmd -dbcodepage 4103 -l SEOCOMPODF.log -loadprocedure fast' exited with return code 2.
For mode details see 'SEOCOMPODF.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

INFO: 2013-11-04 11:01:40 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 1, completed 26, failed 3, total 30  error processing of package SAPAPPL0

ERROR: 2013-11-04 11:01:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

WARNING: 2013-11-04 11:02:07
Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2013-11-04 11:02:07
3 error(s) during processing of packages.

INFO: 2013-11-04 11:02:07
Import Monitor is stopped.

Can you help me please? How can I correct this error?!

Thank you
samid

[ashish_vikas · Accepted solution]

please check and upload below log files :

SAPSSEXC.log

SEOCOMPODF.log

SAPAPPL0.log

best regards

ashish

[Former Member · Accepted solution]

Hello ashish,

I checked that three log files.

-> SAPAPPL0.log:

...

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20131104110139

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#2 $ SAP
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.40/V1.7 [UNICODE]
Compiled Apr 10 2013 20:50:23
patchinfo (patches.h): (0.011) R3ta: incorrect split ranges to tables with RAW fields (note 1816978)
process id 1276
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast

(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SAPAPPL0.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SAPAPPL0.TSK possibly corrupted

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20131104110140

- SAPSSEXC.log:

...

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20131104110139

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#2 $ SAP
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.40/V1.7 [UNICODE]
Compiled Apr 10 2013 20:50:23
patchinfo (patches.h): (0.011) R3ta: incorrect split ranges to tables with RAW fields (note 1816978)
process id 2300
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast

(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SAPSSEXC.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SAPSSEXC.TSK possibly corrupted

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20131104110139

-> SEOCOMPODF.log:
...

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20131104110139

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#2 $ SAP
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.40/V1.7 [UNICODE]
Compiled Apr 10 2013 20:50:23
patchinfo (patches.h): (0.011) R3ta: incorrect split ranges to tables with RAW fields (note 1816978)
process id 2412
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe -i SEOCOMPODF.cmd -dbcodepage 4103 -l SEOCOMPODF.log -loadprocedure fast

(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SEOCOMPODF.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\BS2013\BS2013\ERP607\MSS\INSTALL\BS2013\ERP607\MSS\STD\ABAP\SEOCOMPODF.TSK possibly corrupted

C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\JMD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20131104110139

I don´t understand what´s the problema here...!

Can you help me please?

Thank you,

samid

[Sriram2009 · Accepted solution]

Hi Samid

Kindly refer the SAP note

R3load aborts with return code -1.073.741.819

455195  - R3load: Use of TSK files

Regards

Sriram

[joo_migueldimas · Accepted solution]

Hello,

I had a similar problem... what I did to solve the problem was start again the installation from the scratch! So, my recommendation is that, If you don´t have any problem with time or something else, I recommend starting the installation from the scratch!

Kind regards,

João Dimas

[Former Member · Accepted solution]

Hello,

Ok... I will try that João Dimas... I will give you feedback later.

Thanks,

samid raif

[Former Member · Accepted solution]

Hello,

That´s solved my problem 🙂

I started the SAP installation from the scratch and this error in that phase no longer appeared anymore! 🙂

Tks,

samid raif

[former_member192421 · Accepted solution]

Hi,

Then, SAP should fix this problem...It's very annoying..

Regards,

Rajkumar

[former_member701192]

For me the solution was to edit the <OJECT>.TSK file.

Before editing:

T OBJECT C ok

D OBJECT I err

M OBJECT C xeq

P OBJECT~0 C xeq

I OBJECT~TYP C xeq

U OBJECT C xeq

Then edited err to ok:

T OBJECT C ok

D OBJECT I ok

M OBJECT C xeq

P OBJECT~0 C xeq

I OBJECT~TYP C xeq

U OBJECT C xeq

Save the file, and rerun the installer from the failed step. This solved my issue.

[Former Member]

Hi All,

Just contributing from my side. I faced the same issue and non of the above solutions helped me. You can check the Objectname.cmd file in the installation directory( for example SAPSSEXC.cmd in my case).

This would show you the list of files from the installation directory where the objects are being fetched. Once you find the installation files you just need to download those installation files again and start the fresh installation from the beginning. Mostly it will be Installation export I and II.

The outline is, these files may be corrupt

Regards,

Prithivi Raj

[Former Member]

Hi,

Login as <sid>adm and execute

R3load -merge_only SAPAPPL2.TSK

Then try again.

BR,

Prabhakar

[former_member192421]

Hi Samid,

There is a similar thread, please refer to this thread once. It may resolve your problem.

http://scn.sap.com/thread/1764236

Regards,

Rajkumar