Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SAPMMC ERROR: Disp is running, but Message server untraceble

Dear SAP Gurus

I have installed mySAPERP 2004(ECC5.0) on Windows Server 2003 SP2 with Oracle Database 9.2.0.6

It installed well but when i stated the Instance in SAP MMC it is giving the yellow light with the error

disp+work.exe dispatcher running but message server untraceble

I have checked the dev_disp file for error, this is the content

trc file: "dev_disp", trc level: 1, release: "640"

-

Thu Apr 02 14:16:12 2009

kernel runs with dp version 127(ext=102) (@(#) DPLIB-INT-VERSION-127)

length of sys_adm_ext is 312 bytes

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 10

intno 20020600

make: multithreaded, ASCII

pid 400

***LOG Q00=> DpSapEnvInit, DPStart (00 400) [dpxxdisp.c 1093]

shared lib "dw_xml.dll" version 10 successfully loaded

shared lib "dw_xtc.dll" version 10 successfully loaded

shared lib "dw_stl.dll" version 10 successfully loaded

shared lib "dw_gui.dll" version 10 successfully loaded

Thu Apr 02 14:16:17 2009

      • WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3880]

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: JAVA is not active

DpShMCreate: sizeof(wp_adm) 1656 (828)

DpShMCreate: sizeof(tm_adm) 2083168 (10364)

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 (320)

DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

DpShMCreate: SHM_DP_ADM_KEY (addr: 06100040, size: 2363768)

      • ERROR => DpShMCreate: ShmCreate SHM_DP_CA_KEY(rc=4) [dpxxca.c 181]

      • ERROR => DpIPCInit2: DpShMCreate [dpxxtool2.c 427]

      • DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

      • DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

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=400)

When : 4/2/2009 14:16:17.968

Threads : 2

-

Computer Name : TBG-TEST

User Name : SAPServiceTBG

-

Number of Processors: 2

Processor Type: x86 Family 15 Model 4 Stepping 10

Windows Version : 5.2 Current Build: 3790

-

State Dump for Thread Id f70

eax=00396468 ebx=00000000 ecx=0039647c edx=00000000 esi=00395f4c edi=00395f20

eip=7c8285ec esp=02eeef1c ebp=02eeef2c 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 : DpWpKill

004386bb a11cee9e01 mov eax,[wp_adm (019eee1c)] ds:019eee1c=00000000

004386c0 56 push esi

004386c1 57 push edi

004386c2 8b7c240c mov edi,[esp+0xc] ss:05ddd397=????????

004386c6 8bf7 mov esi,edi

004386c8 69f63c030000 imul esi,esi,0x33c

FAULT-> 004386ce 837c064800 cmp dword ptr [esieax0x48],0x0 ds:032848e3=00000000

004386d3 7f72 jg DpWpKill+0x8c (00438747)

004386d5 833d68c3a60101 ds:01a6c368=00000003

cmp dword ptr [ct_level (01a6c368)],0x1

004386dc 0f8c3f030000 jl DpWpKill+0x366 (00438a21)

004386e2 e8c924bc00 call VmcResetActStack (00ffabb0)

004386e7 6a5c push 0x5c

004386e9 685c8b4f01 push 0x14f8b5c

004386ee ff1534d50301 ds:0103d534=7c343868

call dword ptr [_imp__strrchr (0103d534)]

004386f4 85c0 test eax,eax

004386f6 59 pop ecx

004386f7 59 pop ecx

004386f8 6847090000 push 0x947

--> Stack Back Trace <--

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name

02eef968 00411b97 00000000 00000005 014dfb54 7c36a42b disp+work!DpWpKill [dpxxtool.c (2372)]

02eefd88 0041528b 014dff1c 014dfb54 7ffd7000 00395f08 disp+work!DpFatalErr [dpxxdisp.c (14923)]

02eeff04 00421ac8 00000000 00000000 02eeff60 00401059 disp+work!DpSapEnvInit [dpxxdisp.c (1228)]

02eeff14 00401059 00000002 00395f08 00000001 00000000 disp+work!DpMain [dpxxdisp.c (957)]

02eeff60 01018a33 00000002 00395f08 00392aa8 014d8000 disp+work!main [thxxanf.c (58)]

02eeffc0 77e6f23b 00000000 00000000 7ffd7000 00000000 disp+work!mainCRTStartup [crtexe.c (398)]

02eefff0 00000000 010188f0 00000000 00905a4d 00000003 kernel32!ProcessIdToSessionId

-

State Dump for Thread Id 15c

eax=0608feac ebx=00000103 ecx=4fb18dfb edx=0608feba esi=00000000 edi=00000000

eip=7c8285ec esp=0608feb0 ebp=0608fef4 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

7c8285ec c3 ret

7c8285ed 8da42400000000 lea esp,[esp] ss:0608feb0=7c8270fb

7c8285f4 8d642400 lea esp,[esp] ss:08f7e32b=????????

--> Stack Back Trace <--

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name

0608fef4 00f7c91e 000006b0 00000000 00000000 00396888 ntdll!KiFastSystemCallRet

0608ff84 7c349565 00000000 00000000 00000000 003967f0 disp+work!SigIMsgFunc [signt.c (559)]

0608ffb8 77e64829 003967f0 00000000 00000000 003967f0 MSVCR71!endthreadex

0608ffec 00000000 7c3494f6 003967f0 00000000 00000000 kernel32!GetModuleHandleA

-

-

Thu Apr 02 14:16:18 2009

call clean-up function ...

SigICallExitRoutine: call exithandler (DpHalt)

Shutdown server ...

Switch off Shared memory profiling

ShmProtect( 57, 3 )

ShmProtect(SHM_PROFILE, SHM_PROT_RW

ShmProtect( 57, 1 )

ShmProtect(SHM_PROFILE, SHM_PROT_RD

detach from message server

***LOG Q05=> DpHalt, DPStop ( 400) [dpxxdisp.c 8460]

cleanup event management

      • ERROR => EvtRmMgt: Evt Mgt Table not init'd [evtnt.c 351]

(didn't work)

cleanup shared memory/semaphores

ShmCleanup SHM_SYS_ADM_KEY

ShmCleanup SHM_DP_ADM_KEY

ShmCleanup SHM_DP_CA_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=3. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:3. [shmnt.c 756]

ShmCleanup SHM_PF_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=4. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:4. [shmnt.c 756]

ShmCleanup SHM_PRES_BUF

      • ERROR => ShmDelete: Invalid shared memory Key=14. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:14. [shmnt.c 756]

ShmCleanup SHM_CALI_BUFFER

      • ERROR => ShmDelete: Invalid shared memory Key=11. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:11. [shmnt.c 756]

ShmCleanup SHM_DB_TBUFF

      • ERROR => ShmDelete: Invalid shared memory Key=19. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:19. [shmnt.c 756]

ShmCleanup SHM_DB_TBUFF_P

      • ERROR => ShmDelete: Invalid shared memory Key=33. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:33. [shmnt.c 756]

ShmCleanup SHM_DB_STBUFF

      • ERROR => ShmDelete: Invalid shared memory Key=41. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:41. [shmnt.c 756]

ShmCleanup SHM_DB_TTBUFF

      • ERROR => ShmDelete: Invalid shared memory Key=42. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:42. [shmnt.c 756]

ShmCleanup SHM_DB_FTBUFF

      • ERROR => ShmDelete: Invalid shared memory Key=43. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:43. [shmnt.c 756]

ShmCleanup SHM_DB_SNTBUFF

      • ERROR => ShmDelete: Invalid shared memory Key=45. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:45. [shmnt.c 756]

ShmCleanup SHM_DB_IRBUFF

      • ERROR => ShmDelete: Invalid shared memory Key=44. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:44. [shmnt.c 756]

ShmCleanup SHM_DB_OBJ_BUFFER

      • ERROR => ShmDelete: Invalid shared memory Key=54. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:54. [shmnt.c 756]

ShmCleanup SHM_DB_SYNC

      • ERROR => ShmDelete: Invalid shared memory Key=46. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:46. [shmnt.c 756]

ShmCleanup SHM_DB_CUA_BUFFER

      • ERROR => ShmDelete: Invalid shared memory Key=47. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:47. [shmnt.c 756]

ShmCleanup SHM_DB_OTR_BUFFER

      • ERROR => ShmDelete: Invalid shared memory Key=64. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:64. [shmnt.c 756]

ShmCleanup SHM_DB_ESM_BUFFER

      • ERROR => ShmDelete: Invalid shared memory Key=65. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:65. [shmnt.c 756]

ShmCleanup SHM_ROLL_AREA_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=9. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:9. [shmnt.c 756]

ShmCleanup SHM_PAGING_AREA_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=8. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:8. [shmnt.c 756]

ShmCleanup SHM_ROLL_ADM_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=17. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:17. [shmnt.c 756]

ShmCleanup SHM_PAGING_ADM_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=18. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:18. [shmnt.c 756]

ShmCleanup SHM_PXA_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=6. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:6. [shmnt.c 756]

ShmCleanup SHM_ENQ_TABLE_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=34. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:34. [shmnt.c 756]

ShmCleanup SHM_ENQID_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=58. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:58. [shmnt.c 756]

ShmCleanup SHM_VB_ADM_KEY

      • ERROR => ShmDelete: Invalid shared memory Key=7. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:7. [shmnt.c 756]

ShmCleanup SHM_DB_POOL

      • ERROR => ShmDelete: Invalid shared memory Key=40. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:40. [shmnt.c 756]

ShmCleanup SHM_EM_ADM

      • ERROR => ShmDelete: Invalid shared memory Key=51. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:51. [shmnt.c 756]

ShmCleanup SHM_MSBUF

      • ERROR => ShmDelete: Invalid shared memory Key=52. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:52. [shmnt.c 756]

ShmCleanup SHM_THRUN_ADM_KEY(th run adm)

      • ERROR => ShmDelete: Invalid shared memory Key=30. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:30. [shmnt.c 756]

ShmCleanup SHM_JAVA

      • ERROR => ShmDelete: Invalid shared memory Key=70. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:70. [shmnt.c 756]

ShmCleanup SHM_PF_AS_KEY(Appl.Statistics)

      • ERROR => ShmDelete: Invalid shared memory Key=56. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:56. [shmnt.c 756]

ShmCleanup SHM_POOL_0

      • ERROR => ShmDelete: Invalid shared memory Key=10. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:10. [shmnt.c 756]

ShmCleanup SHM_PROFILE

MiCleanup:

      • ERROR => EvtRmMgt: Evt Mgt Table not init'd [evtnt.c 351]

EvtRmMgt() failed 1

      • 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 3075]

MpiCleanup() -> 1

removing Semaphore-Management

removing request queue

      • ERROR => ShmDelete: Invalid shared memory Key=31. [shmnt.c 682]

      • ERROR => ShmCleanup: ShmDelete failed for Key:31. [shmnt.c 756]

      • ERROR => DpRqIQRemove: ShmDelete [dpxxqueu.c 430]

closing connect handles (dgm + tcp)

***LOG Q05=> DpHalt, DPStop ( 400) [dpxxdisp.c 8672]

      • shutdown completed - server stopped ***

return from clean-up function ...

Kindly help me on this

Thank you

Satyasaikumar P.

Former Member
April 02, 2009 at 13:35 PM
0 Likes
Not what you were looking for? View more on this topic or Ask a question

2 replies