I have urgent problem
After client copy from production to a new client I changing parameter value for new default client.
The system does not start. Namely disp+work.exe does not start. What is wrong?
the trace log:
-
trc file: "dev_disp", trc level: 1, release: "640"
-
Mon Aug 27 11:07:45 2007
kernel runs with dp version 130(ext=102) (@(#) DPLIB-INT-VERSION-130)
length of sys_adm_ext is 312 bytes
sysno 00
sid BK1
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 101
intno 20020600
make: multithreaded, ASCII
pid 3212
***LOG Q00=> DpSapEnvInit, DPStart (00 3212) [dpxxdisp.c 1098]
Mon Aug 27 11:07:46 2007
shared lib "dw_xml.dll" version 101 successfully loaded
shared lib "dw_xtc.dll" version 101 successfully loaded
shared lib "dw_stl.dll" version 101 successfully loaded
shared lib "dw_gui.dll" version 101 successfully loaded
shared lib "dw_mdm.dll" version 101 successfully loaded
Mon Aug 27 11:07:48 2007
Mon Aug 27 11:07:52 2007
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3887]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpShMCreate: sizeof(wp_adm) 9112 (828)
DpShMCreate: sizeof(tm_adm) 2379840 (11840)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpShMCreate: sizeof(comm_adm) 192000 (384)
DpShMCreate: sizeof(vmc_adm) 0 (364)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY (addr: 05900040, size: 2667936)
DpShMCreate: allocated sys_adm at 05900040
DpShMCreate: allocated wp_adm at 059017D0
DpShMCreate: allocated tm_adm_list at 05903B68
DpShMCreate: allocated tm_adm at 05903B90
DpShMCreate: allocated wp_ca_adm at 05B48BD0
DpShMCreate: allocated appc_ca_adm at 05B4D220
DpShMCreate: allocated comm_adm_list at 05B4E990
DpShMCreate: allocated comm_adm at 05B4E9A8
DpShMCreate: allocated vmc_adm_list at 05B7D7A8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 05B7D7D0
DpShMCreate: allocated wall_adm at 05B7D7D8
Mon Aug 27 11:07:53 2007
MBUF state OFF
Mon Aug 27 11:07:55 2007
call semaphore clean-up function ...
***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c 462]
-
C-STACK -
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
-
Application exception occurred:
Exception : c0000005 (Access Violation)
App : disp+work.exe (pid=3212)
When : 8/27/2007 11:7:55.78
Threads : 2
-
Computer Name : BKRRAZVOJ
User Name : SAPServiceBK1
-
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 3
Windows Version : 5.2 Current Build: 3790
-
State Dump for Thread Id c98
eax=0401d150 ebx=00000000 ecx=010992e8 edx=7c82eec6 esi=000361d4 edi=000361a8
eip=7c82ed54 esp=0401cadc ebp=0401caec iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206
function : ab_rfcmode
008d312c 8b8024010000 mov eax,[eax+0x124] ds:0401d274=ffff027f
008d3132 830820 or dword ptr [eax],0x20 ds:0401d150=0401d23c
008d3135 390d8073f501 cmp [ct_level (01f57380)],ecx ds:01f57380=00000001
008d313b 8bf1 mov esi,ecx
008d313d 7c58 jl ab_rfcmode+0xc8 (008d3197)
008d313f e8a824c6ff call DpLock (005355ec)
008d3144 683038a601 push 0x1a63830
008d3149 ebc8 jmp rfc_userkey+0x78 (008d3213)
008d314b a1e0927403 mov eax,[zttaptr (037492e0)] ds:037492e0=04541fe0
008d3150 8b8024010000 mov eax,[eax+0x124] ds:0401d274=ffff027f
FAULT-> 008d3156 f60020 test byte ptr [eax],0x20 ds:0401d150=3c
008d3159 57 push edi
008d315a 6a02 push 0x2
008d315c 59 pop ecx
008d315d 7409 jz ab_rfcmode+0x99 (008d3168)
008d315f bf0038a601 mov edi,0x1a63800
008d3164 8bf1 mov esi,ecx
008d3166 eb08 jmp ab_rfcmode+0xa1 (008d3170)
008d3168 33f6 xor esi,esi
008d316a bf0838a601 mov edi,0x1a63808
008d316f 46 inc esi
008d3170 390d8073f501 cmp [ct_level (01f57380)],ecx ds:01f57380=00000001
--> Stack Back Trace <--
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0401d524 0080989c 00000000 00000000 000004e0 0401d600 disp+work!ab_rfcmode [abrfcsys.c (4282)]
0401d544 0080bb8c 012d2de8 00000008 000004e0 01a252ac disp+work!rabax_init [abrabax.c (4015)]
0401d600 007061fa 012d2e00 012d2de8 00000237 01a252ac disp+work!ab_rabax [abrabax.c (893)]
0401d6a8 0070797a 00000000 00000003 00000000 0401d700 disp+work!resize_0 [abstor.c (567)]
0401d6e0 00547c94 00000000 00000003 00000000 0401d700 disp+work!ab_resize [abstor.c (355)]
0401d720 0053fa76 00000004 00000000 017d3ac0 000004d8 disp+work!rstg_get [saprstg.c (556)]
0401fd84 0040df75 0172d5a4 7c36a42b 0041582e 7ffd8000 disp+work!sapinit [sapinit.c (589)]
0401fd90 0041582e 7ffd8000 00036190 00000001 72616b61 disp+work!DpMemInit [dpxxdisp.c (7914)]
0401ff04 004223ca 00000000 00000000 0401ff60 00401085 disp+work!DpSapEnvInit [dpxxdisp.c (1273)]
0401ff14 00401085 00000002 00036190 00000001 00000000 disp+work!DpMain [dpxxdisp.c (962)]
0401ff60 01099455 00000002 00036190 00032988 016fe000 disp+work!nlsui_main [thxxanf.c (82)]
0401ffc0 77e523cd 00000000 00000000 7ffd8000 896c88e0 disp+work!mainCRTStartup [crtexe.c (398)]
0401fff0 00000000 01099312 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
-
State Dump for Thread Id d68
eax=00000001 ebx=00000103 ecx=fffffffe edx=00030000 esi=00000000 edi=00000000
eip=7c82ed54 esp=058efeb0 ebp=058efef4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:058efeb0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:0990beeb=????????
--> Stack Back Trace <--
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
058efef4 00ff70c7 000006f4 00000000 00000000 000381d8 ntdll!KiFastSystemCallRet
058eff84 7c349565 00000000 00000000 00000000 00038140 disp+work!SigIMsgFunc [signt.c (563)]
058effb8 77e66063 00038140 00000000 00000000 00038140 MSVCR71!endthreadex
058effec 00000000 7c3494f6 00038140 00000000 00000000 kernel32!GetModuleFileNameA
-
-
call clean-up function ...
Shutdown server ...
Stop work processes...
Terminate gui connections
detach from message server
***LOG Q05=> DpHalt, DPStop ( 3212) [dpxxdisp.c 8547]
cleanup event management
cleanup shared memory/semaphores
ERROR => ShmDelete: Invalid shared memory Key=4. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:4. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=14. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:14. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=11. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:11. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=19. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:19. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=33. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:33. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=41. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:41. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=42. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:42. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=43. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:43. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=45. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:45. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=44. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:44. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=54. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:54. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=46. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:46. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=47. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:47. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=64. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:64. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=65. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:65. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=9. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:9. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=8. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:8. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=17. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:17. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=18. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:18. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=6. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:6. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=34. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:34. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=58. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:58. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=7. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:7. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=40. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:40. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=51. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:51. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=30. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:30. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=70. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:70. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=56. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:56. [shmnt.c 756]
ERROR => ShmDelete: Invalid shared memory Key=10. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:10. [shmnt.c 756]
ERROR => EvtRmMgt: Evt Mgt Table not init'd [evtnt.c 351]
ERROR => ShmDelete: Invalid shared memory Key=62. [shmnt.c 682]
ERROR => ShmCleanup: ShmDelete failed for Key:62. [shmnt.c 756]
ERROR => ShmCleanup(62) failed 1 [mpixx.c 3100]
removing request queue
***LOG Q05=> DpHalt, DPStop ( 3212) [dpxxdisp.c 8790]
return from clean-up function ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.