Support package update error
Dear all,
I am currently update my system.
The current version is ECC6 EHP7 based on NW7.4
SAP_BASIS 740 0002
SAP_ABA 740 0002
I would like to upgrade to SPS level 5
We use DB2 LUW 10.5
In the update phase, we encountered an error message:
SQL-error "-203-SQL0203N A reference to column "TABNAME" is ambiguou
2EETP345 s. SQLSTATE=42702" in DDL statement for "V_DSH_TF_DETAIL
As I can see in the log file, error messages are as below
===========================
3 ETP399 "SHPOSITION", DD30L."AUTOSUGGEST" AS "AUTOSUGGEST" FROM "DD31S"
3 ETP399 INNER JOIN "DD30L" ON "SHLPNAME" = "SUBSHLP" WHERE "AS4LOCAL" =
3 ETP399 'A' AND "AS4LOCAL" = 'A' AND "HIDEFLAG" = ' ' AND "AUTOSUGGEST" = 'X'
3 ETP399
2WETP000 06:42:38: Retcode 1: error in DDL statement for "V_DSH_ASSIGNED " - repeat
2EETP345 06:42:50: Retcode 1: SQL-error "-203-SQL0203N A reference to column "SHLPNAME" is ambiguo
2EETP345 us. SQLSTATE=42702" in DDL statement for "V_DSH_ASSIGNED "
2 ETP399 --------------- DB-ROLLBACK() ---------------
2EETP334 06:42:50: error in DDL, nametab for "V_DSH_ASSIGNED" not activated
3 ETP379X06:42:50: activating Nametab "V_DSH_TF_DETAIL":
3 ETP355Xstatements:
3 ETP399 CREATE VIEW "V_DSH_TF_DETAIL" AS SELECT DD02L."TABNAME" AS
3 ETP399 "TABNAME", DD03L."FIELDNAME" AS "FIELDNAME", DD02L."TABCLASS" AS
3 ETP399 "TABCLASS", DD03L."SHLPORIGIN" AS "SHLPORIGIN" FROM "DD02L" INNER
3 ETP399 JOIN "DD03L" ON "TABNAME" = "TABNAME" WHERE "AS4LOCAL" = 'A' AND
3 ETP399 "AS4LOCAL" = 'A'
3 ETP399
2WETP000 06:42:50: Retcode 1: error in DDL statement for "V_DSH_TF_DETAIL " - repeat
2EETP345 06:43:02: Retcode 1: SQL-error "-203-SQL0203N A reference to column "TABNAME" is ambiguou
2EETP345 s. SQLSTATE=42702" in DDL statement for "V_DSH_TF_DETAIL "
2 ETP399 --------------- DB-ROLLBACK() ---------------
2EETP334 06:43:02: error in DDL, nametab for "V_DSH_TF_DETAIL" not activated
2 ETP301 ----------------------------------------------------------------------
3 ETP361 "0" Shadow-Nametabs activated, DDL executed
2 ETP362 "2" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2014/03/19 06:42:38")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2014/03/19 06:43:02")
2 ETP301 ----------------------------------------------------------------------
2 ETP301 ----------------------------------------------------------------------
2 ETP364 Begin: Act. of Shadow-Nametabs ("2014/03/19 06:43:02")
2 ETP301 ----------------------------------------------------------------------
2 ETP301 ----------------------------------------------------------------------
2 ETP338XTouch Load of nametabs
===========================
I have checked another system which is also ehp7 based on NW740 0005, the view "V_DSH_TF_DETAIL" totally doesn't exist, but that is oracle database, here in my case is DB2 database, I have searched for SAP OSS but seems no sap notes for it.
Do you have any idea how to solve this problem? Big thanks!
Best regards,
Fresh man
Hi Ashutosh,
Many thanks for your reply, yes this definitely solve my problem.
But I feel quite confused what's the real reason.
Several weeks ago, I update a system (EHP7+Oracle) from 74002 to 74005, with SUM, no such problem, however this time, its EHP7+DB2 10.5, from 74002 to 74004, with SPAM, met this kind of problem...
The support packages are totally the same...
is it because I should upgrade from 02 to 05 directly? 04 has problem?
or I should update with SUM instead of SPAM?
or it is because of DB2??
or I should involve other packages like something like ST into the update queue?
Best regards,
Fresh
Similar Messages
-
Problem with Support Package SAP_BASIS (Error Stop) IMPORT_PROPER
Hi Everyone,
i want to apply Support Pack for SAP_BASIS. Now Its Level is 0009 (ECC 6.0).
i did import the SPs SAPKB70010 and SAPKB70011. We only want until Stack 11.
The test scenario was without an error. But during the Standard scenario there occurred a problem:
SPAM Status: Error Stop
Import Phase: IMPORT_PROPER
I guess there are different reasons:
1) We didn´t make a SPAM update before! it´s still version 7.00/0021.
2) I have no idea if the guy before me made a kernel update.
And now i wanted to update SPAM to version 27. but first i should "repair" this problem because the SAP_BASIS is still in the queue.
Is there a possibility to delete the queue, update SPAM and the Kernel and then try it again with this support package?
We cannot go further than Stack 11!
please help me!Hi,
This is not because of SPAM version nor the upgrade of kernal.If that was a SPAM problem then it will
not allow you to define the queue.
There are some know problems with this basis patches please read the note .Just run the import again this error would not occur.
If this error occurs then post the import logs for further analysis.
Regards,
Vamshi. -
While Import support package getting error in R/3
Hi All,
I am getting one error following error while importing support package in R/3.
Open data extraction requests
The system has found a number of open data extraction requests.These should be processed before starting the object import process, as changes to DDIC structures could prevent data extraction requests from being read after the import, thus causing them to terminate. Call the Customizing Cockpit data extraction transaction and process all open extraction requests.
Can Anybody aware of this error. How do I delete the open data extraction process specified here.
Thx & Regds,
SGKHi,
I think I have to stop extraction process in LBWE or R/3. Can anybody tell me how to stop extraction process.
Thx & Regds,
SGK -
SOLUTION MANGER SUPPORT PACKAGES CRTs ERROR
Hi all..
System status: solution manager 4.0/MS SQL/Windows 2003/kernel-159/sapm 027/700/tp version:372.04.29
When i am applying basis and abap patches(11) then i am getting CRTs error.
the error message is-
The import was stopped, since an error occurred during the phase
ADDON_CONFLICTS_?, which the Support Package Manager is unable to
resolve without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem
- Error in phase: ADDON_CONFLICTS_?
- Reason for error: TP_CANNOT_CONNECT_SYSTEM
- Return code:
- Error message: TP_INTERFACE_FAILURE
how can I remove this error? please help me urgently.
thanks
NANIHi,
You have to add extra addon (CRT) support pack with SAP Basis support pack. It is necessary for solution manager.
Please can you tell me which support pack you are installing and what is your system version. (e.g SAP ECC 6.0 or SAP R/3 4.7 etc) -
Support Package Import Error in ECC 6.0 SR2
Hi,
We tried to upgrade EA-GLTRADE in our ECC 6.0 SR 2 system with
SAPKGPGD07 patch during which, we encounter with some error at
DDIC_ACTIVATION. (Attached: Entire Log)
Note:
We have already updated the Kernal with latest patch and SPAM with
latest version 7.00/0023.
We also applied dependency patches for SAPKGPGD07.
Please give us the steps to resolve it or to reset the Queue so that
atleast we can continue with other patches
Thanks,
Vignesh P,
Log from Log File:
ides\sapmnt\trans\log\SAPAGPGD07.I01
Log File:
ides\sapmnt\trans\log\SAPAGPGD07.I01
ABAP Dictionary: Activation
Transport request : SAPKGPGD07
 System : I01
tp path : tp
Version and release: 370.01.01 700
3T Program start============================================================
Mass Activation
=========================================================================
 Process..................: ides_9
User.....................: DDIC
Date, time...............: 20.04.2007, 17:14:35
Platform.................: CUSTOMER-I01(700)/MSSQL/WindowsNT/ides
Tool.....................: BATCH/RADMASG0
Log......................: F,
ides\sapmnt\trans\tmp\SAPAGPGD07.I01
Program parameters:
Input Medium...............: Transp. Request SAPKGPGD07
Activation Method..........: Inactv.
Chk Mode...................: T
Version to be activated....: M
Versions to be deleted.....: Delete Only Active Versions
Lock Against Paral. Exec...: Shared
Independent Statistics Log.: being written
Parallel Mode..............: Switched on
..Resources................: 50% of Dialog Processes, Maximum 4 Processes
.Costs for Each Task.......: Minimum: 3.000, Maximum: 150.000
=========================================================================
Number of objects to be analyzed: 121
Number of relevant dependencies: 108
Level 1:42 objects assigned, 52 less dependencies
Level 2:34 objects assigned, 35 less dependencies
Level 3:27 objects assigned, 10 less dependencies
Level 4:7 objects assigned, 7 less dependencies
Level 5:7 objects assigned, 4 less dependencies
Level 6:4 objects assigned, 0 less dependencies
Graph_Analysis: 121 objects on 6 topological levels
Start phase 001 **********************************************************
Object Activation
3T *** Activate objects at level 1
Parallel execution with maximal 3 concurrent tasks *
Total of 42 objects with 28.630 costs in 8 tasks
3T Activate data element WB2_DEFAULT_TEW
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activate data element WB2_FIELD
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activate data element WB2_KBETR_BAPI
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activate data element WB2_KBETR_SCALE_BAPI
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activate data element WB2_KOMXWRT_BAPI
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activate data element WB2_KSTBW_SCALE_BAPI
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activate data element WB2_ORDER_KEY
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Activate table BAPITCCOND
Table BAPITCCOND was activated successfully
Activate table BAPITCCONDCX
Table BAPITCCONDCX was activated successfully
Activate table BAPITCCONDD
Table BAPITCCONDD was activated successfully
Activate table BAPITCCONDDCX
Table BAPITCCONDDCX was activated successfully
Activate table E1BPTCCOND
Table E1BPTCCOND was activated successfully
Activate table E1BPTCCONDCX
Table E1BPTCCONDCX was activated successfully
Activate table E1BPTCCONDD
Table E1BPTCCONDD was activated successfully
Activate table E1BPTCCONDDCX
Table E1BPTCCONDDCX was activated successfully
Activate table KOMEXPENSE
Table KOMEXPENSE was activated successfully
Activate table KOMTCKO
Table KOMTCKO was activated successfully
Activate table KOMTCKOCX
Table KOMTCKOCX was activated successfully
Activate table KOMTCKOE
Table KOMTCKOE was activated successfully
Activate table KOMWBHIE_NEW
Table KOMWBHIE_NEW was activated successfully
Activate table KOMWBHKEX_NEW
Table KOMWBHKEX_NEW was activated successfully
Activate table KOMWBHKE_NEW
Table KOMWBHKE_NEW was activated successfully
Activate table WB2_CHANGED_FIELDS
Table WB2_CHANGED_FIELDS was activated successfully
Activate table WB2_COND_MAP
Table WB2_COND_MAP was activated successfully
Activate table WB2_KONV_SELECT
Table WB2_KONV_SELECT was activated successfully
Activate table WB2_SCALE_EXTERNAL
Table WB2_SCALE_EXTERNAL was activated successfully
Activate table WBHID_NEW
WBHID_NEW-LGOBE: Table KOMWBHI in search help attachment differs from table of search field
Table WBHID_NEW was activated successfully
Activate table WCOCOH
WCOCOH-RATE: Table KOMWCOCOH in search help attachment differs from table of search field
Table WCOCOH was activated successfully
3T Activation of table type T681E_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type T6B2F_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type TB2BN_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type TB2BO_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type TB2BP_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type TWBACCTYPE_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type TWBEXCLASSGROUP_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPIRET2_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_CONDSCALE_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_CONDSCALE_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_KONH_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_KONP_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_KONP_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_VAKE_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Server Usage ************************************************************
Server.............. Workp Tasks Error .Timesum Objcount ms/Obj ..KCosts ms/KCs
ides_I01_00......... ....3 ....8 ..... .....106 ......42 .2.524 ......29 .3.655
 Parallel execution: 38 sec., Phase out time: 8 sec., Load: 9,2982456140350877E+01 percent
3T *** Activate objects at level 2
Parallel execution with maximal 3 concurrent tasks *
Total of 34 objects with 28.040 costs in 8 tasks
Activate table APPEND_KOMWBHKEX
 8R Enhancement category for table missing
8R Enhancement category for include or subtype missing
Table APPEND_KOMWBHKEX was activated with warnings
Activate table BAPITCCONDITIONITEM
Table BAPITCCONDITIONITEM was activated successfully
Activate table BAPITCCONDITIONITEMO
Table BAPITCCONDITIONITEMO was activated successfully
Activate table BAPITCCONDITIONITEMX
Table BAPITCCONDITIONITEMX was activated successfully
Activate table BAPITCCONDITIONKEY
Table BAPITCCONDITIONKEY was activated successfully
Activate table BAPITCCONDITIONKEYO
Table BAPITCCONDITIONKEYO was activated successfully
Activate table BAPITCCONDITIONKEYX
Table BAPITCCONDITIONKEYX was activated successfully
Activate dependent table KOMWBHIE_APPEND
Activation of dependent table KOMWBHIE_APPEND successful
Activate dependent table KOMWBHKE_APPEND
Activation of dependent table KOMWBHKE_APPEND successful
Activate dependent table KOMWCOCOH
Activation of dependent table KOMWCOCOH successful
Activate dependent table KOMWCOCOH_LI
KOMWCOCOH_LI-RATE: Table KOMWCOCOH in search help attachment differs from table of search field
Activation of dependent table KOMWCOCOH_LI successful
Activate table TWGTA
Table TWGTA was activated successfully
Activate table WB2_KOMG
 8O WB2_KOMG-ZZANZ_KG (combination reference table/field WB2_KOMG-ZZME_KG does not exist)
 8O WB2_KOMG-ZZAUFMENG_KG (combination reference table/field WB2_KOMG-ZZME_KG does not exist)
8R Flag: 'Incorrect enhancement category' could not be updated
Table WB2_KOMG was not activated
Activate dependent table WBHID_APPEND
Activation of dependent table WBHID_APPEND successful
3T Activation of table type KOMEXPENSE_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Activate dependent table type TABKOMTCKO
Activate dependent table type TABKOMTCKOCX
3T Activation of table type WB2B_FIELD_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_CHANGED_FIELDS_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_COND_MAP_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_SCALE_EXTERNAL_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Activate dependent table type WCB_WCOCOH_STAB
Activate dependent table type WCB_WCOCOH_TAB
Activate dependent view DB_WCOCOA
 View must be deleted from the database and created again
Activate dependent view DB_WCOCOA_JEST
 View must be deleted from the database and created again
Activate dependent view DB_WCOCOH_I_ST
 View must be deleted from the database and created again
Activate dependent view V_WCOCOA_CUS_LST
Check dependent search help WCB_SH_CC_NUM_CUS_LST_HEADER
Search help WCB_SH_CC_NUM_CUS_LST_HEADER is consistent
 View must be deleted from the database and created again
Activate dependent view V_WCOCOA_VEN_LST
Check dependent search help WCB_SH_CC_NUM_VEN_LST_HEADER
Search help WCB_SH_CC_NUM_VEN_LST_HEADER is consistent
 View must be deleted from the database and created again
Activate dependent view V_WCOCOH_CUS_LST
Check dependent search help WCB_SH_CC_NUM_CUS_LST_A
Search help WCB_SH_CC_NUM_CUS_LST_A is consistent
 View must be deleted from the database and created again
Activate dependent view V_WCOCOH_VEN_LST
Check dependent search help WCB_SH_CC_NUM_VEN_LST_A
Search help WCB_SH_CC_NUM_VEN_LST_A is consistent
 View must be deleted from the database and created again
Server Usage ************************************************************
Server.............. Workp Tasks Error .Timesum Objcount ms/Obj ..KCosts ms/KCs
ides_I01_00......... ....3 ....8 ..... .....171 ......34 .5.029 ......28 .6.107
 Parallel execution: 82 sec., Phase out time: 44 sec., Load: 6,9512195121951223E+01 percent
3T *** Activate objects at level 3
Parallel execution with maximal 3 concurrent tasks *
Total of 28 objects with 20.340 costs in 6 tasks
Activate dependent search help WCB_SH_CC_NUM_CUS_LST_A
Activate dependent search help WCB_SH_CC_NUM_CUS_LST_HEADER
Activate dependent search help WCB_SH_CC_NUM_VEN_LST_A
Activate dependent search help WCB_SH_CC_NUM_VEN_LST_HEADER
Activate table BAPITCSCALE
Table BAPITCSCALE was activated successfully
Activate table BAPITCSCALEO
Table BAPITCSCALEO was activated successfully
Activate dependent table KOMWBHIE
Activation of dependent table KOMWBHIE successful
Activate dependent table KOMWBHKE
Activation of dependent table KOMWBHKE successful
Activate dependent table KOMWBHKEX
 Append structure APPEND_KOMWBHKEX appended to table KOMWBHKEX
8R Enhancement category 2 possible, but include or subty. not yet classified
Activation of dependent table KOMWBHKEX successful
Activate table WB2_COND_CHANGE
Table WB2_COND_CHANGE was activated successfully
Activate table WB2_KEY_CHANGE
 8O INCLUDE table WB2_KOMG is not active
 8O Routine EXPAND (Table WB2_KEY_CHANGE could not be expanded)
Table WB2_KEY_CHANGE was not activated
Activate table WB2_KOMG_EXT
Table WB2_KOMG_EXT was activated successfully
Activate dependent table WBHID
Activation of dependent table WBHID successful
Activate dependent table type KOMWCOCOH_LI_TAB
Activate dependent table type KOMWCOCOH_STAB
3T Activation of table type WB2_BAPITCCONDITIONITEMO_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPITCCONDITIONITEMX_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPITCCONDITIONITEM_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPITCCONDITIONKEYO_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPITCCONDITIONKEYX_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPITCCONDITIONKEY_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Activation of table type WB2_KOMG_STAB
 8O Row type WB2_KOMG is not active or does not exist
Table type WB2_KOMG_STAB was not activated
Activate dependent table type WCB_DB_WCOCOA_JEST_STAB
Activate dependent table type WCB_DB_WCOCOA_STAB
Activate dependent table type WCB_DB_WCOCOH_I_ST_STAB
Activate view V_TWGTA
Activate dependent view V_TWGTA_CFM
Server Usage ************************************************************
Server.............. Workp Tasks Error .Timesum Objcount ms/Obj ..KCosts ms/KCs
ides_I01_00......... ....3 ....6 ..... ......45 ......28 .1.607 ......20 .2.250
 Parallel execution: 17 sec., Phase out time: 3 sec., Load: 8,8235294117647058E+01 percent
3T *** Activate objects at level 4
Too low cost (3.270) for parallel processing. Minimum: 6.000
Synchronous execution, no parallel processing *
3T Activate dependent table KOMWBHI
KOMWBHI-HKPSTP: Table KOMWBHK in search help attachment differs from table of search field
Activation of dependent table KOMWBHI successful
Activate dependent table type TABKOMWBHIE
3T Activation of table type WB2_BAPITCSCALEO_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_BAPITCSCALE_TAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
3T Activation of table type WB2_COND_CHANGE_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Activation of table type WB2_KEY_CHANGE_STAB
 8O Row type WB2_KEY_CHANGE is not active or does not exist
Table type WB2_KEY_CHANGE_STAB was not activated
3T Activation of table type WB2_KOMG_EXT_STAB
 Actions to be performed for dependent objects: activate, ABAP timestamp, DYNP timestamp
Synchronous processing: 19 sec., 7 objects, 3.270 costs
3T *** Activate objects at level 5
Too low cost (4.630) for parallel processing. Minimum: 6.000
Synchronous execution, no parallel processing *
3T Activate dependent table KOMWBHIH
KOMWBHIH-HKPSTP: Table KOMWBHK in search help attachment differs from table of search field
Activation of dependent table KOMWBHIH successful
3T Activate dependent table MCWBHI
MCWBHI-HKPSTP: Table KOMWBHK in search help attachment differs from table of search field
Activation of dependent table MCWBHI successful
Activate dependent table WB2_NASTLIEF
Activation of dependent table WB2_NASTLIEF successful
Activate dependent table type KOMWBHI_TAB
Activate dependent table type TABKOMWBHI
Activate dependent table type TRCON_KOMWBHI_TAB
Activate dependent table type WB2_KOMWBHI_STAB
Synchronous processing: 27 sec., 7 objects, 4.630 costs
3T *** Activate objects at level 6
Too low cost (2.160) for parallel processing. Minimum: 6.000
Synchronous execution, no parallel processing *
Activate dependent table TRCON_OUTP_DBDATA
Activation of dependent table TRCON_OUTP_DBDATA successful
Activate dependent table type GT_MCWBHI
Activate dependent table type KOMWBHIH_TAB
Activate dependent table type WB2_NASTLIEF_TAB
Synchronous processing: 2 sec., 4 objects, 2.160 costs
Object Activation
End phase 001 ***********************************************************
Start phase 002 **********************************************************
Final log
Following objects not activated/deleted or activated/deleted w. warning:
3T 8O Table WB2_KEY_CHANGE could not be activated
8O Table WB2_KOMG could not be activated
8O Table Type WB2_KEY_CHANGE_STAB could not be activated
(E- Row type WB2_KEY_CHANGE is not active or does not exist )
8O Table Type WB2_KOMG_STAB could not be activated
8R Table Type WB2_CHANGED_FIELDS_STAB was activated (error in the dependencies)
8R Table Type WB2_VAKE_TAB was activated (error in the dependencies)
8R Table APPEND_KOMWBHKEX was activated (warning for the dependent tables)
8R Table KOMWBHKEX_NEW was activated (warning for the dependent tables)
Final log
End phase 002 ***********************************************************
Start phase 003 **********************************************************
Statistics on Activated and Deleted Objects
Number of objects to be activated............: 118
Objects not activated........................: 4
Activated objects with errors in dependencies: 2
Objects activated with warning...............: 2
Successfully activated objects...............: 110
Number of objects to be deleted..............: 0
Objects not successfully deleted.............: 0
Successfully deleted objects.................: 0
Tables/views with DROP/CREATE................: 0
No. of them marked for DROP/CREATE: 0
Not marked for DROP/CREATE: 0
Number of nametabs to be deleted.............: 0
Successfully deleted nametabs................: 0
Nametabs that were not successfully deleted..: 0
Statistics on Activated and Deleted Objects
End phase 003 ***********************************************************
=========================================================================
Mass Activation
=========================================================================
 Process..................: ides_9
Return code..............: 8
Phase 001..................: 00:03:05 (Object Activation)
Phase 002..................: < 1 sec. (Final log)
Phase 003..................: < 1 sec. (Statistics on Activated and ...)
Program runtime..........: 00:03:20
Date, time...............: 20.04.2007, 17:17:55
Program end==============================================================
ABAP Dictionary: Activation
End date and time : 20070420171755
 8O Ended with return code: ===> 8 <===
ALOG
ALL I01.ALL t 0000 20070419142033 DDIC ides
SAPKD70022 I01.ALL m 0000 20070419142040 SAPUSER DDIC ides
SAPKD70022 I01.ALL L 0004 20070419142051 SAPUSER DDIC ides 20070419142042
SAPKD70022 I01.ALL P 0004 20070419142056 SAPUSER DDIC ides 20070419142053
SAPKD70022 I01.ALL H 0004 20070419142615 SAPUSER DDIC ides 20070419142100
SAPKD70022 I01.ALL A 0004 20070419142914 SAPUSER DDIC ides 20070419142100
ALL I01.ALL S 0000 20070419142929 DDIC ides 20070419142100
ALL I01.ALL 6 0004 20070419142947 DDIC ides 20070419142100
SAPKD70022 I01.ALL I 0004 20070419143215 SAPUSER DDIC ides 20070419142100
ALL I01.ALL n 0000 20070419143340 DDIC ides 20070419142100
SAPKD70022 I01.ALL R 0000 20070419143413 SAPUSER DDIC ides 20070419142100
ALL I01.ALL t 0000 20070419145325 DDIC ides
SAPKD70023 I01.ALL m 0000 20070419145327 SAPUSER DDIC ides
SAPKD70023 I01.ALL L 0004 20070419145330 SAPUSER DDIC ides 20070419145328
SAPKD70023 I01.ALL P 0004 20070419145332 SAPUSER DDIC ides 20070419145331
SAPKD70023 I01.ALL H 0004 20070419145350 SAPUSER DDIC ides 20070419145332
SAPKD70023 I01.ALL A 0004 20070419145432 SAPUSER DDIC ides 20070419145332
ALL I01.ALL S 0000 20070419145439 DDIC ides 20070419145332
ALL I01.ALL 6 0000 20070419145443 DDIC ides 20070419145332
SAPKD70023 I01.ALL I 0004 20070419145527 SAPUSER DDIC ides 20070419145332
ALL I01.ALL n 0000 20070419145529 DDIC ides 20070419145332
SAPKD70023 I01.ALL R 0000 20070419145535 SAPUSER DDIC ides 20070419145332
ALL I01.ALL t 0000 20070419150805 DDIC ides
SAPKB70010 I01.ALL m 0000 20070419150826 SAPUSER DDIC ides
SAPKB70010 I01.ALL L 0004 20070419151011 SAPUSER DDIC ides 20070419150915
SAPKB70010 I01.ALL P 0004 20070419151101 SAPUSER DDIC ides 20070419151032
SAPKB70010 I01.ALL H 0004 20070419152544 SAPUSER DDIC ides 20070419152217
SAPKB70010 I01.ALL A 0004 20070419154149 SAPUSER DDIC ides
ALL I01.ALL S 0000 20070419154232 DDIC ides 20070419154155
ALL I01.ALL N 0000 20070419154335 DDIC ides 20070419154155
ALL I01.ALL 6 0004 20070419154820 DDIC ides 20070419154155
SAPKB70010 I01.ALL I 0004 20070419163829 SAPUSER DDIC ides 20070419154155
ALL I01.ALL n 0000 20070419164133 DDIC ides 20070419154155
SAPKB70010 I01.ALL R 0000 20070419171913 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070419172644 DDIC ides
ALL I01.ALL t 0000 20070420101414 DDIC ides
ALL I01.ALL t 0000 20070420102627 DDIC ides
SAPKA70010 I01.ALL m 0000 20070420102638 SAPUSER DDIC ides
SAPKIPYJ7A I01.ALL m 0000 20070420102647 PIBASISUSER DDIC ides
SAPKW70010 I01.ALL m 0000 20070420102659 SAPUSER DDIC ides
SAPKNA7007 I01.ALL m 0000 20070420102705 SAPAPUSER DDIC ides
SAPKH60007 I01.ALL m 0000 20070420102728 SAPUSER DDIC ides
SAPK-60007INFICA I01.ALL m 0000 20070420102754 SAPUSER DDIC ides
SAPK-60007INFICAX I01.ALL m 0000 20070420102757 SAPUSER DDIC ides
SAPKA70010 I01.ALL L 0004 20070420102832 SAPUSER DDIC ides 20070420102800
SAPKIPYJ7A I01.ALL L 0004 20070420102838 PIBASISUSER DDIC ides 20070420102800
SAPKW70010 I01.ALL L 0004 20070420102906 SAPUSER DDIC ides 20070420102800
SAPKNA7007 I01.ALL L 0004 20070420102910 SAPAPUSER DDIC ides 20070420102800
SAPKH60007 I01.ALL L 0004 20070420102949 SAPUSER DDIC ides 20070420102800
SAPK-60007INFICA I01.ALL L 0004 20070420103005 SAPUSER DDIC ides 20070420102800
SAPK-60007INFICAX I01.ALL L 0004 20070420103007 SAPUSER DDIC ides 20070420102800
SAPKA70010 I01.ALL P 0004 20070420103039 SAPUSER DDIC ides 20070420103026
SAPKIPYJ7A I01.ALL P 0004 20070420103042 PIBASISUSER DDIC ides 20070420103026
SAPKW70010 I01.ALL P 0004 20070420103053 SAPUSER DDIC ides 20070420103026
SAPKNA7007 I01.ALL P 0004 20070420103055 SAPAPUSER DDIC ides 20070420103026
SAPKH60007 I01.ALL P 0004 20070420103121 SAPUSER DDIC ides 20070420103026
SAPK-60007INFICA I01.ALL P 0004 20070420103126 SAPUSER DDIC ides 20070420103026
SAPK-60007INFICAX I01.ALL P 0004 20070420103128 SAPUSER DDIC ides 20070420103026
SAPKA70010 I01.ALL H 0004 20070420104455 SAPUSER DDIC ides 20070420104317
SAPKIPYJ7A I01.ALL H 0004 20070420104510 PIBASISUSER DDIC ides 20070420104317
SAPKW70010 I01.ALL H 0004 20070420104614 SAPUSER DDIC ides 20070420104317
SAPKNA7007 I01.ALL H 0004 20070420104619 SAPAPUSER DDIC ides 20070420104317
SAPKH60007 I01.ALL H 0004 20070420105120 SAPUSER DDIC ides 20070420104317
SAPK-60007INFICA I01.ALL H 0004 20070420105217 SAPUSER DDIC ides 20070420104317
SAPK-60007INFICAX I01.ALL H 0004 20070420105228 SAPUSER DDIC ides 20070420104317
ALL I01.ALL t 0000 20070420110210 DDIC ides
SAPK-60007INFICA I01.ALL A 0004 20070420115140 SAPUSER DDIC ides
SAPK-60007INFICAX I01.ALL A 0004 20070420115140 SAPUSER DDIC ides
SAPKA70010 I01.ALL A 0004 20070420115140 SAPUSER DDIC ides
SAPKH60007 I01.ALL A 0004 20070420115140 SAPUSER DDIC ides
SAPKIPYJ7A I01.ALL A 0004 20070420115140 PIBASISUSER DDIC ides
SAPKNA7007 I01.ALL A 0004 20070420115140 SAPAPUSER DDIC ides
SAPKW70010 I01.ALL A 0004 20070420115140 SAPUSER DDIC ides
ALL I01.ALL S 0000 20070420115355 DDIC ides 20070420115217
ALL I01.ALL N 0000 20070420115401 DDIC ides 20070420115217
ALL I01.ALL 6 0004 20070420120305 DDIC ides 20070420115217
SAPKA70010 I01.ALL I 0004 20070420121421 SAPUSER DDIC ides 20070420115217
SAPKIPYJ7A I01.ALL I 0004 20070420121612 PIBASISUSER DDIC ides 20070420115217
SAPKW70010 I01.ALL I 0004 20070420123219 SAPUSER DDIC ides 20070420115217
SAPKNA7007 I01.ALL I 0004 20070420123349 SAPAPUSER DDIC ides 20070420115217
SAPKH60007 I01.ALL I 0004 20070420130625 SAPUSER DDIC ides 20070420115217
SAPK-60007INFICA I01.ALL I 0004 20070420131144 SAPUSER DDIC ides 20070420115217
SAPK-60007INFICAX I01.ALL I 0004 20070420131253 SAPUSER DDIC ides 20070420115217
ALL I01.ALL n 0000 20070420131356 DDIC ides 20070420115217
SAPKA70010 I01.ALL R 0000 20070420132346 SAPUSER DDIC ides
SAPKIPYJ7A I01.ALL R 0000 20070420132353 PIBASISUSER DDIC ides
SAPKW70010 I01.ALL R 0000 20070420134358 SAPUSER DDIC ides
SAPKNA7007 I01.ALL R 0000 20070420134934 SAPAPUSER DDIC ides
SAPKH60007 I01.ALL R 0006 20070420140042 SAPUSER DDIC ides
SAPK-60007INFICA I01.ALL R 0000 20070420140703 SAPUSER DDIC ides
SAPK-60007INFICAX I01.ALL R 0000 20070420140713 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420141932 DDIC ides
ALL I01.ALL t 0000 20070420141939 DDIC ides
ALL I01.ALL t 0000 20070420142045 DDIC ides
ALL I01.ALL t 0000 20070420142823 DDIC ides
SAPKGPID07 I01.ALL m 0000 20070420142825 SAPUSER DDIC ides
SAPKGPID07 I01.ALL L 0004 20070420142836 SAPUSER DDIC ides 20070420142828
SAPKGPID07 I01.ALL P 0004 20070420142839 SAPUSER DDIC ides 20070420142837
ALL I01.ALL 6 0000 20070420143317 DDIC ides 20070420143303
SAPKGPID07 I01.ALL I 0004 20070420143348 SAPUSER DDIC ides 20070420143303
ALL I01.ALL t 0000 20070420143614 DDIC ides
SAPKW70011 I01.ALL m 0000 20070420143625 SAPUSER DDIC ides
SAPKW70011 I01.ALL L 0004 20070420143742 SAPUSER DDIC ides 20070420143632
SAPKW70011 I01.ALL P 0004 20070420143811 SAPUSER DDIC ides 20070420143749
SAPKW70011 I01.ALL H 0004 20070420144247 SAPUSER DDIC ides 20070420144134
SAPKW70011 I01.ALL A 0004 20070420144612 SAPUSER DDIC ides
ALL I01.ALL S 0000 20070420144641 DDIC ides 20070420144617
ALL I01.ALL 6 0004 20070420144903 DDIC ides 20070420144617
SAPKW70011 I01.ALL I 0004 20070420150622 SAPUSER DDIC ides 20070420144617
ALL I01.ALL n 0000 20070420150652 DDIC ides 20070420144617
SAPKW70011 I01.ALL R 0000 20070420151931 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420153322 DDIC ides
SAPKGPDD07 I01.ALL m 0000 20070420153324 SAPUSER DDIC ides
SAPKGPDD07 I01.ALL L 0004 20070420153338 SAPUSER DDIC ides 20070420153326
SAPKGPDD07 I01.ALL P 0004 20070420153345 SAPUSER DDIC ides 20070420153340
SAPKGPDD07 I01.ALL H 0004 20070420153632 SAPUSER DDIC ides 20070420153610
SAPKGPDD07 I01.ALL A 0004 20070420153818 SAPUSER DDIC ides
ALL I01.ALL S 0000 20070420153831 DDIC ides 20070420153823
ALL I01.ALL 6 0000 20070420153905 DDIC ides 20070420153823
SAPKGPDD07 I01.ALL I 0004 20070420154205 SAPUSER DDIC ides 20070420153823
SAPKGPDD07 I01.ALL R 0000 20070420154226 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420154751 DDIC ides
SAPKGPAD07 I01.ALL m 0000 20070420154807 SAPUSER DDIC ides
SAPKGPAD07 I01.ALL L 0004 20070420154851 SAPUSER DDIC ides 20070420154814
SAPKGPAD07 I01.ALL P 0004 20070420154911 SAPUSER DDIC ides 20070420154856
SAPKGPAD07 I01.ALL H 0004 20070420155533 SAPUSER DDIC ides 20070420155317
ALL I01.ALL t 0000 20070420155918 DDIC ides
SAPKGPAD07 I01.ALL A 0004 20070420160620 SAPUSER DDIC ides
ALL I01.ALL S 0000 20070420160638 DDIC ides 20070420160625
ALL I01.ALL 6 0004 20070420160743 DDIC ides 20070420160625
SAPKGPAD07 I01.ALL I 0004 20070420162359 SAPUSER DDIC ides 20070420160625
ALL I01.ALL n 0000 20070420162445 DDIC ides 20070420160625
SAPKGPAD07 I01.ALL R 0004 20070420163533 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420163915 DDIC ides
ALL I01.ALL t 0000 20070420164004 DDIC ides
ALL I01.ALL t 0000 20070420164112 DDIC ides
SAPKGPFD07 I01.ALL m 0000 20070420164119 SAPUSER DDIC ides
SAPKGPFD07 I01.ALL L 0004 20070420164205 SAPUSER DDIC ides 20070420164129
SAPKGPFD07 I01.ALL P 0004 20070420164217 SAPUSER DDIC ides 20070420164209
SAPKGPFD07 I01.ALL H 0004 20070420164645 SAPUSER DDIC ides 20070420164524
SAPKGPFD07 I01.ALL A 0004 20070420165233 SAPUSER DDIC ides
ALL I01.ALL S 0000 20070420165248 DDIC ides 20070420165238
ALL I01.ALL 6 0000 20070420165322 DDIC ides 20070420165238
SAPKGPFD07 I01.ALL I 0004 20070420170133 SAPUSER DDIC ides 20070420165238
ALL I01.ALL n 0000 20070420170156 DDIC ides 20070420165238
SAPKGPFD07 I01.ALL R 0000 20070420170418 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420170650 DDIC ides
ALL I01.ALL t 0000 20070420171054 DDIC ides
SAPKGPGD07 I01.ALL m 0000 20070420171056 SAPUSER DDIC ides
SAPKGPGD07 I01.ALL L 0004 20070420171108 SAPUSER DDIC ides 20070420171059
SAPKGPGD07 I01.ALL P 0004 20070420171112 SAPUSER DDIC ides 20070420171109
SAPKGPGD07 I01.ALL H 0004 20070420171431 SAPUSER DDIC ides 20070420171339
SAPKGPGD07 I01.ALL A 0008 20070420171755 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420171911 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420171918 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420172106 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420172117 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420173251 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420173255 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420173753 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420173756 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420173914 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420173917 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420174114 DDIC ides
ALL I01.ALL t 0000 20070420174541 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420174543 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420181327 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420181355 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420183111 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420183123 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420183655 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420183700 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420185422 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420185424 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420185611 TMSADM ides
ALL I01.ALL S 0000 20070420190348 DDIC ides 20070420190338
ALL I01.ALL t 0000 20070420190358 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420190403 SAPUSER DDIC ides
ALL I01.ALL 6 0000 20070420190407 DDIC ides 20070420190338
ALL I01.ALL a 0000 20070420190537 DDIC ides
ALL I01.ALL t 0000 20070420190559 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420190606 SAPUSER DDIC ides
ALL I01.ALL d 0000 20070420190622 DDIC ides
SAPKGPGD07 I01:000 I 0004 20070420190713 SAPUSER DDIC ides 20070420190338
ALL I01.ALL t 0000 20070420190713 DDIC ides
ALL I01.ALL Q 0000 20070420190717 DDIC ides 20070420190338
SAPKGPGD07 I01.ALL A 0008 20070420190925 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420191154 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420191156 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420202424 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420202534 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420204507 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420204509 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420211533 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420211555 SAPUSER DDIC ides
ALL I01.ALL t 0000 20070420220457 DDIC ides
SAPKGPGD07 I01.ALL A 0008 20070420220500 SAPUSER DDIC ides
SLOG
START CMDIMPORT I01 L 20070419142043 DDIC ides 20070419142042
STOP CMDIMPORT I01 L 20070419142052 DDIC ides 20070419142042
START imp all I01 20070419142100 DDIC ides 20070419142100
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT I01 H 20070419142101 DDIC ides 20070419142100
STOP DD IMPORT I01 H 20070419142617 DDIC ides 20070419142100
START DD ACTIVATION I01 A 20070419142618 DDIC ides 20070419142100
START tp_getprots I01 J 20070419142620 DDIC ides 20070419142100
STOP tp_getprots I01 J 20070419142918 DDIC ides 20070419142100
STOP DD ACTIVATION I01 A 20070419142918 DDIC ides 20070419142100
START DISTRIBUTION OF DD-O I01 S 20070419142918 DDIC ides 20070419142100
START tp_getprots I01 S 20070419142918 DDIC ides 20070419142100
STOP tp_getprots I01 S 20070419142933 DDIC ides 20070419142100
STOP DISTRIBUTION OF DD-O I01 S 20070419142933 DDIC ides 20070419142100
INFO TBATG CONVERSION OF I01 N not needed DDIC ides 20070419142100
START MOVE NAMETABS I01 6 20070419142934 DDIC ides 20070419142100
START tp_getprots I01 P 20070419142934 DDIC ides 20070419142100
STOP tp_getprots I01 P 20070419142949 DDIC ides 20070419142100
STOP MOVE NAMETABS I01 6 20070419142949 DDIC ides 20070419142100
START MAIN IMPORT I01 I 20070419142949 DDIC ides 20070419142100
STOP MAIN IMPORT I01 I 20070419143215 DDIC ides 20070419142100
START TBATG CREATION OF EN I01 n 20070419143216 DDIC ides 20070419142100
START tp_getprots I01 Y 20070419143216 DDIC ides 20070419142100
STOP tp_getprots I01 Y 200How was this problem fixed? We are running into the same problem. Any help will be much appreciated.
Thanks so much.
Mario -
Support Package Manager: SPAM/SAINT Update
Hi,
I downloaded the SPAM/SAINT Update and executed it with SAPCAR in the directory of the Application Server Folder. The original file KD74053.sar (6767 kb) is still in the folder, but a new file 'signature.smf' (5 kb) appeared.
What is that one for?
Next, I think that I should be able to take a next step with transaction SPAM (Support Package --> Load Packages --> From Application Server), but it's 'blanked out' and not accessible.
What are the next steps and how do I really get the SPAM/SAINT update working, so I can proceed to my actual goal, the Support Package Update.
Thanks!Hi,
To reset DDIC password you could go with
SQL> select bname from usr02 where mandt='000' and bname='SAP*'
If the user SAP* exists then delete the user with below command
SQL> delete from usr02 where mandt='000' and bname='SAP*'
Run the below command to verify whether user deletion was successful.
SQL> select bname from usr02 where mandt='000' and bname='SAP*'
SQL> commit;
After that login to client 000 with SAP* and password as pass
reset the password for user DDIC with SAP* user.
Thanks,
Gaurav -
Worst case scenario for spam update error
hi friends
i need to know what is the worst case scenario if our support package stack update(SPAM) process fails. I am asking this question because we dont have a DR system.I mean we dont have test server to check our restore & recovery. We have ECC 5.0 and our SPAM updates are long overdue. I need to convince the management to prioritize this activity and my boss thinks that since we dont have test server if anything goes wrong then we might have to restore the db which he is not in favor of.
i would really help if you could provide me some suggestions.
thanks in advance.
regardsHello Nathan,
Very first you need to convince your management that since you didn't had the Support package update in your system actually you are not having the latest corrections available in the system. As per Best practise you should keep the systems to the latest available support package levels.
Now, to your question.Support package update is a easy but critical activity. Easy because it is bit effortless and critical because major changes are involved with the corrections. UPdate for BASIS support package can bring your system to HIghly unstable state (I am just talking about Worst case scenarios) as they update the system basis tables. Application component packages if aborted due to some errors can have problems in the business cycles.
So anyways you'll have to keep proper backup of your system available just to make sure if, by chance you are not able to complete the SP update under the given downtime window you should have the possibility to restore and release the systems to the business users.
This will not be the new thing you'll be doing as majority of the customers don't have DR server to the rescue.
You can discuss with your team and decide a suitable backup strategy.
I hope it helps.
Best Regards
NIraj -
I am trying to update to iTunes 10.5 and am getting a Apple Software update error. "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. ?? I can't uninstall the Apple Software Update from my Control Panel. It states "Fatal error during installation" Please HELP!!!
I am experiencing the exact same issue during the installtion process for iTunes 10.5.
I uninstalled all Apple components but when I attempted to uninstall the Apple Software Update I received the same message: "Fatal error during installtion." I was able to repair the Apple Software Update but still could not install iTunes 10.5 afterwards.
I have tried everything that I could find on these discussions pages as well as other suggestions on third party sites. I continue to receive the error message: "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I was able to uninstall and reinstall QuickTime 7.7.1. During the reinstalltion process I received the same message (There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.) But after clicking "OK" the installtion process was succesful. PLEASE HELP! -
Each time I attempt to download the new itunes 10.5 I keep getting the following error message:
Product: Apple Software Update -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SoftwareUpdate_UnregServer, location: C:\Program Files\Apple Software Update\SoftwareUpdate.exe, command: /UnregServer
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any Ideas of how to solve this one?After reading all these posts, one by one did not resolve my problem until I got the very end. Regardless of what step would resolve your problem, these are the steps I would recomment to everyone for a what seems to be a safe and fool-proof upgrade to iTunes 10.5.
1. Stand alone upgrade to the latest Quicktime version
2. Go to control panel and "change" then select repair to the following applications in the order specified by the post on Oct 27. (Notice I skipped Quicktime because it had been upgrade manually,and Bonjour did not have a "repair" option)
iTunes; Apple Software Update: Mobile Device Support; Apple Applications Support
Some of these applications may not appear if they do not apply to your configuration (no iPhone, or no iPad, or other apple devices).
Once all updated, I did not need to restart nor launch any applications, I simply went straight into the 10.5 upgrade, and where it normally got stuck, this time the installation continued for a while longer until it completed successfully.
Great work everyone who contributed! Thank you very much! -
Hi Experts,
Currently i am installing suppport package for PI 7.10.
SP : SAP_BASIS.
Just newly installed the sap system -> after kernel upgrade, i applied latest SPAM verion - 27.
NowBusiness package SAP -basis is in the process. I started the package three hours back. still is in the process. i chcked the log files /usr/sap/trans/tmp/SAPIB71006.<SID>
==================================================================== ).
4 ETW000 1 entry for SOTR_TEXT rejected - language not installed (00127991401D
1DEBBA864FE336A2EB85J*
4 ETW690 COMMIT "0" "1008778130"
4 ETW000 0 entries for SOTR_TEXT imported (00127991401D1DEBBA864FE336A2EB85E*)
4 ETW690 COMMIT "0" "1008778130"
4 ETW000 0 entries for SOTR_TEXT imported (00127991401D1DEBBA864FE336A2EB85D*)
4 ETW690 COMMIT "0" "1008778130"
4 ETW690 COMMIT "0" "1008778130"
4 ETW000 0 entries for SOTR_HEAD imported (00127991401D1DEBB0E8673749278B85*).
4 ETW690 COMMIT "0" "1008778130"
4 ETW000 0 entries for SOTR_TEXT imported (00127991401D1DEBB0E8673749278B85J*
4 ETW000 1 entry for SOTR_TEXT rejected - language not installed (00127991401D
1DEBB0E8673749278B85J*
4 ETW690 COMMIT "0" "1008778130"
=====================================================================
Observed that error says `entry for SOTR_TEXT rejected - language not installed`
I have not installed the language import till now. I am wondering that that could be an issue.
My logs are keep updating. symptom tells than till import is in the progress.
Could someone reply, Does the Language import must for Support package installation ?.
Now Spam screen says that `Main import ` on the screen.
Thanks
ThirumalHi Vani,
Thank you very much,
SAP_Basis package has been successfully completed. As u said language import not required to update support packages.
It took me around 7 hours to complete the update.Now i have started the Rest of the Business package.
It seems its totally killing my time. I think it shouldnot take this much time to complete a single package I need to install other packages like .
SAP_ABA, PI_Basis,SAP_BW and ST_PI.
Hi Vamshi,
Thank you. Finally package completed.
Thanks and Regards
Thirumal -
Error in Applying Java support packages through JSPM
Hi All,
While Applying support packages, Package CAF 7.00 SP 13 is through an error
help required.
For detailed information see the log file of the Deploy Service.
07/12/05 21:55:26 - ***********************************************************
Dec 5, 2007 9:55:26 PM Info: End of log messages of the target system.
Dec 5, 2007 9:55:26 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 5, 2007 9:55:26 PM Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0', grouped by software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Dec 5, 2007 9:55:26 PM Info: Starting to save the repository
Dec 5, 2007 9:55:28 PM Info: Finished saving the repository
Dec 5, 2007 9:55:28 PM Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
Dec 5, 2007 9:55:28 PM Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0' : aborted
Please, look at error logs above for more information!
Dec 5, 2007 9:55:28 PM Info: Starting to save the repository
Dec 5, 2007 9:55:30 PM Info: Finished saving the repository
Dec 5, 2007 9:55:30 PM Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
Dec 5, 2007 9:55:30 PM Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0':
No further description found.
Dec 5, 2007 9:55:30 PM Info: Starting to save the repository
Dec 5, 2007 9:55:32 PM Info: Finished saving the repository
Dec 5, 2007 9:55:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 5, 2007 9:55:32 PM Error: -
At least one of the Deployments failed -
Regards,
Prashant.Hello Prashant.
Check this supporting SAP note 1010640. It will solve your problem.
This is typical problem when you upgrade from < SP8 to higher version.
You need to Undeploy the CAF components from the system using SDM first and then reply the patches from JSPM.
It should go with out errors.
Let us know if this worked.
*Reward points for helpful answer.
Regards,
Prashant P. -
Error while applying support packages
Hi,
I was applying support packges for NW 7.0 EHP2 for the components SAP BASIS/ABAP/PI BASIS & BW, the support package level was 02, I have downloaded 03,04,05,06 for all the above four components. While updating spam/saint update I got the above error, displayed below. But even while applying support packages I got a list of errrors.
1.
Category: Abap programming error
Runtime error: call_function_parm_unknown
CX_SY_DYN_CALL_PARAM_NOT_FOUND
abap program: RSSPAM07
Function parameter "IV_IMP_SCENARIO" in unknown
this first error displayed after applying SPAM/SAINT update.
2. The import was stopped, since an error occured during the phase IMPORT_PROPER, which the support package Manager is unable to resolve without your input
The following details help you to analyse the problem:
Error in phase : IMPROT_PROPER
Reason for error:
Return code:
Error Message:
Please provide any solution as soon as possible....The details of SLOG
START CMDIMPORT NG1 L 20120227162812 SHABZ BasisTrn3 20120227162811973
STOP CMDIMPORT NG1 L 20120227162813 SHABZ BasisTrn3 20120227162811973
START imp all NG1 20120227162821 SHABZ BasisTrn3 20120227162821661
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT NG1 H 20120227162822 SHABZ BasisTrn3 20120227162821661
STOP DD IMPORT NG1 H 20120227162839 SHABZ BasisTrn3 20120227162821661
START DD ACTIVATION NG1 A 20120227162839 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 J 20120227162839 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 J 20120227162925 SHABZ BasisTrn3 20120227162821661
STOP DD ACTIVATION NG1 A 20120227162925 SHABZ BasisTrn3 20120227162821661
START DISTRIBUTION OF DD-O NG1 S 20120227162925 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 S 20120227162925 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 S 20120227162929 SHABZ BasisTrn3 20120227162821661
STOP DISTRIBUTION OF DD-O NG1 S 20120227162929 SHABZ BasisTrn3 20120227162821661
INFO TBATG CONVERSION OF NG1 N not needed SHABZ BasisTrn3 20120227162821661
START MOVE NAMETABS NG1 6 20120227162929 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 P 20120227162929 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 P 20120227162935 SHABZ BasisTrn3 20120227162821661
STOP MOVE NAMETABS NG1 6 20120227162936 SHABZ BasisTrn3 20120227162821661
START MAIN IMPORT NG1 I 20120227162936 SHABZ BasisTrn3 20120227162821661
STOP MAIN IMPORT NG1 I 20120227163023 SHABZ BasisTrn3 20120227162821661
START TBATG CREATION OF EN NG1 n 20120227163024 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 Y 20120227163024 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 Y 20120227163034 SHABZ BasisTrn3 20120227162821661
STOP TBATG CREATION OF EN NG1 n 20120227163034 SHABZ BasisTrn3 20120227162821661
START EXECUTION OF REPORTS NG1 R 20120227163035 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 R 20120227163035 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 R 20120227163202 SHABZ BasisTrn3 20120227162821661
STOP EXECUTION OF REPORTS NG1 R 20120227163202 SHABZ BasisTrn3 20120227162821661
INFO EXECUTION OF STANDAR NG1 9 not needed SHABZ BasisTrn3 20120227162821661
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all NG1 0004 20120227163203 SHABZ BasisTrn3 20120227162821661
START CMDIMPORT NG1 L 20120227164418 SHABZ BasisTrn3 20120227164416991
STOP CMDIMPORT NG1 L 20120227164454 SHABZ BasisTrn3 20120227164416991
START DD IMPORT NG1 H 20120227165608 SHABZ BasisTrn3 20120227165607479
STOP DD IMPORT NG1 H 20120227170309 SHABZ BasisTrn3 20120227165607479
START DD ACTIVATION NG1 A 20120227170313 SHABZ BasisTrn3
START tp_getprots NG1 J 20120227170313 SHABZ BasisTrn3
STOP tp_getprots NG1 J 20120227171206 SHABZ BasisTrn3
STOP DD ACTIVATION NG1 A 20120227171206 SHABZ BasisTrn3
START imp all NG1 20120227171208 SHABZ BasisTrn3 20120227171207614
INFO: event SAP_IMPORT_START triggered successfully
START DISTRIBUTION OF DD-O NG1 S 20120227171208 SHABZ BasisTrn3 20120227171207614
START tp_getprots NG1 S 20120227171208 SHABZ BasisTrn3 20120227171207614
STOP tp_getprots NG1 S 20120227171303 SHABZ BasisTrn3 20120227171207614
STOP DISTRIBUTION OF DD-O NG1 S 20120227171304 SHABZ BasisTrn3 20120227171207614
START TBATG CONVERSION OF NG1 N 20120227171304 SHABZ BasisTrn3 20120227171207614
START tp_getprots NG1 N 20120227171304 SHABZ BasisTrn3 20120227171207614
STOP tp_getprots NG1 N 20120227171307 SHABZ BasisTrn3 20120227171207614
STOP TBATG CONVERSION OF NG1 N 20120227171307 SHABZ BasisTrn3 20120227171207614
START MOVE NAMETABS NG1 6 20120227171307 SHABZ BasisTrn3 20120227171207614
START tp_getprots NG1 P 20120227171308 SHABZ BasisTrn3 20120227171207614
STOP tp_getprots NG1 P 20120227171755 SHABZ BasisTrn3 20120227171207614
STOP MOVE NAMETABS NG1 6 20120227171755 SHABZ BasisTrn3 20120227171207614
START MAIN IMPORT NG1 I 20120227171756 SHABZ BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP MAIN IMPORT NG1 I 20120227195335 SHABZ BasisTrn3 20120227171207614
START TBATG CREATION OF EN NG1 n 20120227195335 SHABZ BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
START tp_getprots NG1 Y 20120227195335 SHABZ BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP tp_getprots NG1 Y 20120227195521 SHABZ BasisTrn3 20120227171207614
STOP TBATG CREATION OF EN NG1 n 20120227195521 SHABZ BasisTrn3 20120227171207614
INFO EXECUTION OF STANDAR NG1 9 not needed SHABZ BasisTrn3 20120227171207614
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all NG1 0903 20120227195522 SHABZ BasisTrn3 20120227171207614 -
Problem while updating the Support Package 17 on my SAP WAS SP9
Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
SatyaHello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...). -
Importing Support Packages - Error during XPRA_EXECUTION
Hello,
Database: Oracle 10.2.0.4
Operation System: Windows Server 2008 X64
I´m facing with an error during an importing of support packages in our Solution Manager Ehp1 system (SPS 20 to SPS 25).
I checked the import logs of the queue and I see in there the following error:
Program terminated (job: RDDEXECL, no.: 02083200)
See job log
Execution of programs after import (XPRA)
End date and time : 20110126020847
Ended with return code: ===> 12 <===
When I checked the job log I see in there this:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server SAPSM were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
I went to ST22 and I see in there that specific short dump which show:
Short text
XSLT: No valid XML source
What happened?
The transformation is not possible since the XML source document cannot
be parsed.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_XSLT_RUNTIME_ERROR', was not
caught in
procedure "TRANSFORM_FROM_XML" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Either the source document contains invalid XML or it is handled
incorrectly in the ABAP program that called the transformation.
How to correct the error
The most common cause of this error is a conflict between the encoding
specified in the declaration <?xml version="1.0" encoding="..."?> in the
document and the actual encoding of the data.
If the document is held in an ABAP string, the actual encoding is the
system code page. If this does not match the declaration, a parsing
error may occur.
These conflicts are a particular issue when XML documents are produced
in one system and then imported into a system with a different code page
(as strings).
For this reason, XML documents should be held as binary data (X strings)
, if they are extracted from the system or accessed from outside.
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:
"XSLT_BAD_SOURCE_CONTEXT" "CX_XSLT_RUNTIME_ERROR"
"CL_SM_BFR_CONTENT_TRANSPORT===CP" or "CL_SM_BFR_CONTENT_TRANSPORT===CM00E"
"TRANSFORM_FROM_XML"
The exception must either be prevented, caught within proedure
"TRANSFORM_FROM_XML" "(METHOD)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
Can you help how to correct this situation for I can continue the update of support packages!
Best regards,
João Dimas - PortugalHello William,
Which import logs do you refer?
I pasted in my first message the log of import... that is the unique error that it appeared.
I checked the SLOG:
STOP MOVE NAMETABS SSM 6 20110125215838 SAP_BASIS SAPSM 20110125214839404
START MAIN IMPORT SSM I 20110125215838 SAP_BASIS SAPSM 20110125214839404
STOP MAIN IMPORT SSM I 20110125235752 SAP_BASIS SAPSM 20110125214839404
START TBATG CREATION OF EN SSM n 20110125235752 SAP_BASIS SAPSM 20110125214839404
START tp_getprots SSM Y 20110125235753 SAP_BASIS SAPSM 20110125214839404
WARNING: '\SAPSMsapmnt rans mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
WARNING: '\SAPSMsapmnt rans mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
STOP tp_getprots SSM Y 20110126000148 SAP_BASIS SAPSM 20110125214839404
STOP TBATG CREATION OF EN SSM n 20110126000148 SAP_BASIS SAPSM 20110125214839404
INFO EXECUTION OF STANDAR SSM 9 not needed SAP_BASIS SAPSM 20110125214839404
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all SSM 0004 20110126000149 SAP_BASIS SAPSM 20110125214839404
I also checked the ULOG which has the following records:
APServiceSSM 20110126013719 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=\SAPSMsapmnt rans (pid=5276)
APServiceSSM 20110126020829 RFC: tp SHOWPARAMS SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt rans (pid=5196)
APServiceSSM 20110126020830 RFC: tp CONNECT SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt rans (pid=5196)
APServiceSSM 20110126020831 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -
Any idea what´s happen?!
Kind regards,
João Dimas - Portugal -
Update Java Support Package Stack in JSPM
Hi all,
When i update Java Support Package Stack in JSPM i can't start the dispatcher
[Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 920] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
When i goto the log-file of the dispatcher (server.0.log):
E:
usr
sap
P01
DVEBMGS01
j2ee
cluster
dispatcher
bin
services
log_configurator
log_configurator.jar
Loading model: {parent,local,references}
The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
#1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
#1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
Somebody know how to solve this problem?
Thanks in advance,
Cheungdefaulttrc.0.trc"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 2, 10485760]/>
<!PREVIOUSFILE[defaultTrace.1.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 12 more#
#1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 13 more#
#1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 12 more#
#1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 13 more#
Maybe you are looking for
-
I am writing a Universal app. I have a dto (MobileProject) that has several properties, one of which is ShortName. In my ViewModel, I have a property (SelectedProject) to hold which item is bound to the SelectedItem in the ComboBox. private M
-
In Aperture, is there a way to sort photos not by date and time, but so that they display in the order I repeatedly need them within the browser, by for example assigning numbers in decimal form and somehow (?) making that the sort field? Thanks for
-
When I try to access photo sharing from apple tv tv I cannot access because apple tv says AT&T conditions have changed. I read the suggestion from apple to accept the new terms e conditions from pc or iPad but neither pc or iPad ask me to accept the
-
Premiere 8.1 overwrites adjacent audio clip when original clip sent to Audition
We have been editing a documentary in PR 8.0.1 for several months and the UI started to get really sluggish 1.5 weeks ago. I upgraded to PR 8.1 to see if it would solve the problem and hadn't checked the forum. We were able to get a couple of days of
-
My OP sys is win 8.1 I would like to consolidate all my games under GAMES. Right now if I sesrch for games only 4-5 shows up but I have about 15. Could I move them under "GAMES" I know how to move icon on the START page but on the apps page (when I