cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

installation error in netweaver

Former Member

on ‎2011 Feb 03 9:25 AM

0 Kudos
61

Hi,

I am now installation netweaver 7.10 in windows2003 64bit platform.

here in abap import phase i am facing an error. in 18 import jobs 15 has been completed and 3 failed.

So kindly me to resolve this issue.pre requisite checks has been cmpltd successfully.

here i have pasted the error log which i copied from sapinst log.

showDialog()

FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .

TRACE iaxxgenimp.cpp:719

showDialog()

<html><head></head><body>

An error occurred while processing service SAP NetWeaver 2004s Support Release 2 > SAP Systems > Oracle > Central System > Central System Installation. You may now

  • press Retry to repeat the current step.

  • press the View Log button to get more information about the error.

  • stop the task and continue with it later.

Log files are written to C:\Program Files (x86)/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.

</body></html>

Pls help me in this regards,

Thanks in Advance,

Prathap G

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (2)

Answers (2)

lakshminarayanan_m
Contributor
‎2011 Feb 03 1:09 PM
0 Kudos

HI,

Wat type installation u r doing.

Please give the detail with latest available log infro

Regards

Lakshminarayanan

Show replies
Show replies
JPReyes
Active Contributor
‎2011 Feb 03 9:37 AM
0 Kudos 
Log files are written to C:\Program Files (x86)/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS

Theres no info here to help you... Statement above tells you where the log files are, did you read them?

Please read the "Rules of Engagement"

Regards

Juan

Show replies
Show replies
Former Member
‎2011 Feb 03 9:43 AM
0 Kudos

Paste the latest content of sapinst_dev.log file from the installation directory.

Former Member
‎2011 Feb 03 9:53 AM
0 Kudos

/NWM_JSP_700900_LINUX_DE'/'sap.com'/'SAP AG'/'7.0009.20060824164022.0000'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc/mobile/piprintpb20_ppc03_xsc_crm_1_1_1'/'sap.com'/'SAP AG'/'7.0009.20060824164022.0000'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc/mobile/NWM_JSP_700900_WIN32_uncomp'/'sap.com'/'SAP AG'/'7.0009.20060824164022.0000'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc/mobile/connector_ppc03_xsc_crm_1_1_4'/'sap.com'/'SAP AG'/'7.0009.20060824164022.0000'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc/mobile/piscint740a3_ppc03_xsc_crm_1_1_3'/'sap.com'/'SAP AG'/'7.0009.20060824164022.0000'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc/SL/CMS/tsawebui'/'sap.com'/'MAIN_APL70VAL_C'/'937076'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc.CBS.CommonPart'/'sap.com'/'MAIN_APL70VAL_C'/'936886'/'0' will be deployed.Info: Initial deployment: Selected development component 'tc/mobile/NWM_JSP_700900_WINCE_uncomp'/'sap.com'/'SAP AG'/'7.0009.20060824164022.0000'/'0' will be deployed.Info: Ending deployment prerequisites. All items are correct.Info: Saved current Engine state.Info: Starting: Initial deployment: Selected development component 'tc.CBS.DBDefs'/'sap.com'/'MAIN_APL70VAL_C'/'936576'/'0' will be deployed.Info: Creating connections to database "ECC".Info: Creating vendor connection to database.Info: Vendor connection created successfully.Info: Creating openSQL connection to database.Info: OpenSQL connection created successfully.1:57:52 2025-10-07 dbs-Info: $Id: //tc/DictionaryDatabase/645_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $1:57:52 2011-02-03 dbs-Info: <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>1:57:52 2011-02-03 dbs-Info: <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>1:57:52 2011-02-03 dbs-Info: 1:57:52 2011-02-03 dbs-Info: 1:57:52 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBRTH >>>1:57:52 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBRTH >>>1:57:52 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:52 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:53 2011-02-03 dbs-Info: No action required for table 1:57:53 2011-02-03 dbs-Info: No action required for table 1:57:53 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBTABLERT >>>1:57:53 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBTABLERT >>>1:57:53 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:53 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:53 2011-02-03 dbs-Info: No action required for table 1:57:53 2011-02-03 dbs-Info: No action required for table 1:57:53 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBRTH >>>1:57:53 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBRTH >>>1:57:53 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:53 2025-10-07 dbs-Info: predefined action is: >>>null<<<1:57:53 2011-02-03 dbs-Info: No action required for table 1:57:53 2011-02-03 dbs-Info: No action required for table 1:57:53 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBRTX >>>1:57:53 2011-02-03 dbs-Info: <<< Analyze table BC_DDDBRTX >>>1:57:53 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:53 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:54 2011-02-03 dbs-Info: No action required for table 1:57:54 2011-02-03 dbs-Info: No action required for table 1:57:54 2011-02-03 dbs-Info: >>> Analyze tables from archive in database ORACLE1:57:54 2011-02-03 dbs-Info: >>> Analyze tables from archive in database ORACLE1:57:54 2011-02-03 dbs-Info: Next archive object : dbtables/CBS_ACCESSQUEUE.gdbtable1:57:54 2011-02-03 dbs-Info: Next archive object : dbtables/CBS_ACCESSQUEUE.gdbtable1:57:54 2011-02-03 dbs-Info: <<< Analyze table CBS_ACCESSQUEUE >>>1:57:54 2011-02-03 dbs-Info: <<< Analyze table CBS_ACCESSQUEUE >>>1:57:54 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:54 2011-02-03 dbs-Info: predefined action is: >>>null<<<1:57:54 2011-02-03 dbs-Info: Table CBS_ACCESSQUEUE not found on DB1:57:54 2011-02-03 dbs-Info: Table CBS_ACCESSQUEUE not found on DB1:57:56 2011-02-03 dbs-Info: Action: CREATE1:57:56 2011-02-03 dbs-Info: Action: CREATE1:57:56 2011-02-03 dbs-Info: CREATE TABLE "CBS_ACCESSQUEUE"("SEQNO" NUMBER(19) NOT NULL, "BSID" NUMBER(10) NOT NULL, "NODEID" NUMBER(10) NOT NULL, "REQUESTID" NUMBER(19) NOT NULL, "ACCESSTYPE" NUMBER(5) DEFAULT 0 NOT NULL, "RESTRICTIONID" NUMBER(5) DEFAULT 0 NOT NULL) CREATE INDEX "CBS_AQ_BSID_RESID" ON "CBS_ACCESSQUEUE"("BSID", "RESTRICTIONID") ALTER TABLE "CBS_ACCESSQUEUE" ADD PRIMARY KEY ("SEQNO", "BSID") NOT DEFERRABLE INITIALLY IMMEDIATE ENABLE VALIDATE

WARNING 2011-02-03 02:08:32

SDM call of deploySdaList ends with returncode 4. See output of logfile C:\PROGRA1\SAPINS1\NW04S\SYSTEM\ORA\CENTRAL\AS\callSdmViaSapinst.log.

INFO 2011-02-03 02:08:32

Copied file 'C:/Program Files/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log' to 'C:/PROGRA1/SAPINS1/NW04S/SYSTEM/ORA/CENTRAL/AS/UsageTypesDeployment.log'.

ERROR 2011-02-03 02:08:32

CJS-30156 SDM deployment failed for at least one of the components to deploy.<br> SOLUTION: Check 'C:/PROGRA1/SAPINS1/NW04S/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log' for more information.

ERROR 2011-02-03 02:08:32

FCO-00011 The step enableUsageTypes with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|enableUsageTypes was executed with status ERROR .

Former Member
‎2011 Feb 03 12:48 PM
0 Kudos

paste the log callSdmViaSapinst.log also

Ask a Question