Solut Manager v4.0 install. error : CJS-30022 Program 'Migration Monitor

Hi Experts
I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
ERROR 2007-08-11 18:03:25
CJS-30022 Program 'Migration Monitor'
exits with error code 103.
For details see log file(s) import_monitor.java.log, import_monitor.log.
C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
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|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 .
WARNING 2007-08-11 18:03:25
Execution of the command "C:\java\bin\java.exe -classpath migmon.
jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
"C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
"C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\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_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
Any suggesstions/ideas for this error
Regards
Rahul

Check the logfile SAPAPPL0.log for errors...
Markus

Similar Messages

CJS-30022 Program 'Migration Monitor'

Hi Experts
I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
ERROR 2007-08-11 18:03:25
CJS-30022 Program 'Migration Monitor'
exits with error code 103.
For details see log file(s) import_monitor.java.log, import_monitor.log.
C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
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|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 .
WARNING 2007-08-11 18:03:25
Execution of the command "C:\java\bin\java.exe -classpath migmon.
jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
"C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
"C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\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_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
Any suggesstions/ideas for this error
Regards
Rahul

I just encountered this same error, except it was during an export of an ECC 6.0 Source system. I searched SDN for an answer and then worked my counterpart in Japan. My problem turned out to be the version of the R3Load.exe I was using. It was the latest available on Marketplace. I reverted back to the one that was delivered with kernel patch 102 and my export completed with no errors. I made sure to do the same on the Target system so I did not get the errors during the import.
Hope this helps...

Solution Manager 4.0 install Error

I am trying to install Solution Manager 4.0 on a IA64 server running Windows 2003(64 bit edition). I have SQL Server 2005. I have JDK versionj2sdk1.4.2_12-x64.
The sapinst.exe error log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++++++
SAPINST.EXE error
ERROR 2006-08-09 11:00:23
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-08-09 11:00:23
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 .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
The Error entries in the Import_monitor log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++
ERROR: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\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: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\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
++++++++++++++++++++++++++++++++++++++++++++++++++++
The error entry in the SAPSSEXC.log mention in the Import_monitor log is as follows:
++++++++++++++++++++++++++++++++++++++++++++++++++
(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\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
++++++++++++++++++++++++++++++++++++++++++++++++++++
The error entry in the SAPAPPL0.log mention in the Import_monitor log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.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\SAPAPPL0.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: START OF LOG: 20060809111000
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Apr 3 2006 02:55:14
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.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\SAPAPPL0.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809111001
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please let me know.
Thanks
Mikir

Hello.
I'm currently installing SAP BW 3.50 on Oracle 10.2, Windows 2003, J2SDK 1.4.2_11. As of now, i've got an error when i put these reference:
SAP:BW-MMR:630_SP3_REL:::*
SAP:BW-SDK:630_SP3_REL:::*
Kindly help on how to resolve this.
Thanks.

Solution Manager 4.0 install error logging in for DDIC step 29

Has anyone else seen the error 'Test logon to SAP System <sid> failed"? It states that it cannot login for DDIC. This is at step 29 during the install of the solution manager 4.0.
We are running on a Windows 2003 Server/Oracle 10g.
Any help would be greatly appreciated. We've been hitting this same error for the last couple of days.
Thanks,
DBB

Dear Derrick,
I have run into the exact same problem!!!!
During step 29 of the install does it ask you to enter the DDIC password?
It will ask you twice for a password if both the times the login fails then you will have no other option but to uninstall and reinstall Sol Man 4.
The tactic that worked for me is that when it will ask u the passowrd the first time.......before you enter the password.......login in to Sol Man 4 using the default DDIC password 19920706. then change the default password. And then go back to the install and give this new ddic password.
This is the only thing that worked with me.
Let me know if anything else works.
Email me @ [email protected] if you have any other questions.
thanks
Mikir

Solution Manager 7.0 Install Error

Morning Experts,
I'm installing a central instance on windows 2003 vm, 8gb ram, 200gb disk space, MS SQl Server 2005. During install it gets to the point of starting the intance and times out. Here's the error:
This was in the startBPC log (bpc name of sapid):
running D:\usr\sap\BPC\SYS\exe\uc\NTAMD64\sapstart.exe name=BPC nr=00 SAPDIAHOST=DAL-VS-SAPMGR -wait
SAPSTART finished successfully on DAL-VS-SAPMGR_BPC_00, but at least one process doesn't run correctly:
D:\usr\sap\BPC\SYS\exe\uc\NTAMD64\sapstart.exe=>sapparam(1c): No Profile used.
any idea why it would stop the instance and not be able to start it?
Thanks,
Bart

Hello Barton,
This may be due to Message Server connection failed.
try to add the entry in the c:\windows\system32\drivers\ect\services
sapmsJ2E 3600/tcp
if your System ID is J2E and the intance no is 00
wait for some time or restart the host and try for installation.
Hope it helps.
Cheers,
Satish.

ECC v6.0 installation error : CJS-30022 and FCO-00011

Hi All,
I enconter the while installing ECC 6.0 in windows 2003 server and MSSQL 2005 as the database. The error occurs during import ABAP phase ( exactly the Job name was SAPSDIC and this is the first job out of 19)
The same issue has been discussed in this forum but for oracle( Please find the link below for it)Kindly let me know how to fix it and since the database i am using it is SQL 2005 i am really confused on what should i change exactly.
Re: Solution Manager v4.0 installation error : CJS-30022 and FCO-00011
regards,
Anandha Krishnan.R

Sunil,
The log file is pasted.
===== Log file of import.monitor.log =============
TRACE: 2007-04-18 18:45:15 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe -ctf I "E:\SAP ERP 2005 IDES\51032413_4_IDES SAP ERP 2005 SR2 Inst. Export\EXP4\DATA\SAPSDIC.STR" "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2007-04-18 18:45:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast
ERROR: 2007-04-18 19:00:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSDIC.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: 2007-04-18 19:01:00
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2007-04-18 19:01:00
1 error(s) during processing of packages.
INFO: 2007-04-18 19:01:00
Import Monitor is stopped.
===== Log file of import.monitor.java.log =============
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)
Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 0, waiting 18, completed 0, failed 1, total 19.
===== Log file of SAPSDIC.TSK =============
T F4TMP C ok
P F4TMP~0 C ok
D F4TMP I ok
T F4UHLP C ok
P F4UHLP~0 C ok
D F4UHLP I err
Note : Other than the last task all the other tasks were found to be ok
===== Log file of SAPSDIC.log =============
(DB) INFO: ENHA_TMDIR~CMP created
(DB) INFO: ENHA_TMDIR~ENH created
(DB) INFO: ENHA_TMDIR~MTD created
(DB) INFO: F4TMP created
(DB) INFO: F4TMP~0 created
(IMP) INFO: import of F4TMP completed (1404 rows) #20070418185312
(DB) INFO: F4UHLP created
(DB) INFO: F4UHLP~0 created
(CNV) WARNING: code page conversion problem
Number of substitutions: 5
(row 3322 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 22 04 3e 04 47 04 3a 04 38 04 20 00 20 00 20 00 |".>.G.:.8. . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 9
(row 3323 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 23 04 41 04 3a 04 3e 04 40 04 35 04 3d 04 38 04 |#.A.:.>[email protected].=.8.|
VALUE 35 04 20 00 20 00 20 00 20 00 20 00 20 00 20 00 |5. . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 4
(row 3324 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 26 04 38 04 3a 04 3b 04 20 00 20 00 20 00 20 00 |&.8.:.;. . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 7
(row 3325 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 27 04 30 04 41 04 42 04 3e 04 42 04 30 04 20 00 |'.0.A.B.>.B.0. .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 13
(row 3326 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 15 04 3c 04 |-.;.5.:.B.@...<.|
VALUE 3a 04 3e 04 41 04 42 04 4c 04 20 00 20 00 20 00 |:.>.A.B.L. . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 19
(row 3327 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 21 04 3e 04 |-.;.5.:.B.@.!.>.|
VALUE 3f 04 40 04 3e 04 42 04 38 04 32 04 3b 04 35 04 |?.@.>.B.8.2.;.5.|
VALUE 3d 04 38 04 35 04 20 00 20 00 20 00 20 00 20 00 |=.8.5. . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 18
(row 3328 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 38 04 47 04 |-.;.5.:[email protected].|
VALUE 1d 04 30 04 3f 04 40 04 4f 04 36 04 35 04 3d 04 |[email protected].=.|
VALUE 38 04 35 04 20 00 20 00 20 00 20 00 20 00 20 00 |8.5. . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 16
(row 3329 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3b 04 35 04 3a 04 42 04 40 04 38 04 47 04 |-.;.5.:[email protected].|
VALUE 35 04 41 04 3a 04 38 04 39 04 20 00 42 04 3e 04 |5.A.:.8.9. .B.>.|
VALUE 3a 04 20 00 20 00 20 00 20 00 20 00 20 00 20 00 |:. . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(CNV) WARNING: code page conversion problem
Number of substitutions: 7
(row 3330 of current buffer, table F4UHLP)
MANDT 38 00 30 00 30 00 |8.0.0. |
USERNAME 5a 00 48 00 55 00 4b 00 4f 00 56 00 20 00 20 00 |Z.H.U.K.O.V. . .|
USERNAME 20 00 20 00 20 00 20 00 | . . . . |
TABFIELD 54 00 30 00 30 00 36 00 54 00 20 00 20 00 20 00 |T.0.0.6.T. . . .|
TABFIELD 20 00 20 00 | . . |
FIELDFIELD 54 00 58 00 44 00 49 00 4d 00 20 00 20 00 20 00 |T.X.D.I.M. . . .|
FIELDFIELD 20 00 20 00 | . . |
VALUE 2d 04 3d 04 35 04 40 04 33 04 38 04 4f 04 20 00 |[email protected]. .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
VALUE 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .|
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed>
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: F4UHLP~1 created
(DB) INFO: GCTAB created
(DB) INFO: GCTAB~0 created
(IMP) INFO: import of GCTAB completed (0 rows) #20070418185312
(DB) INFO: GUI_FKEY created
(DB) INFO: GUI_FKEY~0 created
(IMP) INFO: import of GUI_FKEY completed (335 rows) #20070418185312
(DB) INFO: VRSX4~1 created
(DB) INFO: disconnected from DB
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\KR3\SYS\exe\nuc\NTI386\R3load.exe: END OF LOG: 20070418190034
regards,
Anandha Krishnan.R

I need your help(sap installation error : CJS-30022)

Hello My friends,
I meet so difficult problems.
- SAP NetWeaver Application Server ABAP 7.02 SP6 32-bit Developer Edition
- SAP NetWeaver Application Server ABAP 7.02 SP6 64-bit Developer Edition
In setting up above two version, it was interrupted on the menu during the installation.
I want to solve this problem.
To request help to solve this problem.
I searched "google" and " sdn.sap.com" but I didn't solve.
I installed the hardware OS xp 32bit cpu 2.4 ram 1 gb hdd 160 gb With OS windows7 64bit cpu 2.0 ram 3 gb hdd 80 gb ---
I installed as follows order
1.os xp pro, windows7 installation.
2.installing iis
3.As hdwwiz.exe MS Loopback Adapter network / ip: 10.10.0.10, 255.255.255.0
4.c: \ windows \ system32 \ drive \ etc \ host add to the 10.10.0.10 netweaver
5.The latest version of jre, java.com download at the click of a button installed in    path: JAVA_HOME setting
6.Computer swap size: 4096 - 4096
7. Turn off the firewall settings
The default setting is
run
D:\Setup\SAPNW7.01ABAPTrial.part1\SAPNWABAP701SR1_TRIAL\SAP_NetWeaver701SR1_2008_Installation_Master\IM_WINDOWS_I386
\sapinst.exe
should install, run
During the installation, it is interrupted from "Import abap menu".
I need your help.
--------- error log ---------
WARNING    2012-07-13 17:13:12.859
           CJSlibModule::writeWarning_impl()
Execution of the command ""C:\Program Files\Java\j2re1.4.2_19\bin\java.exe" -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 2. Output:
java version "1.4.2_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_19-b04)
Java HotSpot(TM) Client VM (build 1.4.2_19-b04, mixed mode)
Required system resources are missing or not available:
Import directory 'C:\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP2' does not have valid structure of subdirectories;
Import directory 'C:\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP3' does not have valid structure of subdirectories.
ERROR      2012-07-13 17:13:12.859
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR      2012-07-13 17:13:12.875 [sixxcstepexecute.cpp:988]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 2. For details see log file(s) import_monitor.java.log, import_monitor.log.).
INFO       2012-07-13 17:13:13.562 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\__instana_tmp.xml.
WARNING    2012-07-13 17:13:15.0 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2012-07-13 17:13:15.0 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .

Hello,
Which system are you getting the error, XP / Win 7 ?
Please find the minimum H/W requirement (Source Inst Guide)
Minimum RAM :- 4GB
Paging file size :- 1 times RAM plus 8 GB
If you are trying for win 7, then I would recommend you to
increase the swap space and give it a try.
It looks like it is not getting the required system
resources (RAM).
Thanks,
Vishal

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SOLUTION MANAGER 7.1 install on linux/oracle java error on ABAP IMPORT

Hello sdn experts, Im trying to install the Solution Manager 7.1 on linux/oracle, but It always stops at the abap import,
The error is in the Program "Migration Monitor", that exit with error.
Reviewing the logs, it seems that is trying to execute a java command line with a unrecognized option:
"Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 1. Output:
JVMJ9VM007E Command-line option unrecognized : -Xjvm:j9vm23"
Usage : java [-options] class...
As you can see, the sdk used is from IBM, and it works for all other saps we have here.
Is the wrong jdk? Which I should use if its wrong?
If is the right jdk, how could I get rid of this option and change it?
Any idea would be appreciated.
Thank you

Hi Maurici,
have you checked this note already?
[https://service.sap.com/sap/support/notes/1159935|https://service.sap.com/sap/support/notes/1159935]
It is about your error message. ...
Best, Hannes

SAP Solution Manager 4.0 Install on iSeries V5R4M0 fails on STEP 40 of 40

During Step 40 of 40 of Solution Manager 4.0 install on iSeries running i5/OS V5R3M0 failed with the following error:
ERROR 2006-08-18 10:00:57 [iaxxgenimp.cpp:728]
showDialog()
FCO-00011 The step fixTemplate400 with step key
|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|fixTemplate400
was executed with status ERROR .
TRACE [iaxxgenimp.cpp:657]
showDialog()
<html><head></head><body>An error occurred while processing service
SAP Solution Manager 4.0 > SAP Systems > IBM DB2 UDB for i
TRACE [iaxxgenimp.cpp:1093]
showDialog()
waiting for an answer from gui
***********End of Data*******************
Searching OSS Notes, there is no reference to the FCO-00011 error code

Hello Loli,
I think it was me, who misunderstood.
Now I followed your recommendations, increased virtual memory on the sapinst machine, restarted the pc and the installation and it completed successfully. Thank you very much.
Sorry that I can't give you points for the helpfull answer, because this is not my thread.
Kind regards,
Jürgen Scheckelhoff.

Solution Manager DB was installed in 'Simple mode'

We are just a couple months into our first SAP installation. I just received this message from my hardware/server guy:
"Please be aware that the Solution Manager DB was installed in Simple mode. This means that we dont have transaction logs, and will only be able to recover back to the most recent back-up."
How critical is this for solution manager?

Hi people!!
i found the solution, if some one have this problem, can check the sapnote 1951729.
if you don't see any changes, try creating the connection through trx. dbacockpit and then assing the DB conection created previously (dbco trx-sapnote). Next step check it on solman setup (enter system parameter step).
Best regards.
Iván.

Install ECC 6.0 and Solution Manager on same server Error (MaxDB/Linux)

I have installed Solution manager on one server and then ECC 6 also in the same server with another SID. during the installation it errored out at phase "SLD configuration" with UME error , J2EE_ADMIN locked etc..we checked the user id and noticed it got locked in ECC 6 system and we unlocked it.
But after the ECC installation the solution manager java engine is not coming up error with "com.sap.security.core.ume.service failed" error. Prior to the ECC installation the Solution Manager J2EE was working.
thanks in advance
Mathew

error in the /j2ee/cluster/server0/log/defaultTrace.1.trc
is as follows
#1.5#00137256A483001E0000001700006F190004163784D40864#1150327614343#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_61##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
When I looked at using jcmon the dispacher is up and the server0 and SDM is down

Solution Manager 4.0 Install Linux : UME phase 34 of 44 fails

I am trying to install Solution Manager 4.0 on Red Hat Enterprise 4 Linux with Oracle 10.2..... I am hung up at phase 34 of 44 of the installation where the UME is being set up...... I am running Java verion 1.4.2_12....
Any help is greatly appreciated....
Main error message is: CJS-30059 J2EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
 at com.sap.engine.offline.FileClassLoader.findClass
UMConfigurator log file:
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
 at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
 at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
 at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
SAPINST Log file:
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:15
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:15
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:16
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:16
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:17
Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.12.xml'.
INFO 2007-02-28 16:36:17
Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.13.xml'.
INFO 2007-02-28 16:36:32
Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.7.xml'.
INFO 2007-02-28 16:36:32
Execute step runUMConfigurator of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:45
Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties.
INFO 2007-02-28 16:36:45
Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties.
INFO 2007-02-28 16:36:46
Account slnadm already exists.
INFO 2007-02-28 16:36:46
Account 0 already exists.
INFO 2007-02-28 16:36:46
Account 500 already exists.
INFO 2007-02-28 16:36:46
Account sapsys already exists.
INFO 2007-02-28 16:36:46
Effective group id set to 501.
INFO 2007-02-28 16:36:46
Account 0 already exists.
INFO 2007-02-28 16:36:46
Account 501 already exists.
INFO 2007-02-28 16:36:46
Effective group id set to 500.
INFO 2007-02-28 16:36:46
Removed environment variable SSH_AGENT_PID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KDE_MULTIHEAD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOSTNAME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SHELL from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable TERM from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HISTSIZE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GTK2_RC_FILES from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GS_LIB from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GTK_RC_FILES from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable WINDOWID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPINST_EXEDIR_CD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KDE_FULL_SESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable USER from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LD_LIBRARY_PATH from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LS_COLORS from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable XCURSOR_SIZE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SSH_AUTH_SOCK from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KDEDIR from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SESSION_MANAGER from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KONSOLE_DCOP from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable MAIL from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DESKTOP_SESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable PATH from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable INPUTRC from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable PWD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KONSOLE_DCOP_SESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable JAVA_HOME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LANG from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPINST_EXE_DIR from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GDMSESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SSH_ASKPASS from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SHLVL from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable XCURSOR_THEME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LOGNAME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LESSOPEN from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DISPLAY from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable G_BROKEN_FILENAMES from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable XAUTHORITY from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable COLORTERM from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOSTTYPE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable VENDOR from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable OSTYPE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable MACHTYPE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GROUP from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOST from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SUPPORTED from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPSYSTEMNAME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DIR_LIBRARY from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable THREAD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable dbms_type from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable dbs_ora_tnsname from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable dbs_ora_schema from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable ORACLE_SID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DB_SID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable ORACLE_BASE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable TNS_ADMIN from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable ORACLE_HOME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable NLS_LANG from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPDATA_HOME from current process environment.
INFO 2007-02-28 16:36:47
Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfigurator.log.
INFO 2007-02-28 16:36:47
Output of /java/j2sdk1.4.2_12/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.tools.UMConfiguratorLoad /usr/sap/SLN/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/SLN/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/oracle/client/10x_32/instantclient/ojdbc14.jar -u ADMIN_USR=J2EE_ADMIN -u XXXXXX -u ADMIN_GRP=SAP_J2EE_ADMIN -u GUEST_USR=J2EE_GUEST -u GUEST_GRP=SAP_J2EE_GUEST -u ALL_GRP=Everyone -c CLIENT=001 -c COM_USR=SAPJSF -c XXXXXX -c ASHOST=localhost -c SYSNR=$$ -a setup -p abap -f /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties is written to the logfile umconfigurator.log.
INFO 2007-02-28 16:36:47
Execution of the command "/java/j2sdk1.4.2_12/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.tools.UMConfiguratorLoad /usr/sap/SLN/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/SLN/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/oracle/client/10x_32/instantclient/ojdbc14.jar -u ADMIN_USR=J2EE_ADMIN -u XXXXXX -u ADMIN_GRP=SAP_J2EE_ADMIN -u GUEST_USR=J2EE_GUEST -u GUEST_GRP=SAP_J2EE_GUEST -u ALL_GRP=Everyone -c CLIENT=001 -c COM_USR=SAPJSF -c XXXXXX -c ASHOST=localhost -c SYSNR=$$ -a setup -p abap -f /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties" finished with return code 0. Output:
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
 at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
 at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
 at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
ERROR 2007-02-28 16:36:47
CJS-30059 J2EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
 at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
 at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
 at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
ERROR 2007-02-28 16:36:47
FCO-00011 The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0|runUMConfigurator was executed with status ERROR .

Hi Carol,
Check note 716604 to see if you are using the correct JDK version.
The problem seem to be that JVM cannot find a class to load. This class should be
available as part of the contents of
/tmp/sapinst_instdir/NW04S/SYSTEM/XXX/CENTRAL/AS/install/ .
The contents of this directory normally come via unpacking of the
J2EEINSTALL.SAR archive from the <Java DVD>/J2EE_OSINDEP/J2EE-INST
location.
Need to unpack J2EEINSTALL.SAR and copy any missing files into install
directory with correct permissions. Check J2EEINSTALL.log to see what
files were unpacked.
Hope this helps if not let me know.
Best regards,
Dolores

Solution Manager 7.0 Installation Error on Import ABAP -Test DB connection

Hi, SDN fellows.
I am installing Solution Manager 7.0. In Step 16 of 44 - Import ABAP, I encountered an error when the installer was testing the database connection. It failed at this command:
R3load.exe -testconnect
Below is the error I copied from the log viewer. Thanks for all possible advices/suggestions to fix this issue.
=================
WARNING 2011-07-12 03:51:49.188
Execution of the command "C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110712035148
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
WARNING[E] 2011-07-12 03:51:49.188
CJS-30023 Process call 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR 2011-07-12 03:51:49.204
FCO-00011 The step testDatabaseConnection 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|testDatabaseConnection was executed with status ERROR .
=============
KC

cont....
4 ETW000 33 1.576524
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 1112312
4 ETW000 24 1.576548
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on open 19 1.576567
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 19 1.576586
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on fetch 13 1.576599
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 18 1.576617
4 ETW000 [dblink ,01299] ***LOG BZA=>table SVERS does not exist on database [dblink#5 @ 1299]
4 ETW000 8060 1.584677
4 ETW000 [dev trc ,00000] Wed Jul 13 23:41:19 2011 41342 1.626019
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000002234118
4 ETW000 25 1.626044
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 3649 1.629693
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.629726
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629745
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 27 1.629772
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629791
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "DDNTT" ]
4 ETW000 28 1.629819
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.629839
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM DDNTT FAILED 277 1.630116
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000003234118
4 ETW000 44 1.630160
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 459 1.630619
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.630652
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 18 1.630670
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 29 1.630699
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 23 1.630722
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "DDNTT" ]
4 ETW000 29 1.630751
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.630771
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM DDNTT FAILED 267 1.631038
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000004234118
4 ETW000 43 1.631081
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 436 1.631517
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.631549
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 18 1.631567
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 58 1.631625
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 19 1.631644
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "DDNTT" ]
4 ETW000 28 1.631672
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.631693
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM DDNTT FAILED
4 ETW000 284 1.631977
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 31 1.632008
4 ETW000 [twdydbacc.c ,00568] i:0 8690 1.640698
4 ETW000 [twdydbacc.c ,00569] db_fd_p.fname: PGMID 20 1.640718
4 ETW000 [twdydbacc.c ,00570] db_fd_p.is_key: 0 11 1.640729
4 ETW000 [twdydbacc.c ,00571] db_fd_p.offset: 0 10 1.640739
4 ETW000 [twdydbacc.c ,00572] db_fd_p.db_length: 0 10 1.640749
4 ETW000 [twdydbacc.c ,00573] db_fd_p.fixed_length:4 10 1.640759
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000005234118
4 ETW000 40 1.640799
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 434 1.641233
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.641265
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 75 1.641340
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 31 1.641371
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 18 1.641389
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "XXXXT" ]
4 ETW000 28 1.641417
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.641438
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM XXXXT FAILED 269 1.641707
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000006234118
4 ETW000 44 1.641751
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 437 1.642188
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.642220
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 18 1.642238
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.642266
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 19 1.642285
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "XXXXT" ]
4 ETW000 27 1.642312
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 70 1.642382
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM XXXXT FAILED 273 1.642655
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000007234118
4 ETW000 44 1.642699
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 435 1.643134
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.643166
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 19 1.643185
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.643213
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 20 1.643233
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "XXXXT" ]
4 ETW000 30 1.643263
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.643284
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM XXXXT FAILED
4 ETW000 324 1.643608
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 27 1.643635
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len (char): 5
2EETW000 key: TADIR
2EETW000 retcode: 2
4 ETW000 [dev trc ,00000] db_con_rollback (con_da={R/3,0,0},th_rollback=1,tx=0)
4 ETW000 9946 1.653581
4 ETW000 [dev trc ,00000] Rollback: TestConnection(1) successful 36526 1.690107

Solution Manager 4.0 Installation error on vmware

Hi guys,
I try to install the solution Manager 4.0 SR4 in a vmware server Win2003 64bit
and get the following error message in phase 17 (import ABAP)
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 2. 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)
Required system resources are missing or not available:
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP1' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP2' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP3' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP4' does not exist.
of course the path exists and the further dvd locations where also found?
is ther something wrong with the naming of the install dir?
must I have a character for the "harddrive"
Plse help
thank you and br
Wolfgang

Hello shareef,
there is no extra recommendation from SAP regarding SolMan on vmware.
SAP supports installations on vmware wheanwhile also for productive systems (plse check PAM).
The experience I have for my installation:
I works fine til now, no probs.
cu Wolfgang

Solut Manager v4.0 install. error : CJS-30022 Program 'Migration Monitor

Similar Messages

Maybe you are looking for