cancel
Showing results for 
Search instead for 
Did you mean: 

Program 'Migration Monitor' exits with error code 103.

marcin_czarny_nype
Participant
0 Kudos

Hi,

I try to install a SAP ECC 6.0 with SQL Server and I have issue during Import ABAP:


Please help me to solve this problem and tell which logs files I need to add to get help.

Windows Server 2008 R2 x64

SQL Server 2005 Enterprise Edition

Best regards,

Marcin


ERROR 2015-01-25 02:56:58.548

FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|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.).

ERROR 2015-01-25 02:56:58.543

CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

WARNING 2015-01-25 02:56:58.541

Execution of the command "C:\j2sdk1.4.2_42-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:

java version "1.4.2_42"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_42-b03)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_42-b03, mixed mode)

Import Monitor jobs: running 1, waiting 8, completed 103, failed 0, total 112.

Import Monitor jobs: running 2, waiting 7, completed 103, failed 0, total 112.

Import Monitor jobs: running 3, waiting 6, completed 103, failed 0, total 112.

Loading of 'COEJ' import package: ERROR

Import Monitor jobs: running 2, waiting 6, completed 103, failed 1, total 112.

Loading of 'SAPSLOAD' import package: ERROR

Import Monitor jobs: running 1, waiting 6, completed 103, failed 2, total 112.

Import Monitor jobs: running 2, waiting 5, completed 103, failed 2, total 112.

Import Monitor jobs: running 3, waiting 4, completed 103, failed 2, total 112.

Loading of 'SAPUSER1' import package: OK

Import Monitor jobs: running 2, waiting 4, completed 104, failed 2, total 112.

Loading of 'SAPDDIM' import package: OK

Import Monitor jobs: running 1, waiting 4, completed 105, failed 2, total 112.

Import Monitor jobs: running 2, waiting 3, completed 105, failed 2, total 112.

Import Monitor jobs: running 3, waiting 2, completed 105, failed 2, total 112.

Loading of 'SAPDODS' import package: OK

Import Monitor jobs: running 2, waiting 2, completed 106, failed 2, total 112.

Loading of 'SAPDFACT' import package: OK

Import Monitor jobs: running 1, waiting 2, completed 107, failed 2, total 112.

Loading of 'SAPUSER' import package: OK

Import Monitor jobs: running 0, waiting 2, completed 108, failed 2, total 112.

Import Monitor jobs: running 1, waiting 1, completed 108, failed 2, total 112.

Loading of 'SAP0000' import package: OK

Import Monitor jobs: running 0, waiting 1, completed 109, failed 2, total 112.

ERROR 2015-01-25 02:56:58.543

CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2015-01-25 02:56:58.548

FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|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.).




Accepted Solutions (0)

Answers (3)

Answers (3)

Reagan
Advisor
Advisor
0 Kudos

There are two failed packages based on the logs you have supplied. COEJ and SAPSLOAD. The COEJ log says


(TSK) ERROR: file C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\COEJ.TSK.bck already seems to exist

             a previous run may not have been finished cleanly

             file C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\COEJ.TSK possibly corrupted

There is COEJ.TSK.bck present and it should be merged with the COEJ.TSK file. The solution to merge the TSK files is provided in the SAP KBA 1970577 - (TSK) ERROR /<sapinst_instdir>/<SAPTABART>.TSK.bck already seems to exist

As this is a Windows based installation you need to run this

R3load.exe -merge_only COEJ.TSK

If the error is same for the SAPSLOAD package then you need to do the same.

R3load.exe -merge_only SAPSLOAD.TSK

Good Luck

RB

former_member182034
Active Contributor
0 Kudos

hi Marcin,

Please share this log COEJ.

Regards,

Sriram2009
Active Contributor
0 Kudos

Hi Marcin

Could you paste or attach import_monitor.java.log and What is the kernel and DBSL release  ?

BR

SS

marcin_czarny_nype
Participant
0 Kudos

NW 7.0 SR3 UC-Kernel 7.00 Windows Server on x64 64bit.


I attach logs files.


https://dl.dropboxusercontent.com/u/54036986/logs.zip


Regards,

Marcin



Sriram2009
Active Contributor
0 Kudos

Hi Marcin

1. What is the kernel release? I think you may require to use the kernel and DBSL 700 release 300 and above

2. From the log file name COEJ  Error message "

(TSK) ERROR: file C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\COEJ.TSK.bck already seems to exist

             a previous run may not have been finished cleanly

             file C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\COEJ.TSK possibly corrupted"

Refer the SAP KBA

1970577 - (TSK) ERROR /<sapinst_instdir>/<SAPTABART>.TSK.bck already seems to exist

BR