SWPM: Program ‘Migration Monitor’ exits with error code 103

We are doing an installation of SAP ERP 6.0 Support Release 3 with Windows Server 2008 R2 and Microsoft SQL Server 2008 R2. During the IMPORT ABAP phase, the installation is stuck due to the following error,

An error occurred while processing option SAP Business Suite 2005 > SAP ERP 6.0 Support Release 3 > SAP Application Server ABAP > MS SQL Server > Central System > Central System

( 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.).

You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and be able to continue later.
Log files are written to C:\Program Files/sapinst_instdir/BS2005/ERP60SR3/AS-ABAP/MSS/CENTRAL/

Solution

From the logs, it says that we need to check on – import_monitor.java.log and import_monitor.log files. These 2 files are located in installation log directory (also been mentioned from the screenshot)

So, here’s the details – Looks like there are 8 files are failing to be imported.

import_monitor.java

java version "1.6.0_71"
Java(TM) SE Runtime Environment (build 6.1.062)
SAP Java Server VM (build 6.1.062 24.51-b11, Feb  7 2014 00:35:25
- 61_REL - optU - windows amd64 - 6 - bas2:210946 (mixed mode))
Import Monitor jobs: running 1, waiting 8, completed 19, failed 0, total 28.
Import Monitor jobs: running 2, waiting 7, completed 19, failed 0, total 28.
Import Monitor jobs: running 3, waiting 6, completed 19, failed 0, total 28.
Import Monitor jobs: running 4, waiting 5, completed 19, failed 0, total 28.
Import Monitor jobs: running 5, waiting 4, completed 19, failed 0, total 28.
Import Monitor jobs: running 6, waiting 3, completed 19, failed 0, total 28.
Import Monitor jobs: running 7, waiting 2, completed 19, failed 0, total 28.
Import Monitor jobs: running 8, waiting 1, completed 19, failed 0, total 28.
Loading of 'DD03L' import package: ERROR
Import Monitor jobs: running 7, waiting 1, completed 19, failed 1, total 28.
Loading of 'SEOCOMPODF' import package: ERROR
Import Monitor jobs: running 6, waiting 1, completed 19, failed 2, total 28.
Loading of 'SCPRSVALS' import package: ERROR
Import Monitor jobs: running 5, waiting 1, completed 19, failed 3, total 28.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 4, waiting 1, completed 19, failed 4, total 28.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 3, waiting 1, completed 19, failed 5, total 28.
Loading of 'TODIR' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 19, failed 6, total 28.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 19, failed 7, total 28.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 19, failed 8, total 28.

import_monitor

INFO: 2014-08-20 11:29:12 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 1, completed 19, failed 8, total 28  error
processing of package SAPAPPL2

ERROR: 2014-08-20 11:29:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is interrupted with R3load error.
Process 'C:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage
4103 -l SAPAPPL2.log -loadprocedure fast' exited with return code 2.

For mode details see 'SAPAPPL2.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: 2014-08-20 11:29:39
Cannot start import of packages with views because not all import packages with
tables are loaded successfully.

WARNING: 2014-08-20 11:29:39
8 error(s) during processing of packages.

INFO: 2014-08-20 11:29:39
Import Monitor is stopped.

To find what are the causes of the failure, you may need to look up the 8 files accordingly. Example here, for SCPRSVALS file. From the log, it shows that the SCPRSVALS file might not be cleanly installed or possibly corrupted. So, what’s are the next action?

(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\BS2005\ERP60SR3\AS-ABAP\MSS
\CENTRAL\SCPRSVALS.TSK.bck already seems to exist a previous run may not have
been finished cleanly file C:\Program Files\sapinst_instdir\BS2005\ERP60SR3
\AS-ABAP\MSS\CENTRAL\SCPRSVALS.TSK possibly corrupted

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

Now, stop the installation and log off from your session. Login back using SID-adm user. Open the command prompt and execute the following command.

R3load -merge_only "PATH-TO-THE-TSK-FILE\SCPRSVALS.TSK"

Output from the above command,

sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3load: START OF LOG: 20140820120755

R3load: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
R3load: version R7.20/V1.6 [UNICODE]
Compiled Dec  4 2013 16:10:48
patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for
the table (note 1914260)
process id 3860
R3load -merge_only C:\Program Files\sapinst_instdir\BS2005\ERP60SR3\AS-ABAP\MSS\
CENTRAL\SCPRSVALS.TSK

(TSK) WARNING: user requested automatic merge of C:\Program Files\sapinst_instdi
r\BS2005\ERP60SR3\AS-ABAP\MSS\CENTRAL\SCPRSVALS =.TSK and C:\Program Files\sapins
t_instdir\BS2005\ERP60SR3\AS-ABAP\MSS\CENTRAL\SCPRSVALS.TSK.bck

         This may indicate that there is already a job processing
         the same task file
         Merging the task and .bck files can be dangerous if somebody
         fiddled with the files or file system errors occurred

R3load: job completed
R3load: END OF LOG: 20140820120755

You will also need to execute the same thing to the other failure files. Once done, run the SWPM again with the old option. The IMPORT ABAP phase will continue successfully with no error!