CJS-30022 Program 'Migration Monitor' and FCO-00011 The step runMigration

[joo_migueldimas]

Dear friends,

I am trying to install SAP Solution Manager with MS SQL 2005 Server but at Phase 16 of 44 "Import ABAP" I am getting the below error message. I really appreciate your help in solving this problem. Thanks in advance.

There they are the SAPINST.LOG with error and next, follow this, the two log file with details import_monitor.java.log , import_monitor.log

SAPINST.LOG :

u2026.

INFO 2008-10-06 11:49:28.052

Output of C:\j2sdk1.4.2_17-x64\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 2008-10-06 11:49:58.474

Execution of the command "C:\j2sdk1.4.2_17-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_17"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)

Import Monitor jobs: running 1, waiting 3, completed 25, failed 0, total 29.

Import Monitor jobs: running 2, waiting 2, completed 25, failed 0, total 29.

Import Monitor jobs: running 3, waiting 1, completed 25, failed 0, total 29.

Loading of 'REPOSRC' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 25, failed 1, total 29.

Loading of 'SAPSSEXC' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 25, failed 2, total 29.

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 25, failed 3, total 29.

ERROR 2008-10-06 11:49:58.474

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

ERROR 2008-10-06 11:49:58.490

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

IMPORT_MONITOR.JAVA.LOG :

java version "1.4.2_17"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)

Import Monitor jobs: running 1, waiting 3, completed 25, failed 0, total 29.

Import Monitor jobs: running 2, waiting 2, completed 25, failed 0, total 29.

Import Monitor jobs: running 3, waiting 1, completed 25, failed 0, total 29.

Loading of 'REPOSRC' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 25, failed 1, total 29.

Loading of 'SAPSSEXC' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 25, failed 2, total 29.

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 25, failed 3, total 29.

IMPORT_MONITOR.LOG :

u2026

ERROR: 2008-10-06 11:49:29 com.sap.inst.migmon.LoadTask run

Loading of 'REPOSRC' import package is interrupted with R3load error.

Process 'F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -loadprocedure fast' exited with return code 2.

For mode details see 'REPOSRC.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

ERROR: 2008-10-06 11:49:29 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Process 'F:\usr\sap\SSM\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

ERROR: 2008-10-06 11:49:32 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL0' import package is interrupted with R3load error.

Process 'F:\usr\sap\SSM\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: 2008-10-06 11:49:58

Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2008-10-06 11:49:58

3 error(s) during processing of packages.

INFO: 2008-10-06 11:49:58

Import Monitor is stopped.

--> This next 3 log files correspond to those 3 Erroru00B4s details which appear in above IMPORT_MONITOR.LOG , all that 3 logs have the same content / error detail which is:

REPOSRC.log = SAPSSEXC.log = SAPAPPL0.log :

(DB) INFO: connected to DB

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

a previous run may not have been finished cleanly

file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPSSEXC.TSK possibly corrupted

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20081006114900

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20081006114929

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jan 24 2008 01:41:44

F:\usr\sap\SSM\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\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPSSEXC.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPSSEXC.TSK possibly corrupted

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

F:\usr\sap\SSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20081006114929

Help me please... thanks

Best regards,

Joao Dimas

[joo_migueldimas]

Hi everyone...

It now passed two years after opening this message and in that momment after I solve this problem I didn´t put here the solution for the problem!

The solution was delete some files in sapinstdir as is said in note 455195 - R3load: Use of TSK files, it was in this directory that I deleted this next files:

- SAPAPPL0.TSK;

- SAPAPPL0.TSK.BCK;

- REPOSRC.TSK;

- REPOSRC.TSK.BCK;

- SAPSSEXC.TSK;

- SAPSSEXC.TSK.BCK

Look at this following image:

http://img714.imageshack.us/img714/3/deletefilessapinstdir.jpg

I hope this help!!

Best regards,

João Dimas

[Former Member]

hi,

can you look at this

[http://sap.ittoolbox.com/groups/technical-functional/sap-basis/cjs30022-program-migration-monitor-and-fco00011-the-step-runmigration-2392475]

Regards,

Muralidhar

[Former Member]

I will not prefer having errors in installations, since its once in a life time offer.

please work on the errors and restart a fresh installation and make sure you will not get it back.

Regards,

Pavan

[Former Member]

Guys,

Thanks for this response. I have the same problem installing Solution Manager 7 EHP1 on Win/Oracle 10g.

My question is how do you modify the R3load command to -merge according to the last paragraph of sapnote 455195?

"As of a certain patch level in Release 6.40, the R3load contains the option '-merge_only'. If you call the R3load with the option '-merge_only <TSK file>, only the TSK file and the bck file are merged, but the export or import is not started.

You can use the option 'R3load -h' to check whether the R3load contains the option '-merge_only'."

thx.

[Former Member]

Hi,

ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPSSEXC.TSK.bck already seems to exist a previous run may not have been finished cleanly.

The above error indicates the previous run of step R3load finished uncleanly. The R3load has been canceled.

Please restart the R3load with parameter "-merge_bck", check note 455195, especially the last paragraph.

Cheers!