Yes. Please delete the virtual hostname and let SWPM installs it.
I faced such kind of problem and I just deleted the virtual hostname in the MSCS Failover management and it worked.
Take a screenshot for future use before deleting.
↧
Re: How to create virtual host for SAP High availability system
↧
Re: how to update java stack version in netweaver 7.4 in sap
Hi
The Java Support Package Manager (JSPM) is no longer supported in this SAP NetWeaver 7,4 release and is replaced by the Software Update Manager (SUM). Therefore, the JSPM documentation is now deleted from the respective documentation delivery.
↧
↧
Re: Program 'Migration Monitor' exits with error code 103.
Hi Marcin
Could you paste or attach import_monitor.java.log and What is the kernel and DBSL release ?
BR
SS
↧
Re: Program 'Migration Monitor' exits with error code 103.
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
↧
Re: Program 'Migration Monitor' exits with error code 103.
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
↧
↧
Re: Program 'Migration Monitor' exits with error code 103.
hi Marcin,
Please share this log COEJ.
Regards,
↧
Re: Program 'Migration Monitor' exits with error code 103.
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20150124142615
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\Users\Administrator\Desktop\SAP IDES UNPACK\51034985_1\EXP1\DATA\COEJ.STR C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL COEJ.TSK MSS -l COEJ.log
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: job completed
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20150124142615
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20150124142615
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i COEJ.cmd -dbcodepage 4103 -l COEJ.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: COEJ created
(DB) INFO: COEJ~0 created
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20150125025500
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i COEJ.cmd -dbcodepage 4103 -l COEJ.log -loadprocedure fast
(DB) INFO: connected to DB
(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
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20150125025501
↧
Re: Program 'Migration Monitor' exits with error code 103.
Can You clarify first point? Where I can find DBSL release? I'm not basis, so sorry for my 'simply' question.
↧
Re: Program 'Migration Monitor' exits with error code 103.
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
↧
↧
Re: how to update java stack version in netweaver 7.4 in sap
HI
You need to download the relevant stack with MOPZ (Solution manager)
and upgrade with Software Update Manager (SUM)
regards
naor
↧
Re: SAP Page size calculation
Hi
Please check the "Virtual Memory and Page File Size Required by SAP System Components" document
Approx. 500 MB + 1 to 2 times PHYS_MEMSIZE + 2.5 GB + 250 MB per work process
regards
naor
↧
Re: Program 'Migration Monitor' exits with error code 103.
Thanks for Your reply, currently, I'm out of office, I'll check this when I will have access to my office computer.
Regards,
Marcin
↧
Re: how to update java stack version in netweaver 7.4 in sap
Hi
The Java Support Package Manager (JSPM) is no longer supported in this SAP NetWeaver 7,4 release and is replaced by the Software Update Manager (SUM). Therefore, the JSPM documentation is now deleted from the respective documentation delivery.
↧
↧
Program 'Migration Monitor' exits with error code 103.
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.).
↧
Dispatcher - Running but Dialog Queue info unavailable
Dear friends
I ECC production system running on MSCS failover cluster with oracle dataase. CI was suddenly stopped.
Running but Dialog Queue info unavailable
Services started after restart CI.
But how can I found cause of this problem to prevent system from such issue.
↧
Re: Dispatcher - Running but Dialog Queue info unavailable
Hi.
Could you please clarify, are you seeking to determine the cause of the CI stopping or the Dialog Queue information is unavailable.
Thanks
Neil Ryan
SAP Active Global Support
↧
Re: Dispatcher - Running but Dialog Queue info unavailable
hi,
please share the log dev_w0 from DVEBMGS00/work directory?
Regards,
↧
↧
Re: Dispatcher - Running but Dialog Queue info unavailable
HI,
Since your CI installed on cluster, check cluster event logs.
↧
Re: SAPLPD has stopped working
It's probably a rhetorical question but I'll ask anyway...
If SAP is no longer supporting SAPLPD then why are they distributing an updated version...?
The version information for the executable is clearly 7.40, ask you can see in the event log entry from my failure (below) ...
Faulting application name: SAPlpd.exe, version: 7400.1.0.32, time stamp: 0x541f5aa6
Faulting module name: mfc110.dll, version: 11.0.60610.1, time stamp: 0x51b50f06
Exception code: 0xc0000005
Fault offset: 0x000544eb
Faulting process id: 0x1a74
Faulting application start time: 0x01d03ccb8aa04fa3
Faulting application path: C:\Program Files (x86)\SAP\FrontEnd\SAPgui\SAPlpd\SAPlpd.exe
Faulting module path: C:\windows\SYSTEM32\mfc110.dll
Report Id: db0a8e62-a8be-11e4-befc-c0ddb927f9e8
Faulting package full name:
Faulting package-relative application ID:
Note that the failure point is in the SAP Supplied, Microsoft-authored "mfc110.dll" module.
I applaud the resourcefulness of this group, and hacking a piece of the 7.30 distro onto the 7.40 install will most likely work but that's not a long-term solution.
Has anyone gotten a response from SAP on this error?
↧
Re: Dispatcher - Running but Dialog Queue info unavailable
Hi
On your Windows MSCS all the resources are online? or it getting failover to another node?
Could you share the log's ? Share the your SAP kernel version and release ?
BR
SS
↧