Problems with installation when run phase 17 of 24

[Former Member]

Can someone help me?

I have windows 2003 enterprise edition and j2sdk1.4.2_11

I start the installation of Netweaver 2004 and when I arrived to the phase 17 (Import ABAP) an error occurs and display :

-

---

ERROR 2006-03-13 15:44:52

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

-

---

ERROR 2006-03-13 15:44:52

FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|10|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .

-

---

the import_monitor.java.log contains:

java version "1.4.2_11"

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

Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)

Import Monitor jobs: running 1, waiting 17, completed 0, failed 0, total 18.

Import Monitor jobs: running 2, waiting 16, completed 0, failed 0, total 18.

Import Monitor jobs: running 3, waiting 15, completed 0, failed 0, total 18.

Loading of 'SAPSSEXC' import package: ERROR

Import Monitor jobs: running 2, waiting 15, completed 0, failed 1, total 18.

Loading of 'SAPAPPL1' import package: ERROR

Import Monitor jobs: running 1, waiting 15, completed 0, failed 2, total 18.

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 0, waiting 15, completed 0, failed 3, total 18.

Import Monitor jobs: running 1, waiting 14, completed 0, failed 3, total 18.

Import Monitor jobs: running 2, waiting 13, completed 0, failed 3, total 18.

Import Monitor jobs: running 3, waiting 12, completed 0, failed 3, total 18.

Loading of 'SAPSDIC' import package: ERROR

Import Monitor jobs: running 2, waiting 12, completed 0, failed 4, total 18.

Loading of 'SAPSSRC' import package: ERROR

Import Monitor jobs: running 1, waiting 12, completed 0, failed 5, total 18.

Loading of 'SAPAPPL2' import package: ERROR

Import Monitor jobs: running 0, waiting 12, completed 0, failed 6, total 18.

Import Monitor jobs: running 1, waiting 11, completed 0, failed 6, total 18.

Import Monitor jobs: running 2, waiting 10, completed 0, failed 6, total 18.

Import Monitor jobs: running 3, waiting 9, completed 0, failed 6, total 18.

Loading of 'SAPPOOL' import package: ERROR

Import Monitor jobs: running 2, waiting 9, completed 0, failed 7, total 18.

Loading of 'SAPSLEXC' import package: ERROR

Import Monitor jobs: running 1, waiting 9, completed 0, failed 8, total 18.

Loading of 'SAPSPROT' import package: ERROR

Import Monitor jobs: running 0, waiting 9, completed 0, failed 9, total 18.

Import Monitor jobs: running 1, waiting 8, completed 0, failed 9, total 18.

Import Monitor jobs: running 2, waiting 7, completed 0, failed 9, total 18.

Import Monitor jobs: running 3, waiting 6, completed 0, failed 9, total 18.

Loading of 'SAPSLOAD' import package: ERROR

Import Monitor jobs: running 2, waiting 6, completed 0, failed 10, total 18.

Loading of 'SAPSDOCU' import package: ERROR

Import Monitor jobs: running 1, waiting 6, completed 0, failed 11, total 18.

Loading of 'SAPCLUST' import package: ERROR

Import Monitor jobs: running 0, waiting 6, completed 0, failed 12, total 18.

Import Monitor jobs: running 1, waiting 5, completed 0, failed 12, total 18.

Import Monitor jobs: running 2, waiting 4, completed 0, failed 12, total 18.

Import Monitor jobs: running 3, waiting 3, completed 0, failed 12, total 18.

Loading of 'SAPDDIM' import package: ERROR

Import Monitor jobs: running 2, waiting 3, completed 0, failed 13, total 18.

Loading of 'SAPDODS' import package: ERROR

Import Monitor jobs: running 1, waiting 3, completed 0, failed 14, total 18.

Loading of 'SAPDFACT' import package: ERROR

Import Monitor jobs: running 0, waiting 3, completed 0, failed 15, total 18.

Import Monitor jobs: running 1, waiting 2, completed 0, failed 15, total 18.

Import Monitor jobs: running 2, waiting 1, completed 0, failed 15, total 18.

Loading of 'SAPUSER' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 0, failed 16, total 18.

Loading of 'SAP0000' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 0, failed 17, total 18.

-

---

and part of the import_monitor.log contain:

INFO: 2006-03-13 20:08:34

Import Monitor is started.

CONFIG: 2006-03-13 20:08:34

Application options:

dbCodepage=1100

dbType=ADA

extFiles=no

impJobNum=3

importDirs=C:\SAPNW2004sSneakPreviewABAP\NSPExport\ABAP

installDir=C:\Archivos de programa\sapinst_instdir\NW04S\LM\COPY\ADA\SYSTEM\CENTRAL\AS-ABAP

jobNum=3

loadArgs= -nolog

monitorTimeout=30

orderBy=size

r3loadExe=C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2006-03-13 20:08:34

List of packages with table structure: 'SAP0000'.

CONFIG: 2006-03-13 20:08:34

List of packages with views: 'SAPVIEW'.

INFO: 2006-03-13 20:08:34

Data codepage 1100 is determined using TOC file 'C:\SAPNW2004sSneakPreviewABAP\NSPExport\ABAP\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.

TRACE: 2006-03-13 20:08:34 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC' import package is started.

TRACE: 2006-03-13 20:08:34 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is started.

TRACE: 2006-03-13 20:08:34 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL0' import package is started.

TRACE: 2006-03-13 20:08:34 com.sap.inst.migmon.LoadTask processPackage

Task file generation for 'SAPSSEXC' import package:

C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -ctf I C:\SAPNW2004sSneakPreviewABAP\NSPExport\ABAP\DATA\SAPSSEXC.STR DDLADA.TPL SAPSSEXC.TSK ADA -l SAPSSEXC.log

TRACE: 2006-03-13 20:08:34 com.sap.inst.migmon.LoadTask processPackage

Task file generation for 'SAPAPPL1' import package:

C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -ctf I C:\SAPNW2004sSneakPreviewABAP\NSPExport\ABAP\DATA\SAPAPPL1.STR DDLADA.TPL SAPAPPL1.TSK ADA -l SAPAPPL1.log

TRACE: 2006-03-13 20:08:34 com.sap.inst.migmon.LoadTask processPackage

Task file generation for 'SAPAPPL0' import package:

C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -ctf I C:\SAPNW2004sSneakPreviewABAP\NSPExport\ABAP\DATA\SAPAPPL0.STR DDLADA.TPL SAPAPPL0.TSK ADA -l SAPAPPL0.log

TRACE: 2006-03-13 20:08:35 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPSSEXC' import package into database:

C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 1100 -l SAPSSEXC.log -nolog

TRACE: 2006-03-13 20:08:35 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL1' import package into database:

C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 1100 -l SAPAPPL1.log -nolog

TRACE: 2006-03-13 20:08:36 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL0' import package into database:

C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 1100 -l SAPAPPL0.log -nolog

ERROR: 2006-03-13 20:20:41 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC' import package is interrupted with exception.

com.sap.inst.lib.io.ProcessExitException: Process 'C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 1100 -l SAPSSEXC.log -nolog' exited with return code 2

at com.sap.inst.migmon.LoadTask.loadPackage(LoadTask.java:534)

at com.sap.inst.migmon.LoadTask.processPackage(LoadTask.java:257)

at com.sap.inst.migmon.LoadTask.run(LoadTask.java:176)

at java.lang.Thread.run(Thread.java:534)

at com.sap.inst.lib.util.ThreadDispatcher$ThreadWrapper.run(ThreadDispatcher.java:113)

ERROR: 2006-03-13 20:20:43 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is interrupted with exception.

com.sap.inst.lib.io.ProcessExitException: Process 'C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 1100 -l SAPAPPL1.log -nolog' exited with return code 2

at com.sap.inst.migmon.LoadTask.loadPackage(LoadTask.java:534)

at com.sap.inst.migmon.LoadTask.processPackage(LoadTask.java:257)

at com.sap.inst.migmon.LoadTask.run(LoadTask.java:176)

at java.lang.Thread.run(Thread.java:534)

at com.sap.inst.lib.util.ThreadDispatcher$ThreadWrapper.run(ThreadDispatcher.java:113)

ERROR: 2006-03-13 20:20:44 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL0' import package is interrupted with exception.

com.sap.inst.lib.io.ProcessExitException: Process 'C:\usr\sap\NSP\SYS\exe\nuc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 1100 -l SAPAPPL0.log -nolog' exited with return code 2

at com.sap.inst.migmon.LoadTask.loadPackage(LoadTask.java:534)

at com.sap.inst.migmon.LoadTask.processPackage(LoadTask.java:257)

at com.sap.inst.migmon.LoadTask.run(LoadTask.java:176)

at java.lang.Thread.run(Thread.java:534)

at com.sap.inst.lib.util.ThreadDispatcher$ThreadWrapper.run(ThreadDispatcher.java:113)

.

.

.

.

.

and another 90kb of error text

-

---

I repeat the installation 2 times but i don't have success.

What can I do wrong?

Thanks

[athavanraja · Accepted solution]

the problem is because of j2sdk1.4.2_11

you have to use <b>j2sdk1.4.2_08</b>

Regards

Raja

[Former Member · Accepted solution]

Thanks for the reply but that was not correct the problem.

I think the version is not the problem, because if I need to upgrade the J2SDK in future, what will be happen to the SAP??

[athavanraja · Accepted solution]

this is a know issue. if you look at the installation documentation one of the prerequisite is to use proper version of jdk. and we have heard in this forum many times that wrong version of jdk causes problem. uninstall everything, install 1.4.2_08 and reinstall ABAP you will be able to install it successfully

Regards

Raja

[Former Member · Accepted solution]

I'm sorry about my incredulity, but you have all the reason. I uninstall j2sdk1.4.2_11 and install j2sdk1.4.2_08 version and the installation complete succesfull.

Now, I install the sapgui but I don't enter to SAP. I read that I need to install WebDynProClient.reg, so I downloaded and install it but I have the same result.

At Sap Logon, only appears 3 folders: "Direct Access, Systems and Web Dynpro Applications" but it don`t have any information to access to SAP.

Thanks

[athavanraja · Accepted solution]

its ok. i too learned it the hardway. if you go thru the installtaion prereqisites ,verbatim, you will not have any problem.

anyhow coming to your question.

webdynpro client is not a prerequisite to log on to SAP system. what you need to do is to create a system under systems tab

1. click on user defined

2. in the resulting screen enter the following values

Description = some text

Application server = your computer name

system id = NSP

system number = the number you have specified during installation. (it will be two digit number)

and hit save.

now double click on the new created entry in under system tab

Hope this is clear.

Regards

Raja

[Former Member · Accepted solution]

Sorry, but installation guide for NW2004s, part 2.2.10 Preparing the System for SAPinst, points to SAP Note 709140, which in turn points to note 716604:

Please use Sun J2SE 1.4.2_09 SDK (or higher 1.4.2 versions after they will become available). It is not recommended to use versions lower than 1.4.2_09. Please also do not use J2SE 5.0.

so why not using 1.4.2.11? BTW the remark '... or higher 1.4.2 version after they will become available' repeats in all NW installation guides. If SAP is not able to give us the appropriate hint about Java version, they should include it with SAP as boundle, like for example Oracle is doing since release 8.

Regards

Robert

[Former Member · Accepted solution]

If you read the whole note you will see that after the paragraph you copied,

Please use Sun J2SE 1.4.2_09 SDK (or higher 1.4.2 versions after they will become available). It is not recommended to use versions lower than 1.4.2_09. Please also do not use J2SE 5.0.

comes this paragraph

Important note:

In contrast to the recommendation above please do not use J2SE 1.4.2_10 as it has problems during installation. The problem is under investigation.

The J2SE 1.4.2 SDK is available from

http://java.sun.com .

[athavanraja · Accepted solution]

I dont have access to OSS right now, so couldnt get a chance to read the notes.

but this thread is about the issue with NW2004sSneakPreviewABAP installtion and the installtion guide for this clearly says that you have to use 1.4.2_08.

it may be different for full version.

Regards

Raja

[Former Member · Accepted solution]

Hi,

I posted the same problem here:

J2sdk 1.4.2_08 also doesn't work. The installation stops now at phase 11 of 24.

I agree Robert, why is it such a big problem to do a working bundle, or better to a big archive which has only be extract in a folder and than start the system.

thx for any help

Rossi

[former_member192029 · Accepted solution]

Hi

I'm using J2SDK1.4.2_11 and it works fine.

I guess please meet the pre-requiste and check the system authorisation ( admin user)

Cheers

Jawahar Govindaraj

[Former Member · Accepted solution]

Hi,

I've done a new User as local admin.

Rossi

[former_member339862]

you DB should be running. Please check that

[Former Member]

Hi,

I am having the same problem. I have 17 jobs completed, 1 failed and 1 waiting. Does anybody know if there is a way to restart 18th job. I want to try it again. When I continue the installation, it is not trying to attempt 18th job again.

Thanks,

Gaurav

[Former Member]

Hallo all,

I am a newcomer in SAP technology but I tried to install Netweaver 2004 because I have to have opportunity to test.

I have already had the problem mentioned above many times when I tried to install.

I tried on two different computers with JDK 1.4.2_11 installed. Both computers are with WinXP SP2. I succeed to install on third computer with WinXP SP1 and JDK 1.4.2_11. The installation was not very clean and did not succeed to the end. There was an error at the last step. However, the system is started now and I can even log in remotely, i.e. SAP GUI is installed on the one machine and Netweaver 2004 system on the other.

I tried to continue the installation with nspadm local account but unsuccessfully.

Best regards,

Detelin Nedev

[yuri_shikunov]

Hi,

This problem is not related to JRE version.

The error description you can find in the R3load log file, ex. SAPSSEXC.log (look for "ERROR:" strings in the import_monitor.log file).

Regards,

Yuri

[Former Member]

Hi.

I had a similar problem with JDK 1.4.2_11 installed. After a clean install of JDK 1.4.2_12, I still got the same/similar error.

In the end what worked for me was that I stopped at the point of getting the error, logged off my account, logged in as the <SID>adm and restarted and continued the install. Worked then.

Hope this helps you.

Regards,

Reenal

[Former Member]

Hi,

I faced similar problem at step 18 of 45 for Sol Man 4.0 installation. After I uninstalled JDK 1.4.2_12 and installed 1.4.2_08, I encountered error "Java Home directory must exist" error at the same step. In Env variable already set JAVA_HOME = C:\j2sdk1.4.2_08 and added in Path = ...;%JAVA_HOME%\bin;.

Any idea what's wrong here? greatly appreciate yr advice.

Regards,

Jocelyn

[Former Member]

Re: IDES ECC60 installation problems

Posted: Sep 3, 2006 12:17 PM Reply

I am trying to install Solution Manager and ECC 6.0 as well.

While installing SolMan, everything goes fine, however while importingABAP monitor jobs, 15 out of 18 monitor packages gets imported fine, then it runs into following error messages.

I am performing installation on Windows 2003 server SP1, Have J2SDK1.4.2_11 and loopback adapter installed.

Oracle v10.2 has already been patched with 10.2.0.2

Error Message:

=====================

WARNING 2006-09-03 11:40:21

Execution of the command "C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs G:\ECC6\Solman\2\DVD_4.0_SAP_Solution_Manager_Export_Lang\EXP1;G:\ECC6\Solman\3\DVD_4.0_SAP_Solution_Manager_Export_Lang\EXP2;G:\ECC6\Solman\4\DVD_4.0_SAP_Solution_Manager_Export_Lang\EXP3;G:\ECC6\Solman\5\DVD_4.0_SAP_Solution_Manager_Export_Lang\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\C12\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_11"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06)Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)Import Monitor jobs: running 1, waiting 2, completed 15, failed 0, total 18.Import Monitor jobs: running 2, waiting 1, completed 15, failed 0, total 18.Loading of 'SAPAPPL0' import package: ERRORImport Monitor jobs: running 1, waiting 1, completed 15, failed 1, total 18.Loading of 'SAPAPPL2' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 15, failed 2, total 18.

ERROR 2006-09-03 11:40:21

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

ERROR 2006-09-03 11:40:21

FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|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 .

================================================

Since you guys already ran into similar problem, would like your help on resolving this issue.

Btw - were you guys able to finally resolve this problem ?

Many thanks,

Chris

[Former Member]

Hi,

This is Alex.

As im doing ECC 6.0 instalallation, all the checks are finished and when iam starting my installation it shows a error in the 19th process that is IMPORT ABAP process in which the same error " Import package .... interrupted with exception" occurs though i have jdk1.4.2_08.

Pls give me the instruction how to proceed with this.

The error is exactly same as the previous Netweaver installation error.

Check and revert asap.

Thanks,

Alex.P

[Former Member]

I can confirm this approach:

1) uninstall any portions of the NW2004s that you may have attempted, including removing any previous logs

2) then uninstall ANY/ALL Java SDK's and JRE's that you have on your machine

3) reinstall ONLY 1.4.2_08 SDK & JRE

4) Reinstall the NW2004s

• One thing to be very careful of is to keep special characters out of all of your passwords during installation...that hung me up for several tries as well!