Content installation fails in 7.3 at ABAP program SAPLRRSI
Hi all,
We have a brand new 7.3 system, when we are trying to install standard content, we are getting a DUMP. Any clue what we are missing or anybody faced the same issue?
Category ABAP Programming Error
Runtime Errors RAISE_EXCEPTION
ABAP Program SAPLRRSI
Application Component BW-BEX-OT
And what is the highest SP level on 7.3? I tried to find it on service market place - but I dont see 7.3 listed out there.
Any pointer would be appreciated.
Thanks,
Voodi
Hi ,
The below link's may help u.
Dump RAISE_EXCEPTION; condition "X_MESSAGE"
Dump when activating Business Content 7.35
http://sap-core.com/troubleshoot/bw/bex/ot/class_RSDD/
Similar Messages
-
Business content installation failed
Hi
When i try to install the objects frok the business content, the job is getting cancelled and following msg is displayed in the SM37.
07.05.2008 17:51:28 STDO: Log could not be written on output device T
07.05.2008 17:51:28 STDO: Log could not be written on output device T
07.05.2008 17:51:28 STDO: Log could not be written on output device T
07.05.2008 17:51:28 STDO: Log could not be written on output device T
07.05.2008 17:51:28 STDO: Log could not be written on output device T
07.05.2008 17:51:28 STDO: Log could not be written on output device T
07.05.2008 17:52:07 ABAP/4 processor: SYSTEM_NO_TASK_STORAGE
07.05.2008 17:52:07 Job cancelled
I know this error comes due to lack of resource in the system.
My question here is how do i know what are the resources tat system is using and in which transaction code can i check it.
I have to tell basis guy to fix the issue. To tell him i need to know where the exact prlblem is.
Thanks
AnnieHi
The following is the dump information
Short text
Unable to fulfil request for 91904 bytes of storage space.
What happened?
Each transaction requires some main memory sp
application data. If the operating system can
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Regards
annie -
Selective Deletion of the Cube contents in Abap Program of the PChain
Dear Experts
I need to selectively delete the contents in Basic Infocube using Process Type - ABAP Program in the Process Chain in BW 3.5
For this I have to give the Variant and Program name in the Process Type - ABAP Program in the Process Chain
The ABAP Program for this purpose can be generated automatically by the system in the the below navigation
info cube> Manage>contents > system menu(in the Top)> Status
but this abap program is changing dynamically every time and hence in the Process chain ABAP Program node is failing with error saying that that program is not available
I have tried the same way in the selective deletin navigation path also in the cube manage
Please let me know how to get the system generated program to use in the Process type-ABAP Program in Process Chain
Thanks for all in advance
KSRHi KSR,
Try this.. start a selective deletion on the cube. you will get a background job running. Get the job name from SM37.
Now write a ABAP program with the below code.
parameter: p_Job_Name type sysuuid_c.
CALL METHOD cl_rscrmbw_bapi=>exec_rep_in_batch
EXPORTING i_barepid = l_jobnam.
Execute the above program. Pass the job name which you got from SM37.
Create a variant with that job name.
Now schedule this newly created program. This should solve your issue.
Note : The job name might vary from one server to another (Dev / Qual / Prod). So if you are planning to move your process chain from Dev, then pass the Job name (in prod) as the variant in yr Dev system and then transport it.
Cheer,
Balaji Venugopal -
BI Content 353 Installation failed in phase XPRA_EXECUTION
Hi Friends,
When I install BI_CONT 353 Add-on (i.e., SAPKIBIFIH) on a SAP Netweaver 2004 (640) the installation fails in phase XPRA_EXECUTION with error 12. Looking further in the logs, I found that the real problem is that the job RDDEXECL terminates with error GETWA_NOT_ASSIGNED.
Following are support patch levels already available in my system.
SPAM/SAINT -- SAPKD64023
SAP_BASIS -- SAPKB64014
SAP_ABA -- SAPKA64014
SAP_BW -- SAPKW35012
PI_BASIS2004_1_640 -- SAPKIPYI66
Is there a way I could remove my Add-On.
Thanks for any advise.Hi,
Thanks for your reply.
I installed entire system from the scratch again. Now itz working fine.
This time I have installed BI content with the default patch levels given below.
ABAP - release 640 , level 5
BASIS - release 640, level 5
BW - release 350, level 5
Later I updated ABAP,BASIS, BW patch levels from 5 to 20. -
Solution Manager Installation Fails at step Run ABAP Reports
I'm trying to install Solution Manager 4.0 on Windows 2003 using SQL 2005. The installation fails at the Run ABAP Reports step: Executing ABAP report RADDBDIF
I have logged in manually and run the RADDBDIF job in SE38 but I receive the same error message. My SAPTRANHOST is properly defined and so are the shares. Can anyone help? Thank!
Here's the sapinst_dev.log:
Calling function module: INST_RFC_GET_INTERFACE
INFO 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1065]
CAbRfcImpl::performFunctionCall
Function call was successful.
TRACE 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1066]
CAbRfcImpl::performFunctionCall
Function module call succesful: INST_RFC_GET_INTERFACE
INFO 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:924]
CAbRfcImpl::getRfcInterfaceSAP
Function interface generated successfully.
INFO 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:926]
CAbRfcImpl::getRfcInterfaceSAP
Technical properties of function set successfully.
INFO 2008-10-21 14:00:34.842 [iaxxrfcfls.cpp:107]
CRfcFuncRep::insFuncIf
Information for application function INST_EXECUTE_REPORT copied to local repository.
TRACE 2008-10-21 14:00:34.842 [iaxxrfcfls.cpp:108]
CRfcFuncRep::insFuncIf
Function interface entered into repository for INST_EXECUTE_REPORT
INFO 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:622]
CAbRfcImpl::setFunction
Function module INST_EXECUTE_REPORT set successfully.
TRACE 2008-10-21 14:00:34.842
2008-10-21 14:00:34.842 JSCo.setFunction() done: true
TRACE 2008-10-21 14:00:34.842
2008-10-21 14:00:34.842 JSCo.setParameter(PARA, [])
TRACE 2008-10-21 14:00:34.842
2008-10-21 14:00:34.842 JSCo.setParameter() done: true
TRACE 2008-10-21 14:00:34.842
2008-10-21 14:00:34.842 JSCo.setParameter(PROGRAM, RADDBDIF)
TRACE 2008-10-21 14:00:34.842
2008-10-21 14:00:34.842 JSCo.setParameter() done: true
TRACE 2008-10-21 14:00:34.842
2008-10-21 14:00:34.842 JSCo.execute()
INFO 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1032]
CAbRfcImpl::callFunction
Executing function call INST_EXECUTE_REPORT.
TRACE 2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1056]
CAbRfcImpl::performFunctionCall
Calling function module: INST_EXECUTE_REPORT
ERROR 2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1089]
CAbRfcImpl::performFunctionCall
FRF-00025 Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
TRACE 2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1090]
CAbRfcImpl::performFunctionCall
RFC failure or system exception raised
TRACE 2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1091]
CAbRfcImpl::performFunctionCall
Exception condition "WRITE_FAILED" raised.
INFO 2008-10-21 14:00:35.045 [iaxxbjsco.cpp:561]
CIaJSCo::disconnect_nothrow(000:DDIC:EN:nath02:00::SOL:)
RFC connection closed.
TRACE 2008-10-21 14:00:35.45 [iaxxejsbas.hpp:408]
handleException<ERfcExcept>()
Converting exception into JS Exception ERfcException.
TRACE 2008-10-21 14:00:35.045
Function setMessageIdOfExceptionMessage: modlib.jslib.caughtException
ERROR 2008-10-21 14:00:35.045
CJSlibModule::writeError_impl()
MUT-03025 Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
TRACE 2008-10-21 14:00:35.45 [iaxxejsbas.hpp:483]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2008-10-21 14:00:35.45 [sixxcstepexecute.cpp:951]
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR ( Last error reported by the step :Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..).
TRACE 2008-10-21 14:00:35.61 [iaxxgenimp.cpp:752]
CGuiEngineImp::showMessageBox
<html> <head> </head> <body> <p> An error occurred while processing service SAP Solution Manager 4.0 Support Release 4 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step :Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..). You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS. </p> </body></html>
TRACE 2008-10-21 14:00:35.61 [iaxxgenimp.cpp:1255]
CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUIHello Amélie,
Check the file systems if you're not ran out of disk space.
Second, check the database if you've enough storage space left.
Hope it helps.
Cheers,
Satish. -
IDES ECC 6.0 Installation failed at IMPORT ABAP -- Urgent pls....
Hi Gurus,
ecc6 installation failed at IMPORT ABAP step (to be precise - 16th step out of 19 steps) while importing 'SAPSSEXC' package .....
snippets of following logs are below
1> IMPORT_MONITOR.LOG
2> SAPINST.LOG
3> SAPSSEXC.LOG
<h2>IMPORT_MONITOR.LOG</h2>
ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l
SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
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
INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2008-01-08 02:42:17
Cannot start import of packages with views because not all import packages with tables are loaded
successfully.
WARNING: 2008-01-08 02:42:17
1 error(s) during processing of packages.
INFO: 2008-01-08 02:42:17
Import Monitor is stopped.
<h2>SAPINST.LOG</h2>
WARNING 2008-01-08 02:42:21
Execution of the command "C:\j2sdk1.4.2_16-x64\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs
F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:
\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F
:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11 -installDir
C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS -orderBy "" -r3loadExe
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3
-monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code
103. Output:
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
Loading of 'SAPAPPL2' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
ERROR 2008-01-08 02:42: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 2008-01-08 02:42:24
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|in
d|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio
nMonitor was executed with status ERROR .
<h2>SAPSSEXC.LOG</h2>
(DB) INFO: D301T~A created
(DB) INFO: D345T created
(DB) INFO: D345T~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of D345T completed (6585 rows) #20080107180224
(DB) INFO: DSYST created
(DB) INFO: DSYST~0 created
(IMP) INFO: import of DSYST completed (54353 rows) #20080107194721
(DB) INFO: DYNPSOURCE created
(DB) INFO: DYNPSOURCE~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of DYNPSOURCE completed (190478 rows) #20080107205002
(DB) INFO: ENHSPOTCONTRACT~1 created
(DB) INFO: ENHSPOTHEADER created
(DB) INFO: ENHSPOTHEADER~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of ENHSPOTHEADER completed (4078 rows) #20080107205109
(DB) INFO: INDTEXT created
(DB) INFO: INDTEXT~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(DB) INFO: PERMISSION created
(DB) INFO: PERMISSION~0 created
(IMP) INFO: import of PERMISSION completed (112356 rows) #20080107214109
(DB) INFO: PERMISSION~IF created
(DB) INFO: REPOSRC created
(DB) INFO: REPOSRC~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
ANY POINTERS WILL BE HIGHLY APPRECIATED
THANKS IN ADVANCEno...loading was not finished....it aborted with 'Retry', 'View Log', & Stop options...i retried with no luck...
this is 'Central system ' installation btw....
it failed with below error
ERROR 2008-01-08 02:42:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
<h2>IMPORT_MONITOR.LOG</h2>
INFO: 2008-01-07 16:33:26
Import Monitor is started.
CONFIG: 2008-01-07 16:33:26
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11
installDir=C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2008-01-07 16:33:26
List of packages with table structure: 'SAP0000'.
CONFIG: 2008-01-07 16:33:26
List of packages with views: 'SAPVIEW'.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2008-01-07 16:33:26
Data codepage 4103 is determined using TOC file 'F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
TRACE: 2008-01-07 16:33:28 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
INFO: 2008-01-08 00:15:00 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is successfully completed.
TRACE: 2008-01-08 00:15:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2008-01-08 00:15:27 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
INFO: 2008-01-08 00:15:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2008-01-08 00:15:58 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
TRACE: 2008-01-08 00:16:02 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
INFO: 2008-01-08 00:49:00 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2008-01-08 00:49:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2008-01-08 00:49:40 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
TRACE: 2008-01-08 00:50:11 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
INFO: 2008-01-08 00:53:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2008-01-08 00:54:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2008-01-08 00:54:40 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport3\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
TRACE: 2008-01-08 00:54:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
INFO: 2008-01-08 01:02:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2008-01-08 01:02:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2008-01-08 01:02:50 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
TRACE: 2008-01-08 01:03:11 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
INFO: 2008-01-08 01:09:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2008-01-08 01:09:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2008-01-08 01:09:51 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
TRACE: 2008-01-08 01:09:55 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
INFO: 2008-01-08 01:14:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
TRACE: 2008-01-08 01:14:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2008-01-08 01:14:18 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
TRACE: 2008-01-08 01:14:21 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
INFO: 2008-01-08 01:15:50 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2008-01-08 01:16:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2008-01-08 01:16:19 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
TRACE: 2008-01-08 01:16:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
INFO: 2008-01-08 01:17:55 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2008-01-08 01:18:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2008-01-08 01:18:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
TRACE: 2008-01-08 01:18:31 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
INFO: 2008-01-08 01:18:43 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
TRACE: 2008-01-08 01:18:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2008-01-08 01:18:48 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
TRACE: 2008-01-08 01:18:50 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
INFO: 2008-01-08 01:20:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
TRACE: 2008-01-08 01:20:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
INFO: 2008-01-08 01:20:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
TRACE: 2008-01-08 01:20:46 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
INFO: 2008-01-08 01:20:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
TRACE: 2008-01-08 01:21:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2008-01-08 01:21:22 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
TRACE: 2008-01-08 01:21:23 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
INFO: 2008-01-08 01:21:25 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2008-01-08 01:21:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is started.
TRACE: 2008-01-08 01:21:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER1' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER1.TSK MSS -l SAPUSER1.log
TRACE: 2008-01-08 01:21:52 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER1' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -loadprocedure fast
INFO: 2008-01-08 01:21:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is successfully completed.
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2008-01-08 01:22:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
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
INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2008-01-08 02:42:17
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2008-01-08 02:42:17
1 error(s) during processing of packages.
INFO: 2008-01-08 02:42:17
Import Monitor is stopped. -
ECC 6.0 Installation fails during Import ABAP Phase
Hi,
I am tryiing to install ECC 6.0 on windows 2003:Oracle and it is failing at phase 17 Import Abap with the following error:
ERROR 2007-11-13 16:04:09
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-11-13 16:04:09
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 .
here is the import_monitor.java.log file:
ava version "1.4.2_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_14-b05)
Java HotSpot(TM) Client VM (build 1.4.2_14-b05, mixed mode)
Import Monitor jobs: running 1, waiting 37, completed 0, failed 0, total 38.
Loading of 'SAPNTAB' import package: OK
Import Monitor jobs: running 0, waiting 37, completed 1, failed 0, total 38.
Import Monitor jobs: running 1, waiting 36, completed 1, failed 0, total 38.
Import Monitor jobs: running 2, waiting 35, completed 1, failed 0, total 38.
Import Monitor jobs: running 3, waiting 34, completed 1, failed 0, total 38.
Loading of 'SAPSSEXC_4' import package: OK
Import Monitor jobs: running 2, waiting 34, completed 2, failed 0, total 38.
Import Monitor jobs: running 3, waiting 33, completed 2, failed 0, total 38.
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 33, completed 3, failed 0, total 38.
Import Monitor jobs: running 3, waiting 32, completed 3, failed 0, total 38.
Loading of 'SAPAPPL2_1' import package: OK
Import Monitor jobs: running 2, waiting 32, completed 4, failed 0, total 38.
Import Monitor jobs: running 3, waiting 31, completed 4, failed 0, total 38.
Loading of 'SAPSSEXC_2' import package: OK
Import Monitor jobs: running 2, waiting 31, completed 5, failed 0, total 38.
Import Monitor jobs: running 3, waiting 30, completed 5, failed 0, total 38.
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 30, completed 6, failed 0, total 38.
Import Monitor jobs: running 3, waiting 29, completed 6, failed 0, total 38.
Loading of 'SAPAPPL1_1' import package: OK
Import Monitor jobs: running 2, waiting 29, completed 7, failed 0, total 38.
Import Monitor jobs: running 3, waiting 28, completed 7, failed 0, total 38.
Loading of 'SAPSSEXC_1' import package: OK
Import Monitor jobs: running 2, waiting 28, completed 8, failed 0, total 38.
Import Monitor jobs: running 3, waiting 27, completed 8, failed 0, total 38.
Loading of 'SAPAPPL0_3' import package: OK
Import Monitor jobs: running 2, waiting 27, completed 9, failed 0, total 38.
Import Monitor jobs: running 3, waiting 26, completed 9, failed 0, total 38.
Loading of 'SAPAPPL1_2' import package: OK
Import Monitor jobs: running 2, waiting 26, completed 10, failed 0, total 38.
Loading of 'SAPAPPL2_2' import package: OK
Import Monitor jobs: running 1, waiting 26, completed 11, failed 0, total 38.
Import Monitor jobs: running 2, waiting 25, completed 11, failed 0, total 38.
Import Monitor jobs: running 3, waiting 24, completed 11, failed 0, total 38.
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 12, failed 0, total 38.
Import Monitor jobs: running 3, waiting 23, completed 12, failed 0, total 38.
Loading of 'SAPAPPL0_1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 13, failed 0, total 38.
Import Monitor jobs: running 3, waiting 22, completed 13, failed 0, total 38.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 13, failed 1, total 38.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 13, failed 2, total 38.
Import Monitor jobs: running 2, waiting 21, completed 13, failed 2, total 38.
Import Monitor jobs: running 3, waiting 20, completed 13, failed 2, total 38.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 2, waiting 20, completed 13, failed 3, total 38.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 1, waiting 20, completed 13, failed 4, total 38.
Import Monitor jobs: running 2, waiting 19, completed 13, failed 4, total 38.
Import Monitor jobs: running 3, waiting 18, completed 13, failed 4, total 38.
Loading of 'FUPARAREF' import package: ERROR
Import Monitor jobs: running 2, waiting 18, completed 13, failed 5, total 38.
Import Monitor jobs: running 3, waiting 17, completed 13, failed 5, total 38.
Loading of 'TODIR' import package: ERROR
Import Monitor jobs: running 2, waiting 17, completed 13, failed 6, total 38.
Import Monitor jobs: running 3, waiting 16, completed 13, failed 6, total 38.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 13, failed 7, total 38.
Import Monitor jobs: running 3, waiting 15, completed 13, failed 7, total 38.
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 14, failed 7, total 38.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 1, waiting 15, completed 14, failed 8, total 38.
Loading of 'E071K' import package: ERROR
Import Monitor jobs: running 0, waiting 15, completed 14, failed 9, total 38.
Import Monitor jobs: running 1, waiting 14, completed 14, failed 9, total 38.
Import Monitor jobs: running 2, waiting 13, completed 14, failed 9, total 38.
Import Monitor jobs: running 3, waiting 12, completed 14, failed 9, total 38.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 15, failed 9, total 38.
Import Monitor jobs: running 3, waiting 11, completed 15, failed 9, total 38.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 11, completed 15, failed 10, total 38.
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 1, waiting 11, completed 16, failed 10, total 38.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 0, waiting 11, completed 17, failed 10, total 38.
Import Monitor jobs: running 1, waiting 10, completed 17, failed 10, total 38.
Import Monitor jobs: running 2, waiting 9, completed 17, failed 10, total 38.
Import Monitor jobs: running 3, waiting 8, completed 17, failed 10, total 38.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 8, completed 17, failed 11, total 38.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 1, waiting 8, completed 18, failed 11, total 38.
Import Monitor jobs: running 2, waiting 7, completed 18, failed 11, total 38.
Import Monitor jobs: running 3, waiting 6, completed 18, failed 11, total 38.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 2, waiting 6, completed 18, failed 12, total 38.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 6, completed 18, failed 13, total 38.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 0, waiting 6, completed 19, failed 13, total 38.
Import Monitor jobs: running 1, waiting 5, completed 19, failed 13, total 38.
Import Monitor jobs: running 2, waiting 4, completed 19, failed 13, total 38.
Import Monitor jobs: running 3, waiting 3, completed 19, failed 13, total 38.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 20, failed 13, total 38.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 1, waiting 3, completed 21, failed 13, total 38.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 0, waiting 3, completed 22, failed 13, total 38.
Import Monitor jobs: running 1, waiting 2, completed 22, failed 13, total 38.
Import Monitor jobs: running 2, waiting 1, completed 22, failed 13, total 38.
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 23, failed 13, total 38.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 24, failed 13, total 38.
here is a copy of import_monitor.log
INFO: 2007-11-13 14:02:09
Import Monitor is started.
CONFIG: 2007-11-13 14:02:09
Application options:
dbCodepage=4103
dbType=ORA
extFiles=yes
importDirs=C:\sapcds\inst_exp\exp1\EXP1;C:\sapcds\inst_exp\exp1\EXP2;C:\sapcds\inst_exp\exp1\EXP3;C:\sapcds\inst_exp\exp1\EXP4;C:\sapcds\inst_exp\exp1\EXP5;C:\sapcds\inst_exp\exp1\EXP6;C:\sapcds\inst_exp\exp2\EXP7;C:\sapcds\inst_exp\exp2\EXP8;C:\sapcds\inst_exp\exp2\EXP9;C:\sapcds\inst_exp\exp2\EXP10;C:\sapcds\inst_exp\exp2\EXP11
installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
jobNum=3
loadArgs= -stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-11-13 14:02:09
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-11-13 14:02:09
List of packages with views: 'SAPVIEW'.
TRACE: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
INFO: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2007-11-13 14:02:10
Data codepage 1100 is determined using TOC file 'C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.TOC' for package 'SAPSSEXC_3'.
INFO: 2007-11-13 14:02:12
Version table 'SVERS' is found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2007-11-13 14:02:12
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPNTAB' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPNTAB.TSK ORA -l SAPNTAB.log
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error
INFO: 2007-11-13 14:13:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is successfully completed.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_4' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_3.TSK ORA -l SAPSSEXC_3.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_4' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_4.TSK ORA -l SAPSSEXC_4.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DOKCLU' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP11\DATA\DOKCLU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DOKCLU.TSK ORA -l DOKCLU.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_4' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_4.cmd -dbcodepage 4103 -l SAPSSEXC_4.log -stop_on_error
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DOKCLU' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -l DOKCLU.log -stop_on_error
INFO: 2007-11-13 14:28:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_4' import package is successfully completed.
TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_2' import package is started.
TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_2.TSK ORA -l SAPSSEXC_2.log
TRACE: 2007-11-13 14:29:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_2.cmd -dbcodepage 4103 -l SAPSSEXC_2.log -stop_on_error
INFO: 2007-11-13 14:34:56 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is successfully completed.
TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_1' import package is started.
TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_1.TSK ORA -l SAPAPPL2_1.log
TRACE: 2007-11-13 14:35:12 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_1.cmd -dbcodepage 4103 -l SAPAPPL2_1.log -stop_on_error
INFO: 2007-11-13 15:02:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_1' import package is successfully completed.
TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_1' import package is started.
TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_1.TSK ORA -l SAPAPPL1_1.log
TRACE: 2007-11-13 15:02:43 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_1.cmd -dbcodepage 4103 -l SAPAPPL1_1.log -stop_on_error
INFO: 2007-11-13 15:08:06 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_2' import package is successfully completed.
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is started.
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DD03L' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\DD03L.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DD03L.TSK ORA -l DD03L.log
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DD03L' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
INFO: 2007-11-13 15:19:29 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is successfully completed.
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is started.
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_1.TSK ORA -l SAPSSEXC_1.log
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -stop_on_error
INFO: 2007-11-13 15:22:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_1' import package is successfully completed.
TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_2' import package is started.
TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_2.TSK ORA -l SAPAPPL2_2.log
TRACE: 2007-11-13 15:22:42 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_2.cmd -dbcodepage 4103 -l SAPAPPL2_2.log -stop_on_error
INFO: 2007-11-13 15:24:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is successfully completed.
TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_3' import package is started.
TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_3.TSK ORA -l SAPAPPL0_3.log
TRACE: 2007-11-13 15:24:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_3.cmd -dbcodepage 4103 -l SAPAPPL0_3.log -stop_on_error
INFO: 2007-11-13 15:34:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_3' import package is successfully completed.
TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_2' import package is started.
TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_2.TSK ORA -l SAPAPPL1_2.log
TRACE: 2007-11-13 15:34:41 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_2.cmd -dbcodepage 4103 -l SAPAPPL1_2.log -stop_on_error
INFO: 2007-11-13 15:45:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_2' import package is successfully completed.
INFO: 2007-11-13 15:46:06 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_2' import package is successfully completed.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_1' import package is started.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRSVALS' import package is started.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_1.TSK ORA -l SAPAPPL0_1.log
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SCPRSVALS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRSVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRSVALS.TSK ORA -l SCPRSVALS.log
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SCPRSVALS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRSVALS.cmd -dbcodepage 4103 -l SCPRSVALS.log -stop_on_error
TRACE: 2007-11-13 15:46:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_1.cmd -dbcodepage 4103 -l SAPAPPL0_1.log -stop_on_error
INFO: 2007-11-13 15:51:35 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRSVALS' import package is successfully completed.
TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_3' import package is started.
TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_3.TSK ORA -l SAPAPPL2_3.log
TRACE: 2007-11-13 15:51:41 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error
INFO: 2007-11-13 15:56:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_1' import package is successfully completed.
TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_2' import package is started.
TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_2.TSK ORA -l SAPAPPL0_2.log
TRACE: 2007-11-13 15:56:43 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
ERROR: 2007-11-13 15:56:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_3' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL2_3.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: 2007-11-13 15:56:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC_3.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
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_5' import package is started.
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_5' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_5.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_5.TSK ORA -l SAPSSEXC_5.log
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDIC.TSK ORA -l SAPSDIC.log
TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_5' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error
TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_5' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC_5.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: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_2' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0_2.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
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
Loading of 'FUPARAREF' import package is started.
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
Loading of 'TODIR' import package is started.
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'FUPARAREF' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\FUPARAREF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" FUPARAREF.TSK ORA -l FUPARAREF.log
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'TODIR' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\TODIR.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" TODIR.TSK ORA -l TODIR.log
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'TODIR' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'FUPARAREF' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error
ERROR: 2007-11-13 15:57:40 com.sap.inst.migmon.LoadTask run
Loading of 'FUPARAREF' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error' exited with return code 2.
For mode details see 'FUPARAREF.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
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSRC.TSK ORA -l SAPSSRC.log
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
ERROR: 2007-11-13 15:58:10 com.sap.inst.migmon.LoadTask run
Loading of 'TODIR' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error' exited with return code 2.
For mode details see 'TODIR.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
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is started.
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SEOSUBCODF' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SEOSUBCODF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SEOSUBCODF.TSK ORA -l SEOSUBCODF.log
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SEOSUBCODF' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SEOSUBCODF.cmd -dbcodepage 4103 -l SEOSUBCODF.log -stop_on_error
ERROR: 2007-11-13 15:58:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error' 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
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask run
Loading of 'E071K' import package is started.
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'E071K' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\E071K.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" E071K.TSK ORA -l E071K.log
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'E071K' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error
INFO: 2007-11-13 16:00:13 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is successfully completed.
ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSRC.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: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
Loading of 'E071K' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error' exited with return code 2.
For mode details see 'E071K.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
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRVALS' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SCPRVALS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRVALS.TSK ORA -l SCPRVALS.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPPOOL.TSK ORA -l SAPPOOL.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP5\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSPROT.TSK ORA -l SAPSPROT.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SCPRVALS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRVALS.cmd -dbcodepage 4103 -l SCPRVALS.log -stop_on_error
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
INFO: 2007-11-13 16:01:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP4\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDOCU.TSK ORA -l SAPSDOCU.log
TRACE: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
ERROR: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error' exited with return code 2.
For mode details see 'SAPPOOL.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
INFO: 2007-11-13 16:01:57 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRVALS' import package is successfully completed.
INFO: 2007-11-13 16:02:01 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_4' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLEXC.TSK ORA -l SAPSLEXC.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPCLUST.TSK ORA -l SAPCLUST.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_4' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_4.TSK ORA -l SAPAPPL0_4.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
TRACE: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_4' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error
ERROR: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSLEXC.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
INFO: 2007-11-13 16:02:23 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLOAD.TSK ORA -l SAPSLOAD.log
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER.TSK ORA -l SAPUSER.log
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error
ERROR: 2007-11-13 16:02:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_4' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0_4.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: 2007-11-13 16:02:41 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error' exited with return code 2.
For mode details see 'SAPUSER.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
INFO: 2007-11-13 16:02:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDDIM.TSK ORA -l SAPDDIM.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDFACT.TSK ORA -l SAPDFACT.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDODS.TSK ORA -l SAPDODS.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
INFO: 2007-11-13 16:03:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is started.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAP0000.TSK ORA -l SAP0000.log -o D
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER1.TSK ORA -l SAPUSER1.log
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -stop_on_error
INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is successfully completed.
INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
WARNING: 2007-11-13 16:04:09
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-11-13 16:04:09
13 error(s) during processing of packages.
INFO: 2007-11-13 16:04:09
Import Monitor is stopped.
how can i resolve these errors?Hi,
Here are the logs of the jobs that are failing to complete. i am selecting the recommended which is unicode
SAPALLP2_3.log
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TN02Q" ( "MANDT" VARCHAR2(9) DEFAULT '000' NOT NULL , "EINRI" VARCHAR2(12) DEFAULT ' ' NOT NULL , "ANWEN" VARCHAR2(12) DEFAULT ' ' NOT NULL , "PARNA" VARCHAR2(30) DEFAULT ' ' NOT NULL , "PARWE" VARCHAR2(45) DEFAULT ' ' NOT NULL , "COMMT" VARCHAR2(90) DEFAULT ' ' NOT NULL ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155648
SAPSSEXC_3.log
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: REPOSRC created #20071113141340
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "REPOSRC"
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155650
SAPSSEXC_5.log
DbSl Trace: Failed to register client info: orc=604
DbSl Trace: ORA-604 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TFTIT" ( "SPRAS" VARCHAR2(3) DEFAULT ' ' NOT NULL , "FUNCNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "STEXT" VARCHAR2(222) DEFAULT ' ' NOT NULL ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 34164981 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select name,password,datats#...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711
SAPAPPL0_2.log
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=41)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "ECRM_REPL_KEY~0" ON "ECRM_REPL_KEY" ( "MANDT", "ISUPRODLOG", "OBJNUM" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select con#,obj#,rcon#,enabl...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711 -
ABAP Dump ASSIGN LENGTH 0 SAPLSNR3 LOCAL Buffer - BI content installation
Hi all,
I get the following ABAP dump while installing the BI content and choosing the grouping ' in dataflow before' in Bi 7.0 SP 13
Short text
Program error: ASSIGN with length 0 in program "SAPLSNR3".
Error analysis
In an ASSIGN statement in the program "SAPLSNR3" a field symbol with
length 0 should have been created. However, this is not possible.
length 0. This is not possible s
Trigger Location of Runtime Error
Program SAPLSNR3
Include LSNR3F01
Row 178
Module type (FORM)
Module Name LOCAL_BUFFER
How to correct the error
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ASSIGN_LENGTH_0" " "
"SAPLSNR3" or "LSNR3F01"
"LOCAL_BUFFER"
I did search for the same error discussion in the forum. However most of them are dealing with "LOCAL_ENTRY_EXISTS" while this dump is related to "LOCAL_BUFFER".
Kindly let me know if anyone has similar issue and got it resolved.
Thanks in advance
KeeFor anyone who come across the same error - here is the solution.
Assign the number ranges for objects
BI_TS , BI_TSDTEL, BI_TSDOMA and BI_CS in tcode SNUM as below
No. From Number To Number Currenct Number
01 0000000001 9999999999 1
You can surpass this error.
Thanks
Kee -
SAP NW7.0 SR3 Java AddIn Installation failed at "Import Java dump"
Dear all,
I get an error at Java AddIn Installation SAP Netweaver 7.0 SR3
(Software Life-Cycle Option -> Java Add-In for ABAP -> Oracle ->
Central System ->)
The first installation step "Central Services Instance (SCS) Java Add-
In" I have installed it without errors.
The Installation failed at 2nd step "Database Instance Java Add-In" at phase 11
of 14 "Import java dump":
26.05.09 15:16:46 com.sap.inst.jload.Jload main
INFO: Jload -sec
Q2B,jdbc/pool/Q2B,/usr/sap/Q2B/SYS/global/security/data/SecStore.properties,/usr/sap/Q2B/SYS/global/security/
data/SecStore.key -
dataDir /usr/sap/swdc/51033513/DATA_UNITS/JAVA_EXPORT_JDMP -
job /tmp/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN
/ORA/CENTRAL/DB/IMPORT.XML -log jload.log
26.05.09 15:16:47 com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
26.05.09 15:16:47 com.sap.inst.jload.Jload logStackTrace
SEVERE: java.sql.SQLException: Io exception: The Network Adapter could
not establish the connection
at oracle.jdbc.driver.DatabaseError.throwSqlException
(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException
(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException
(DatabaseError.java:255)
at oracle.jdbc.driver.T4CConnection.logon
(T4CConnection.java:387)
at oracle.jdbc.driver.PhysicalConnection.<init>
(PhysicalConnection.java:420)
at oracle.jdbc.driver.T4CConnection.<init>
(T4CConnection.java:165)
at oracle.jdbc.driver.T4CDriverExtension.getConnection
(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect
(OracleDriver.java:801)
at
com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection
(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection
(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection
(OpenSQLDataSourceImpl.java:276)
at com.sap.inst.jload.db.DBConnection.connectViaSecureStore
(DBConnection.java:105)
at com.sap.inst.jload.db.DBConnection.connect
(DBConnection.java:149)
at com.sap.inst.jload.Jload.main(Jload.java:580)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main
(OfflineToolStart.java:81)
the database is up and running, the Oracle Listener is also working well.
Any idea??
Thanks so much in advance!
Best Regards,
GerdHi Sunny, hi Markus!
many thanks for your hints!
I've just solved the problem. The problem was, our Listener was not configured correctly.
I've adjusted the listener.ora, tnsnames.ora to the correct hostname - cause, we had a hostname-switch last month and I had forgotten to adapt the Listener...
now the Listener is running as well:
mcho35au:oraq2b 120% lsnrctl status LISTENER_Q2B
LSNRCTL for Solaris: Version 10.2.0.4.0 - Production on 30-MAY-2009
09:52:48
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=Q2B.WORLD))
STATUS of the LISTENER
Alias LISTENER_Q2B
Version TNSLSNR for Solaris: Version 10.2.0.4.0 -
Production
Start Date 30-MAY-2009 09:52:15
Uptime 0 days 0 hr. 0 min. 32 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/Q2B/102_64/network/admin/listener.ora
Listener Log
File /oracle/Q2B/102_64/network/log/listener_q2b.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=Q2B.WORLD)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=Q2B)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mcho35au)(PORT=1527)))
Services Summary...
Service "Q2B" has 1 instance(s).
Instance "Q2B", status UNKNOWN, has 1 handler(s) for this service...
Service "Q2B.WORLD" has 1 instance(s).
Instance "Q2B", status READY, has 1 handler(s) for this service...
Service "Q2B_XPT.WORLD" has 1 instance(s).
Instance "Q2B", status READY, has 1 handler(s) for this service...
The command completed successfully
meanwhile the step "Import java dump" has finished successfully!
Thanks to all!
Best Regards,
Gerd
Edited by: Gerd Schuster on May 30, 2009 10:29 AM -
Installation "failed" on return to first install DVD
I installed the entire Logic 9 upgrade on my Macbook Pro and all the disks were read in and installed without issues. The entire installation took over 2 hours with no error messages during that time.
After all the disks were read and installed, I inserted the first Installation DVD again as the installer requested and the installer suddenly gave me an exclamation point in a triangle with the following message:
"The installation failed. The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance."
Logic 9, Mainstage 2and Soundtrack Pro 3 all load and work, and the samples and loops seem to be there, but I'm not sure if anything is missing. All the disks seem to have loaded without issues so I'm really stumped as to why I got that message.
Is there an install log that I could read to find out what happened? And should I wait to figure out what went wrong before I update to the latest version?
Thanks.I just upgraded on my MacPro yesterday (ran the upgrade on my MacBook Pro months ago with no issues) and got the same message - most of the additional content installed, but instead of asking for the Jam Pack content 3 disk, it asked for the Logic install disk. And then I got the same message - installation failed.
All of the programs work, the content seems to be there... just an odd thing to happen. Like you, I'd like to know if something is missing... but I guess I'll find out the hard way, as nobody has bothered to answer this thread. -
Error during installation of SAP Netweaver 7.01 ABAP Trial Version
Hello everyone,
i tried to install 'SAP Netweaver 7.01 ABAP Trial Version' on my laptop using an VMWare Server.
My used operating system on my VMWare Server is 'Windows Server 2003 Enterprise Edition'.
I´ve executed within the folder D:...SAPNetWeaver701SAPNW7.01ABAPTrialimageSetup.exe
and entered all necessary informations to start the installation.
More or less 30mins. later i got the following message from the system:
'An error occurred and product installation failed. Look at the log file E:sapdbNSPlog.txt for details.'
The log text show the following information:
Line: -
(Dec 25, 2009 1:53:43 PM), Install, com.sap.installshield.maxdb.maxdb_call_sdbinst, err, An error occurred and product installation failed. Look at the log file E:sapdbNSPlog.txt for details.
(Dec 25, 2009 1:53:43 PM), Install, com.sap.installshield.maxdb.maxdb_call_sdbinst, err, ProductException: (error code = 601; message="An Error happened during call of MaxDB Tool sdbinst. Check end of Logfile C:/DOCUME1/ADMINI1/LOCALS~1/Temp/MaxDBSAPNWPREV.log")
STACK_TRACE: 22
ProductException: (error code = 601; message="An Error happened during call of MaxDB Tool sdbinst. Check end of Logfile C:/DOCUME1/ADMINI1/LOCALS~1/Temp/MaxDBSAPNWPREV.log")
at com.sap.installshield.maxdb.maxdb_call_sdbinst.install(maxdb_call_sdbinst.java:193)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installProduct(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.installshield.wizard.service.LocalImplementorProxy.invoke(Unknown Source)
at com.installshield.wizard.service.AbstractService.invokeImpl(Unknown Source)
at com.installshield.product.service.product.GenericProductService.installProduct(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installAssembly(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl.access$900(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Line: -
Can anyone help me with this??? I have no ideas how to solve this problem.
Thank you very much.Check end of Logfile C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/MaxDBSAPNWPREV.log
have you checked that log? -
Database Error during installation of SAP NetWeaver 7.01 ABAP Trial Version
Hi All,
I was installing the SAP NetWeaver 7.01 ABAP Trial Version but during the installation i got some MaxDB error.
Log.txt
(Apr 28, 2010 10:13:41 PM), Install, com.sap.installshield.maxdb.maxdb_call_sdbinst, err, An error occurred and product installation failed. Look at the log file F:\sapdb\NSP\log.txt for details.
(Apr 28, 2010 10:13:41 PM), Install, com.sap.installshield.maxdb.maxdb_call_sdbinst, err, ProductException: (error code = 601; message="An Error happened during call of MaxDB Tool sdbinst. Check end of Logfile C:/DOCUME1/ASHISH/LOCALS1/Temp/MaxDBSAPNWPREV.log")
STACK_TRACE: 22
ProductException: (error code = 601; message="An Error happened during call of MaxDB Tool sdbinst. Check end of Logfile C:/DOCUME1/ASHISH/LOCALS1/Temp/MaxDBSAPNWPREV.log")
at com.sap.installshield.maxdb.maxdb_call_sdbinst.install(maxdb_call_sdbinst.java:193)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installProduct(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.installshield.wizard.service.LocalImplementorProxy.invoke(Unknown Source)
at com.installshield.wizard.service.AbstractService.invokeImpl(Unknown Source)
at com.installshield.product.service.product.GenericProductService.installProduct(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installAssembly(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl.access$900(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)Hi,
In environment variables under system variables see if the path to java has been set,
JAVA_Home
C:\j2sdk1.4.2_11
JRE_PATH
C:\Program Files\Java\j2re1.4.2_11\bin\java.exe
Both these variables should be set.
The values would differ on the version of java that you are using and the
path where you have java installed.
I suggest you go with Java version 1.4.2_*.
Regards,
Vishnu -
Attempted to update the flash on my 15" Retina Macbook Pro running OS X 10.10 today, only to get the error "installation failed" which provides me a link to a support page. After extensive research on Adobe forums, I followed several pieces of advice for a fix with no avail. For example:
I uninstalled the flash version I currently had, restarted my computer and attempted a new clean install as suggested by Adobe. Did not work.
I've attempted to run an install using that backdoor method of "show package contents" and installing from there. Same error occurs.
I've downloaded the .dmg file a few times incase I had something wrong with the download. I've restarted computer multiple times. Still nothing. Now I don't even have the previous version of flash installed on the computer, because the previous advice was to uninstall it altogether.
Any new suggestions out there?Hi radiatedesign
Thank you for providing the screenshot it is as it does confirm you and OP sarahrannals are having the same error.
To address your other comment, by posting 'same thing' and not providing the previously requested information slows down our ability to assist you, as your issue may or may not be the same as the OP. Many people post "same thing" but it usually turns out that their issue is not be the same thing as the OP For example, in this thread, melinda_o said she had the same problem as OP sarahrannals, but the offline installer worked for melinda_0, and is not workging for sarahrannals, and probably won't work for you either, therefore, melinda_o did not have the "same issue" as sarahrannals. This is the reason for asking for the information, to verify if it was indeed the same issue.
sarahrannals and radiatedesign
Unfortunately, the FlashPlayerInstallManager.log file didn't provide information on the failure. This usually indicates a permissions issue in the filesystem. Repairing the filesystem and filesystem permissions may resolve this. Please see the section on First Aid in this Apple tech note, Resolve startup issues and perform disk maintenance with Disk Utility and fsck - Apple Support. Run both Verify and Repair Filesystem and Verify and Repair Disk Permissions. Sometimes the verify step will return clean, but the repair step will fix some things.
After completing the above. Delete all Flash Player installers you may have downloaded and download a new installer again from https://get.adobe.com/flashplayer. I recommend clearing the browsers cache first to make sure a previously cached installer is not downloaded again.
Maria -
Windows Server 2008 R2 Service Pack 1 installation failed with error code 0x800f0a12
Hello,
I'm facing problem to install windows server 2008 R2 SP1. I cannot install SP1. In this server have running Exchange 2010 server. to update Win2008 R2 SP1 facing the following error:
1. Service Pack installation failed with error code 0x800f0a12.
2. Installation Failure: Windows failed to install the following update with error 0x80070643: Windows Server 2008 R2 Service Pack 1 for x64-based Systems (KB976932).
Please suggestPlease run the system update readiness tool.
http://windows.microsoft.com/en-us/windows7/What-is-the-System-Update-Readiness-Tool?SignedIn=1
Then post the complete contents of;
%SYSTEMROOT%\Logs\CBS\CheckSUR.log
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012
Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
log file:
===============
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801
Maybe you are looking for
-
Error importing external files in flash cs6
I am getting this error message when I try to import image files into my flash CS6 animation: "Unable to load external importer C:\Program Files\Adobe\Adobe Flash CS6\es_ES\Configuration\Importers\PhotoshopReader.dll". I am using Windows XP SP3. Than
-
Slides play out of order on Apple TV
My sides are in a fixed order in my windows file. When they play on Apple TV through Home share, they are in some random order. Several others have had this problem. Is there a solution?
-
M2t files show wrong aspect ratio in Bridge CS5
We're using Bridge CS5 version 4.02.1 running on a Vista 64bit machine. Our m2t files appear in Bridge as a 4:3 aspect ratio, when they should show 16:9. They import correctly into PProCS5. Our MOV files show correctly in both Bridge & PPro. Why
-
Logic pro 9 in Mavericks CPU spikes to red
Ok, I was running logic pro 9 in OSX 10.7.5 and my project was running fine. I never once noticed the CPU levels spiking into the red.] I upgraded to Mavericks and now 2 of the CPU's are constantly in the red! It is the same in 32 bit or 64 bit mode.
-
Help us to choose [ we want to purchase] Adobe Media server 5 version like professional or standard etc. Our requirement are : 1) video streaming for existing website through RTMP protocol Both on-demand & live streaming 2) video streaming for new IO