Hemanth,
Yes, I have done the same, reverted back to 7.20_EXT. Let me watch couple of days if the issue re-occurs or not. Only MOPZ calculated 7.21_EXT, but looks like still it is not compatible.
Thanks,
Kavitha Rajan.
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Hi Kavitha,
Yes, thats the best option. I would suggest that you raise an incident in the BC-CST-STS component so that this can be checked.
In the meantime, just use the manual kernel update and use a older stable kernel.
How to do a Manual Kernel Upgrade of an SAP Server
Regards,
Hemanth
↧
↧
Re: Slowness in SAP after
Hi Anuradha,
Did you find a solution for the slowness...
What is your connection method to the server?
Is it on your LAN or Connecting through SAP Router?
Regards,
Surendra
↧
RSECNOTE and RTCCTOOL crash when executed from se38 was working until now
RSECNOTE and RTCCTOOL crash when executed from se38 was working until now.
Last time i did run these report all was good, that was last year, no changes have been done to the system.
These reports are failing in al my systems sandbox dev test and prod.
This seems to have someting to do with the pse certificated.
The Pse is still vaild so i´m lost on this.
↧
Re: RSECNOTE and RTCCTOOL crash when executed from se38 was working until now
do not copy and paste the dump, please attach to the thread.
see note 2056661 - /SSA/NXS dump "Parameter B_WRITEHIST unknown" on basis 740 up to SP04
↧
↧
Re: RSECNOTE and RTCCTOOL crash when executed from se38 was working until now
Hi
Check the following Notes based on your system version
2056661 - /SSA/NXS dump "Parameter B_WRITEHIST unknown" on basis 740 up to SP04
Thanks ,
Manu
↧
Re: RSECNOTE and RTCCTOOL crash when executed from se38 was working until now
Hi,
Implement the above said SAP Note 2056661 - /SSA/NXS dump "Parameter B_WRITEHIST unknown" on basis 740 up to SP04
and if still issue persists try to apply support packages for ST-A/PI and SAP_BASIS as well.
Regards,
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Hi All,
Even after reverting the kernel, the issue still exists. I cannot move to QA upgrade until I fix this in SBX and DEV. Pls help.
Disp+work on ABAP side stopped. In the java system server0 stopped with-11113 (Core service or additional service start fails: "HaltOnAdditionalServiceFailure=true"(service manager)).
---------------------------------------------------
trc file: "dev_disp", trc level: 1, release: "720"
---------------------------------------------------
sysno 00
sid CRD
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 700
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile F:\usr\sap\CRD\SYS\profile\CRD_DVEBMGS00_SAPCRMDEV
pid 6404
kernel runs with dp version 140000(ext=121000) (@(#) DPLIB-INT-VERSION-140000-UC)
length of sys_adm_ext is 592 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 6404) [dpxxdisp.c 1326]
shared lib "dw_xml.dll" version 700 successfully loaded
shared lib "dw_xtc.dll" version 700 successfully loaded
shared lib "dw_stl.dll" version 700 successfully loaded
shared lib "dw_gui.dll" version 700 successfully loaded
shared lib "dw_mdm.dll" version 700 successfully loaded
shared lib "dw_rndrt.dll" version 700 successfully loaded
shared lib "dw_abp.dll" version 700 successfully loaded
shared lib "dw_sym.dll" version 700 successfully loaded
shared lib "dw_aci.dll" version 700 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
rdisp/dynamic_wp_check : 1
rdisp/calculateLoadAverage : 1
Tue Jan 20 11:45:08 2015
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6492]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is active
display_tcp_ip: 0
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >SAPCRMDEV_CRD_00 <
DpShMCreate: sizeof(wp_adm) 63168 (2256)
DpShMCreate: sizeof(tm_adm) 5517056 (27448)
DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
DpShMCreate: sizeof(appc_ca_adm) 128000 (64)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080
DpShMCreate: sizeof(comm_adm) 1384080 (2744)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=512/48/163904/96560/260512
DpShMCreate: sizeof(slock_adm) 260512 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=5600/16/537664/537680
DpShMCreate: sizeof(file_adm) 537680 (80)
DpShMCreate: sizeof(vmc_adm) 60480 (2160)
DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 0000000007780050, size: 8117840)
DpShMCreate: allocated sys_adm at 0000000007780060
DpShMCreate: allocated wp_adm_list at 00000000077830D0
DpShMCreate: allocated wp_adm at 00000000077832C0
DpShMCreate: allocated tm_adm_list at 0000000007792990
DpShMCreate: allocated tm_adm at 00000000077929E0
DpShMCreate: allocated wp_ca_adm at 0000000007CD58F0
DpShMCreate: allocated appc_ca_adm at 0000000007CE5300
DpShMCreate: allocated comm_adm at 0000000007D04710
DpShMCreate: allocated slock_adm at 0000000007E565B0
DpShMCreate: allocated file_adm at 0000000007E95F60
DpShMCreate: allocated vmc_adm_list at 0000000007F193C0
DpShMCreate: allocated vmc_adm at 0000000007F19470
DpShMCreate: allocated gw_adm at 0000000007F280C0
DpShMCreate: allocated j2ee_adm at 0000000007F28100
DpShMCreate: allocated ca_info at 0000000007F29080
DpShMCreate: allocated wall_adm at 0000000007F29110
DpCommAttachTable: attached comm table (header=0000000007D04710/ft=0000000007D04720)
DpSysAdmIntInit: initialize sys_adm
rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
dia token check not active (15 token)
MBUF state OFF
DpCommInitTable: init table for 500 entries
DpFileInitTable: init table for 5600 entries
DpSesCreateTable: created session table at 0000000002E90050 (len=167472)
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> EsILock: use spinlock for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 2865 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 192 MB
mm.dump: set global maximum dump mem to 192 MB
EsRegisterEmCheck: Register EmGetEsHandles at 0000000140A25A70
Es2ResCreate: Changed resource parameters to
filenamePrefix =
blockSizeKB = 2048 KB
initialSizeMB = 480 MB
extendSizeMB = 240 MB
maxSizeMB = 19680 MB
DpVmcSetActive: set vmc state DP_VMC_ENABLED
DpVmcSetActive: set vmc state DP_VMC_ACTIVE
DpVmcInit2: o.k.
MPI: dynamic quotas disabled.
MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 4.0.1 4.0.1 5.1) [dpxxdisp.c 1712]
***LOG Q0K=> DpMsAttach, mscon ( SAPCRMDEV) [dpxxdisp.c 12865]
MBUF state LOADING
DpStartStopMsg: send start message (myname is >SAPCRMDEV_CRD_00 <)
DpStartStopMsg: start msg sent
CCMS: Initialized monitoring segment of size 60000000.
CCMS: Initialized CCMS Headers in the shared monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: AlMsUpload called by wp 1024.
Tue Jan 20 11:45:09 2015
CCMS: AlMsUpload successful for F:\usr\sap\CRD\DVEBMGS00\log\ALMTTREE.DAT (2864 MTEs).
Tue Jan 20 11:45:13 2015
CCMS: start to initalize 3.X shared alert area (first segment).
Tue Jan 20 11:45:15 2015
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]
MBUF state ACTIVE
DpWpBlksLow: wp blocks in queue threshold is 800 (80 %)
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpAppcBlksLow: appc blocks in queue threshold is 1000 (50 %)
Tue Jan 20 11:45:18 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
DpModState: change server state from STARTING to ACTIVE
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:20 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:21 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:22 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:23 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:24 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:25 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:26 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:27 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:28 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:29 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:30 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:32 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:33 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:34 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:35 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:36 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:43 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:44 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:45 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:46 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:45:47 2015
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Tue Jan 20 11:52:25 2015
DpWpConf: requested operation mode switch:
DIA 15->17 BTC 6->4 UPD 2->2 UP2 1->1 ENQ 1->1 SPO 1->1 RESTR 0->0 DYN 2->2
***LOG Q0V=> DpWpConf, mod_req (020BTCDIA) [dpxxdisp.c 15852]
***LOG Q0V=> DpWpConf, mod_req (022BTCDIA) [dpxxdisp.c 15852]
DpAdaptWppriv_max_no : 10 -> 12
DpWpConf: operation mode switch completed
DIA water mark reached (>30)
DIA water mark underrun (<=30)
Tue Jan 20 15:16:32 2015
DpHdlDeadWp: W4 (pid=5256) terminated automatically
Tue Jan 20 15:19:52 2015
DpHdlDeadWp: W6 (pid=3108) terminated automatically
Tue Jan 20 15:20:32 2015
DpHdlDeadWp: W0 (pid=5020) terminated automatically
Tue Jan 20 15:29:33 2015
DpHdlDeadWp: W7 (pid=3204) terminated automatically
DpHdlDeadWp: W9 (pid=152) terminated automatically
Tue Jan 20 16:22:08 2015
SoftCancel request for T29 U10629 M0 received from REMOTE_TERMINAL
SoftCancel request for T31 U16703 M0 received from APPC_SERVER
SoftCancel request for T53 U16704 M0 received from APPC_SERVER
Tue Jan 20 16:22:35 2015
DpHdlDeadWp: W11 (pid=4088) terminated automatically
Tue Jan 20 16:22:39 2015
*** ERROR => DpRqCheck: T53 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7118): [dpxxdisp.c 6208]
-IN-- sender_id APPC_SERVER tid 53 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 16704 appc_ca_blk 80 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 80 rq_id 60903
-IN-- msg_name -
Tue Jan 20 16:24:25 2015
SoftCancel request for T31 U18443 M0 received from IC_MAN
SoftCancel request for T53 U18444 M0 received from IC_MAN
DpRqCheck: mode 0 in status CANCEL
Tue Jan 20 16:24:46 2015
SoftCancel request for T31 U18492 M0 received from IC_MAN
SoftCancel request for T54 U18484 M0 received from IC_MAN
Tue Jan 20 16:24:50 2015
SoftCancel request for T53 U18498 M0 received from IC_MAN
SoftCancel request for T32 U18496 M0 received from IC_MAN
SoftCancel request for T54 U18495 M0 received from IC_MAN
DpRqCheck: mode 0 in status CANCEL
SoftCancel request for T53 U18498 M0 received from IC_MAN
*** ERROR => DpRqCheck: T53 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7118): [dpxxdisp.c 6208]
-IN-- sender_id DISPATCHER tid 53 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 18498 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 61436
-IN-- prio HIGH
-IN-- req_info DP_SOFT_CANCEL
-IN-- msg_name -
DpRqCheck: mode 0 in status CANCEL
SoftCancel request for T32 U18496 M0 received from IC_MAN
*** ERROR => DpRqCheck: T32 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7118): [dpxxdisp.c 6208]
-IN-- sender_id DISPATCHER tid 32 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 18496 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 61439
-IN-- prio HIGH
-IN-- req_info DP_SOFT_CANCEL
-IN-- msg_name -
Tue Jan 20 16:25:00 2015
SoftCancel request for T32 U18518 M0 received from IC_MAN
SoftCancel request for T31 U18516 M0 received from IC_MAN
DpRqCheck: mode 0 in status CANCEL
SoftCancel request for T32 U18518 M0 received from IC_MAN
*** ERROR => DpRqCheck: T32 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7118): [dpxxdisp.c 6208]
-IN-- sender_id DISPATCHER tid 32 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 18518 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 61498
-IN-- prio HIGH
-IN-- req_info DP_SOFT_CANCEL
-IN-- msg_name -
*** ERROR => DpRqCheck: T31 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 4234): [dpxxdisp.c 6208]
-IN-- sender_id DISPATCHER tid 31 wp_ca_blk 140 wp_id 2
-IN-- action SEND_TO_WP uid 18516 appc_ca_blk -1 type NOWP
-IN-- new_stat NO_CHANGE mode 0 len 8 rq_id 61489
-IN-- req_info CANCELMODE
-IN-- msg_name -
Tue Jan 20 16:25:09 2015
SoftCancel request for T31 U18532 M0 received from IC_MAN
DpRqCheck: mode 0 in status CANCEL
Tue Jan 20 16:25:10 2015
SoftCancel request for T31 U18536 M0 received from IC_MAN
SoftCancel request for T32 U18534 M0 received from IC_MAN
*** ERROR => DpRqCheck: T32 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 3943): [dpxxdisp.c 6208]
-IN-- sender_id IC_MAN tid 32 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_DP uid 18534 appc_ca_blk -1 type NOWP
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 61554
-IN-- req_info DP_SOFT_CANCEL,DP_ICM_EVENT
-IN-- msg_name -
Tue Jan 20 16:25:23 2015
*** ERROR => DpRqCheck: T54 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 4234): [dpxxdisp.c 6208]
-IN-- sender_id DISPATCHER tid 54 wp_ca_blk 455 wp_id 0
-IN-- action SEND_TO_WP uid 18544 appc_ca_blk -1 type NOWP
-IN-- new_stat NO_CHANGE mode 0 len 8 rq_id 61607
-IN-- req_info CANCELMODE
-IN-- msg_name -
*** ERROR => DpRqCheck: T54 in state TM_SLOT_FREE [dpxxdisp.c 8087]
***LOG Q0G=> DpRqBadHandle, bad_req (NOWP) [dpxxdisp.c 6206]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 4234): [dpxxdisp.c 6208]
-IN-- sender_id DISPATCHER tid 54 wp_ca_blk 456 wp_id 0
-IN-- action SEND_TO_WP uid 18544 appc_ca_blk -1 type NOWP
-IN-- new_stat NO_CHANGE mode 0 len 8 rq_id 61620
-IN-- req_info CANCELMODE
-IN-- msg_name -
Tue Jan 20 16:31:35 2015
DpHdlDeadWp: W20 (pid=5076) terminated automatically
Tue Jan 20 16:32:35 2015
DpHdlDeadWp: W6 (pid=1552) terminated automatically
DpHdlDeadWp: W7 (pid=8028) terminated automatically
Tue Jan 20 16:32:55 2015
DpHdlDeadWp: W1 (pid=6044) terminated automatically
DpHdlDeadWp: W10 (pid=5420) terminated automatically
Tue Jan 20 16:39:15 2015
DpHdlDeadWp: W9 (pid=8160) terminated automatically
Tue Jan 20 16:39:35 2015
DpHdlDeadWp: W12 (pid=5432) terminated automatically
Tue Jan 20 16:39:55 2015
DpHdlDeadWp: W8 (pid=5096) terminated automatically
Tue Jan 20 16:40:35 2015
DpHdlDeadWp: W22 (pid=1804) terminated automatically
Tue Jan 20 17:10:36 2015
DpHdlDeadWp: W5 (pid=2452) terminated automatically
Tue Jan 20 17:29:16 2015
DpHdlDeadWp: W8 (pid=8120) terminated automatically
Tue Jan 20 17:31:56 2015
DpHdlDeadWp: W11 (pid=2856) terminated automatically
Tue Jan 20 17:32:16 2015
DpHdlDeadWp: W1 (pid=740) terminated automatically
Tue Jan 20 17:42:17 2015
DpHdlDeadWp: W14 (pid=5928) terminated automatically
Tue Jan 20 17:42:37 2015
DpHdlDeadWp: W3 (pid=3684) terminated automatically
Tue Jan 20 20:00:37 2015
DpWpConf: requested operation mode switch:
DIA 17->15 BTC 4->6 UPD 2->2 UP2 1->1 ENQ 1->1 SPO 1->1 RESTR 0->0 DYN 2->2
***LOG Q0V=> DpWpConf, mod_req (014DIABTC) [dpxxdisp.c 15852]
***LOG Q0V=> DpWpConf, mod_req (004DIABTC) [dpxxdisp.c 15852]
DpAdaptWppriv_max_no : 12 -> 10
DpWpConf: operation mode switch completed
Tue Jan 20 21:06:07 2015
DpHdlDeadWp: W22 (pid=6096) terminated automatically
Tue Jan 20 21:48:48 2015
DpHdlDeadWp: W22 (pid=1164) terminated automatically
Tue Jan 20 22:22:10 2015
***LOG Q0I=> NiIRead: P=127.0.0.1:64745; L=127.0.0.1:3200: recv (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 63/sock 996
(SI_ECONN_BROKEN/10053; I4; ST; P=127.0.0.1:64745; L=127.0.0.1:3200) [nixxi.cpp 5082]
Tue Jan 20 23:25:09 2015
***LOG Q0I=> NiIRead: P=192.168.101.63:3900; L=192.168.101.63:49596: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 17/sock 960
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.101.63:3900; L=192.168.101.63:49596) [nixxi.cpp 5082]
*** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c 2833]
Tue Jan 20 23:25:32 2015
*****************************************************************************
*
* LOCATION SAP-Dispatcher SAPCRMDEV_CRD_00 on host SAPCRMDEV
* ERROR Reading data from the message server (SAPCRMDEV / 3900)
* failed.
* Please check the trace file of the message server.
*
* TIME Tue Jan 20 23:25:32 2015
* RELEASE 720
* COMPONENT MS (message handling interface, multithreaded)
* VERSION 4
* RC -36
* MODULE msxxi.c
* LINE 2852
* COUNTER 8024
*
*****************************************************************************
*** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c 1867]
MBUF state OFF
MBUF component DOWN
*** ERROR => DpMsgProcess: MsReceive () -> MSENILAYER, partner: [dpxxdisp.c 2604]
*** ERROR => DpMsgProcess: disconnect from msg_server [dpxxdisp.c 2675]
Tue Jan 20 23:25:46 2015
***LOG Q0K=> DpMsAttach, mscon ( SAPCRMDEV) [dpxxdisp.c 12865]
MBUF state LOADING
***LOG Q0I=> NiIRead: P=127.0.0.1:49788; L=127.0.0.1:3200: recv (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 57/sock 1296
(SI_ECONN_BROKEN/10053; I4; ST; P=127.0.0.1:49788; L=127.0.0.1:3200) [nixxi.cpp 5082]
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]
MBUF state ACTIVE
MBUF component UP
DpMsgProcess: 1 server in MBUF
Tue Jan 20 23:51:32 2015
*** WARNING => DpEnvCheck: no answer from msg server since 20 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c 8486]
Tue Jan 20 23:51:52 2015
*** WARNING => DpEnvCheck: no answer from msg server since 40 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c 8486]
Tue Jan 20 23:52:12 2015
*** WARNING => DpEnvCheck: no answer from msg server since 60 secs, but dp_ms_keepalive_timeout(300 secs) not reached [dpxxdisp.c 8486]
Tue Jan 20 23:52:13 2015
***LOG Q0I=> NiIRead: P=192.168.101.63:3900; L=192.168.101.63:49789: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 18/sock 1000
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.101.63:3900; L=192.168.101.63:49789) [nixxi.cpp 5082]
*** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c 2833]
*****************************************************************************
*
* LOCATION SAP-Dispatcher SAPCRMDEV_CRD_00 on host SAPCRMDEV
* ERROR Reading data from the message server (SAPCRMDEV / 3900)
* failed.
* Please check the trace file of the message server.
*
* TIME Tue Jan 20 23:52:13 2015
* RELEASE 720
* COMPONENT MS (message handling interface, multithreaded)
* VERSION 4
* RC -36
* MODULE msxxi.c
* LINE 2852
* COUNTER 8335
*
*****************************************************************************
*** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c 1867]
MBUF state OFF
MBUF component DOWN
*** ERROR => DpMsgProcess: MsReceive () -> MSENILAYER, partner: [dpxxdisp.c 2604]
*** ERROR => DpMsgProcess: disconnect from msg_server [dpxxdisp.c 2675]
Tue Jan 20 23:52:17 2015
***LOG Q0K=> DpMsAttach, mscon ( SAPCRMDEV) [dpxxdisp.c 12865]
Tue Jan 20 23:52:31 2015
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]
MBUF state ACTIVE
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpMsgProcess: 1 server in MBUF
Wed Jan 21 00:08:32 2015
***LOG Q0I=> NiIRead: P=192.168.101.63:3900; L=192.168.101.63:50407: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 19/sock 1016
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.101.63:3900; L=192.168.101.63:50407) [nixxi.cpp 5082]
*** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c 2833]
*****************************************************************************
*
* LOCATION SAP-Dispatcher SAPCRMDEV_CRD_00 on host SAPCRMDEV
* ERROR Reading data from the message server (SAPCRMDEV / 3900)
* failed.
* Please check the trace file of the message server.
*
* TIME Wed Jan 21 00:08:32 2015
* RELEASE 720
* COMPONENT MS (message handling interface, multithreaded)
* VERSION 4
* RC -36
* MODULE msxxi.c
* LINE 2852
* COUNTER 8474
*
*****************************************************************************
*** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c 1867]
MBUF state OFF
MBUF component DOWN
*** ERROR => DpMsgProcess: MsReceive () -> MSENILAYER, partner: [dpxxdisp.c 2604]
*** ERROR => DpMsgProcess: disconnect from msg_server [dpxxdisp.c 2675]
Wed Jan 21 00:08:44 2015
***LOG Q0K=> DpMsAttach, mscon ( SAPCRMDEV) [dpxxdisp.c 12865]
Wed Jan 21 00:08:57 2015
DpMBufHwIdSet: set Hardware-ID
Wed Jan 21 00:09:04 2015
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]
MBUF state ACTIVE
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpMsgProcess: 1 server in MBUF
Wed Jan 21 00:38:15 2015
*** WARNING => DpITimeCheck: suspicious forward jump of current time 1421818695, last time 1421817252 [dpxxdisp.c 9153]
DpITimeCheck: new time seems to be OK now, I accept 1421818695
*** WARNING => DpTimeCheck: huge diff between current 1421817312 and next schedule (act_time 1421818695 delay 120 [dpxxdisp.c 9326]
Wed Jan 21 00:38:34 2015
***LOG Q0I=> NiIRead: P=192.168.101.63:3900; L=192.168.101.63:50773: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 20/sock 1292
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.101.63:3900; L=192.168.101.63:50773) [nixxi.cpp 5082]
*** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c 2833]
*****************************************************************************
*
* LOCATION SAP-Dispatcher SAPCRMDEV_CRD_00 on host SAPCRMDEV
* ERROR Reading data from the message server (SAPCRMDEV / 3900)
* failed.
* Please check the trace file of the message server.
*
* TIME Wed Jan 21 00:38:34 2015
* RELEASE 720
* COMPONENT MS (message handling interface, multithreaded)
* VERSION 4
* RC -36
* MODULE msxxi.c
* LINE 2852
* COUNTER 8507
*
*****************************************************************************
*** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c 1867]
MBUF state OFF
MBUF component DOWN
*** ERROR => DpMsgProcess: MsReceive () -> MSENILAYER, partner: [dpxxdisp.c 2604]
*** ERROR => DpMsgProcess: disconnect from msg_server [dpxxdisp.c 2675]
*** ERROR => MsISnd2: not_attached [msxxi.c 1510]
***LOG Q0N=> DpRqNoWpHandle, MsSnd2Type () [dpxxdisp.c 5557]
Wed Jan 21 00:38:39 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:38:45 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:39:05 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:39:25 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:39:50 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:40:15 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:40:35 2015
*** ERROR => MsIAttachEx: NiBufConnect to SAPCRMDEV/3900 failed (rc=NIECONN_PENDING) [msxxi.c 718]
Wed Jan 21 00:59:28 2015
***LOG Q0I=> NiIRead: P=192.168.101.63:3900; L=192.168.101.63:50894: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 20/sock 1292
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.101.63:3900; L=192.168.101.63:50894) [nixxi.cpp 5082]
***LOG Q0I=> NiIRead: P=192.168.101.63:3900; L=192.168.101.63:50894: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
*** ERROR => NiIRead: SiRecv failed for hdl 20/sock 1292
(SI_ECONN_BROKEN/10054; I4; ST; P=192.168.101.63:3900; L=192.168.101.63:50894) [nixxi.cpp 5082]
*** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c 2833]
*****************************************************************************
*
* LOCATION SAP-Dispatcher SAPCRMDEV_CRD_00 on host SAPCRMDEV
* ERROR The connection to the specified message server
* (SAPCRMDEV / 3900) failed. Please check the trace file
* of the message server. If a network filter has
* been activated (see message server parameters
* ms/acl_file_...) please check the configuration
*
* TIME Wed Jan 21 00:59:28 2015
* RELEASE 720
* COMPONENT MS (message handling interface, multithreaded)
* VERSION 4
* RC -35
* MODULE msxxi.c
* LINE 2861
* COUNTER 8510
*
*****************************************************************************
*** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c 1867]
***LOG Q1K=> MsIAttachEx: StoC check failed, Kernel not compatible with system (rc=-100) [msxxi.c 820]
*** ERROR => Kernel incompatible to already connected instances (see dev_ms for details) [dpxxdisp.c 12810]
Wed Jan 21 00:59:41 2015
DpHalt: shutdown server >SAPCRMDEV_CRD_00 < (normal)
DpHalt: stop work processes
Wed Jan 21 00:59:42 2015
SoftCancel request for T39 U19749 M0 received from DISPATCHER
DpHdlSoftCancel: wp 0 inside critical section, do not interrupt now
SoftCancel request for T11 U12 M0 received from DISPATCHER
SoftCancel request for T18 U19 M0 received from DISPATCHER
SoftCancel request for T21 U22 M0 received from DISPATCHER
SoftCancel request for T23 U24 M0 received from DISPATCHER
Wed Jan 21 01:01:06 2015
*** ERROR => DpWpKill(7968, SIGUSR2): kill failed [dpxxtool.c 2792]
*** ERROR => DpWpKill(584, SIGUSR2): kill failed [dpxxtool.c 2792]
*** ERROR => DpWpKill(3088, SIGUSR2): kill failed [dpxxtool.c 2792]
DpHalt: stop gateway
DpHalt: stop icman
DpHalt: terminate gui connections
DpHalt: wait for end of work processes
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:07 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:09 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:10 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:12 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:13 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:14 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:16 2015
DpHalt: waiting for termination of work processes ...
Wed Jan 21 01:01:17 2015
DpHalt: wait for end of gateway
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:18 2015
*** ERROR => 21.01.2015 06:01:18.185 PID=6404, TID=5220 SapTimer warning. Took time keeping ownership. PID=6404, old owner PID:5888 [dpxxdisp.c 21728]
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:19 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:20 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:21 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:22 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:24 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:26 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:27 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:28 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:29 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:30 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:32 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:33 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:34 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:36 2015
DpHalt: waiting for termination of gateway ...
Wed Jan 21 01:01:37 2015
*** ERROR => [DpProcDied] Process died (PID:3924 HANDLE:964 rc:0x0) [dpnttool2.c 147]
DpHalt: wait for end of icman
*** ERROR => [DpProcDied] Process died (PID:7016 HANDLE:972 rc:0x0) [dpnttool2.c 147]
DpHalt: not attached to the message server
DpHalt: cleanup EM
***LOG Q05=> DpHalt, DPStop ( 6404) [dpxxdisp.c 11745]
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Hi,
Could you share your system host file and are you able to resolve host name of the system.
Regards,
↧
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Gaurav/All,
I found why java Server0 is shutting. It is because of UME service failure from the ABAP side. If disp+work is not shutting down on ABAP side, then Server0 should be fine in java side. I have also attached hosts file from C:\Windows\System32\drivers\etc. Pls help.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=SAPCRMDEV SYSNR=00 PCS=1
LOCATION CPIC (TCP/IP) on local host SAPCRMDEV with Unicode
ERROR partner '192.168.101.63:3300' not reached
TIME Wed Jan 21 01:02:46 2015
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3283
DETAIL NiPConnect2: 192.168.101.63:3300
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=<Java Rfc client> ASHOST=SAPCRMDEV SYSNR=00 PCS=1
LOCATION CPIC (TCP/IP) on local host SAPCRMDEV with Unicode
ERROR partner '192.168.101.63:3300' not reached
TIME Wed Jan 21 01:02:46 2015
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3283
DETAIL NiPConnect2: 192.168.101.63:3300
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:447)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jan 21, 2015 1:02:46 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_70] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Heap
par new generation reserved 614400K, committed 614400K, used 39570K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)
eden space 409600K, 1% used [0x000000007fff0000, 0x00000000806be6a8, 0x0000000098ff0000)
from space 102400K, 31% used [0x000000009f3f0000, 0x00000000a13c6350, 0x00000000a57f0000)
to space 102400K, 0% used [0x0000000098ff0000, 0x0000000098ff0000, 0x000000009f3f0000)
concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)
concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 34760K [0x00000000ffff0000, 0x000000011fff0000, 0x000000011fff0000)
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Thanks,
Kavitha Rajan.
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Just want to add that both ABAP and Java (CRD and CDJ) are in the same server with separate DB.
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Hi Kavitha,
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Could you edit above and make it as like
127.0.0.1 localhost.localdomain localhost
<Server IP> <Hostname>
save the entries and try to start the server again.
Regards,
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
I suspect part of the root of the problem may be a lack of available dialog work processes on the ABAP system. You are getting the error:
*** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
This happens very close to the beginning of the dispatcher trace. What is probably happening here is the system is trying to generate programs during startup (which is common when importing a new version of the kernel -- or reverting to an older version), for which it needs available dialog WPs, but all the WPs are busy. Make sure that you have at least as many DIA WPs as non-DIA WPs configured (i.e., sum up the BTC, ENQ, VB, VB2, and SPO work processes, and set DIA to that number (or higher)).
I also see the setting:
rdisp/dynamic_wp_check : 1
This should be ok with NetWeaver 7.02, but just to be safe, you might want to revert to the 7.01 behavior, which is to disallow dynamic work processes (at least while troubleshooting -- once the system starts up in a stable manner, you can experiment with re-enabling them). To do this, set the following parameters in your instance profile:
rdisp/wp_no_restricted = 0
rdisp./configurable_wp_no = 0
rdisp/dynamic_wp_check = FALSE
Also make sure that rdisp/wp_max_no is set to a number equal to the sum of all the other rdisp/wp_no_* settings (dia, vb2, btc, vb, spo, and enq), and that rdisp/wp_no_dia is equal to or greater than the sum of the "non-dia" settings.
Regards,
Matt
↧
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Hi Kavitha,
UME is a core service and unless it starts, the J2EE server nodes wil not reach the running state. So you need to make sure that the ABAP part is fully functional.
Apart from the point Matt mentioned, check if the same stack SAPEXE* and SAPEXEDB* files were used when you did the kernel upgrade.
Check the output of:
sapcontrol -nr 00 -function GetVersionInfo
The versions should be same for all files.
regards,
Hemanth
↧
Re: Question about shrink the log file in the SQL Server database
Hi
Change the backup mode to Simple and do shrink and revert to full mode
Regards,
Sudarshan
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Hi All,
I changed the hosts file as recommended by Gaurav and monitored couple of days, system is continuously up now. No shutdown in the non-business hours. Reverting kernel and host file changes, fixed my issue of dispatcher shutting down. Thank you ALL for helping me in resolving the issues.
Regards,
Kavitha Rajan.
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Great news Kavitha 
.
↧
↧
Re: After Upgrade kernel not compatible with system (rc=-100)
Oh Great to know your issue has been resolved now !!
Nice experience for me also.
Regards,
Gaurav
↧
The transaction log for database 'SID' is full.
Hi Team,
We are performing system copy to sandbox. While importing i got few errors.
Could you please help us on this issue.
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed:The transaction log for database 'SBX' is full. To find out why space in the log cannot be reused, see the lo>
(IMP) ERROR: ExeFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE INDEX [BSIS~1] ON [BSIS] ( [MANDT] , [BUKRS] , [BELNR] , [GJAHR] , [BUZEI] ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 9002)
error message returned by DbSl:
The transaction log for database 'SBX' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
(DB) ERROR: DDL statement failed
(CREATE INDEX [BSIS~Z01] ON [BSIS] ( [MANDT] , [BUKRS] , [HKONT] , [BUDAT] ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 9002)
error message returned by DbSl:
The transaction log for database 'SBX' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
(DB) INFO: disconnected from DB
F:\usr\sap\SBX\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 3 error(s)
F:\usr\sap\SBX\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20150124000512
Thank you
Regards
Nani
↧
Re: The transaction log for database 'SID' is full.
Hi Nani
I think your MS Sql DB log full, you have to take the truncate log backup to reduce the log disk free space or increase the DB disk free space.
Kindly refer the SAP Note 1151572 - R3load uses DELETE for restart
BR
SS
↧