cancel
Showing results for 
Search instead for 
Did you mean: 

Dispatcher is not coming up

Former Member
0 Kudos

Hi all,

One of the apps in the production system is not coming up after the windows patching, there are 2 servers in the same box the other one came up fine with no issues.

Even the Work process log is also not generated.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

-


trc file: "dev_disp", trc level: 1, release: "46D"

-


Tue Jun 21 15:11:31 2011

relno 4640

patchlevel 0

patchno 2513

intno 0

pid 13548

***LOG Q00=> DpSapEnvInit, DPStart (71 13548) [dpxxdisp.c 921]

Tue Jun 21 15:11:35 2011

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

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

MtxInit: -2 0 0

DpIPCInit: start server >xxxx_71 <

      • ERROR => DpShMCreate: ShmCreate SHM_DP_ADM_KEY [dpxxtool2.c 1335]

      • ERROR => DpIPCInit: DpShMCreate [dpxxtool2.c 409]

      • DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit

      • DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

call semaphore clean-up function ...

***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c 390]

-


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

When : 6/21/2011 15:11:35.782

Threads : 2

-


Computer Name xxxxxx

User Name : SAPServicexxx

-


Number of Processors: 32

Processor Type: EM64T Family 6 Model 46 Stepping 6

Windows Version : 5.2 Current Build: 3790

-


Stack Dump for Thread Id 3ca8

eax=00000000 ebx=00000003 ecx=016ea020 edx=0319f68c esi=00000000 edi=00000000

eip=00427bcb esp=0319fdf8 ebp=00000000 iopl=0 nv up ei pl nz na po nc

cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206

function : <nosymbols>

00427bb0 ff742404 push dword ptr [esp+0x4] ss:0633e6a3=????????

00427bb4 ffd0 call eax

00427bb6 59 pop ecx

00427bb7 c3 ret

00427bb8 a1bcf06c01 mov eax,[016cf0bc] ds:016cf0bc=00000000

00427bbd 56 push esi

00427bbe 57 push edi

00427bbf 8b7c240c mov edi,[esp+0xc] ss:0633e6a3=????????

00427bc3 8bf7 mov esi,edi

00427bc5 69f698020000 imul esi,esi,0x298

FAULT-> 00427bcb 837c064800 cmp dword ptr [esieax0x48],0x0 ds:0319e8ab=467f0048

00427bd0 7f46 jg 00427c18

00427bd2 833db89f6e0101 cmp dword ptr [016e9fb8],0x1 ds:016e9fb8=00000003

00427bd9 0f8c45030000 jl 00427f24

00427bdf e8ad910a00 call 004d0d91

00427be4 68310a0000 push 0xa31

00427be9 689060d400 push 0xd46090

00427bee e8e6d0ffff call 00424cd9

00427bf3 59 pop ecx

00427bf4 50 push eax

00427bf5 689c60d400 push 0xd4609c

00427bfa 68bc9f6e01 push 0x16e9fbc

--> Stack Back Trace <--

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

00000000 00000000 00000000 00000000 00000000 00000000 disp+work!<nosymbols>

-


Stack Dump for Thread Id 2f70

eax=00000000 ebx=0036f190 ecx=00000000 edx=00000000 esi=77bd0888 edi=00000000

eip=7d61cd3e esp=0769fc78 ebp=0769fcb8 iopl=0 nv up ei pl nz na pe nc

cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202

function : NtFsControlFile

7d61cd29 b836000000 mov eax,0x36

7d61cd2e b91b000000 mov ecx,0x1b

7d61cd33 8d542404 lea edx,[esp+0x4] ss:0a83e523=????????

7d61cd37 64ff15c0000000 call dword ptr fs:[000000c0] fs:000000c0=????????

7d61cd3e c22800 ret 0x28

--> Stack Back Trace <--

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

0769fcb8 00c38ed8 000004f4 00000000 00000000 0036f0f8 ntdll!NtFsControlFile

0769ff84 77bcb530 00000000 00000000 00000000 0036f190 disp+work!<nosymbols>

0769ffb8 7d4dfe37 0036f190 00000000 00000000 0036f190 MSVCRT!endthreadex

0769ffec 00000000 77bcb4bc 0036f190 00000000 00000000 kernel32!FlsSetValue

-


-


call clean-up function ...

SigICallExitRoutine: call exithandler (DpHalt)

DpHalt: shutdown server >mudpap01_UDP_71 <

Switch off Shared memory profiling

not attached to the message server

***LOG Q05=> DpHalt, DPStop ( 13548) [dpxxdisp.c 7267]

removing Event-Managment

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

(didn't work)

ShmCleanup SHM_SYS_ADM_KEY

ShmCleanup SHM_DP_ADM_KEY

      • ERROR => ShmDelete: Inv. Key=2 [shmnt.c 676]

      • ERROR => ShmCleanup: ShmDelete failed for Key: 2 [shmnt.c 747]

ShmCleanup SHM_DP_CA_KEY

      • ERROR => ShmDelete: Inv. Key=3 [shmnt.c 676]

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

ShmCleanup SHM_PF_KEY

      • ERROR => ShmDelete: Inv. Key=4 [shmnt.c 676]

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

ShmCleanup SHM_PRES_BUF

      • ERROR => ShmDelete: Inv. Key=14 [shmnt.c 676]

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

ShmCleanup SHM_CALI_BUFFER

      • ERROR => ShmDelete: Inv. Key=11 [shmnt.c 676]

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

ShmCleanup SHM_DB_TBUFF

      • ERROR => ShmDelete: Inv. Key=19 [shmnt.c 676]

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

ShmCleanup SHM_DB_TBUFF_P

      • ERROR => ShmDelete: Inv. Key=33 [shmnt.c 676]

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

ShmCleanup SHM_DB_STBUFF

      • ERROR => ShmDelete: Inv. Key=41 [shmnt.c 676]

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

ShmCleanup SHM_DB_TTBUFF

      • ERROR => ShmDelete: Inv. Key=42 [shmnt.c 676]

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

ShmCleanup SHM_DB_FTBUFF

      • ERROR => ShmDelete: Inv. Key=43 [shmnt.c 676]

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

ShmCleanup SHM_DB_SNTBUFF

      • ERROR => ShmDelete: Inv. Key=45 [shmnt.c 676]

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

ShmCleanup SHM_DB_IRBUFF

      • ERROR => ShmDelete: Inv. Key=44 [shmnt.c 676]

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

ShmCleanup SHM_DB_OBJ_BUFFER

      • ERROR => ShmDelete: Inv. Key=54 [shmnt.c 676]

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

ShmCleanup SHM_ROLL_AREA_KEY

      • ERROR => ShmDelete: Inv. Key=9 [shmnt.c 676]

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

ShmCleanup SHM_PAGING_AREA_KEY

      • ERROR => ShmDelete: Inv. Key=8 [shmnt.c 676]

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

ShmCleanup SHM_ROLL_ADM_KEY

      • ERROR => ShmDelete: Inv. Key=17 [shmnt.c 676]

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

ShmCleanup SHM_PAGING_ADM_KEY

      • ERROR => ShmDelete: Inv. Key=18 [shmnt.c 676]

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

ShmCleanup SHM_PXA_KEY

      • ERROR => ShmDelete: Inv. Key=6 [shmnt.c 676]

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

ShmCleanup SHM_ENQ_TABLE_KEY

      • ERROR => ShmDelete: Inv. Key=34 [shmnt.c 676]

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

ShmCleanup SHM_ENQID_KEY

      • ERROR => ShmDelete: Inv. Key=58 [shmnt.c 676]

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

ShmCleanup SHM_VB_ADM_KEY

      • ERROR => ShmDelete: Inv. Key=7 [shmnt.c 676]

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

ShmCleanup SHM_DB_POOL

      • ERROR => ShmDelete: Inv. Key=40 [shmnt.c 676]

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

ShmCleanup SHM_EM_ADM

      • ERROR => ShmDelete: Inv. Key=51 [shmnt.c 676]

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

ShmCleanup SHM_MSBUF

      • ERROR => ShmDelete: Inv. Key=52 [shmnt.c 676]

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

ShmCleanup SHM_THRUN_ADM_KEY(th run adm)

      • ERROR => ShmDelete: Inv. Key=30 [shmnt.c 676]

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

ShmCleanup SHM_PF_AS_KEY(Appl.Statistics)

      • ERROR => ShmDelete: Inv. Key=56 [shmnt.c 676]

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

ShmCleanup SHM_POOL_0

      • ERROR => ShmDelete: Inv. Key=10 [shmnt.c 676]

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

ShmCleanup SHM_PROFILE

removing Semaphore-Management

removing Request Queue

      • ERROR => ShmDelete: Inv. Key=31 [shmnt.c 676]

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

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

closing connect handles (dgm + tcp)

***LOG Q05=> DpHalt, DPStop ( 13548) [dpxxdisp.c 7454]

return from clean-up function ...

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Changed the extendend memory and other parameters still not able to bring it up...

Please suggest...

Thanks,

Subhash.G

Accepted Solutions (1)

Accepted Solutions (1)

paul_power
Active Contributor
0 Kudos

Hi,

Since all the errors are of type

ERROR => ShmCleanup: ShmDelete failed for Key

please clean IPC or restart the server

(restartig the server would be best if this is possible at all)

to ensure the shared memory is cleared

Regards,

Paul

Answers (2)

Answers (2)

former_member185031
Active Contributor
0 Kudos

You can try this also.

1.Stop the SAP Instance

2.Stop the Services SAP_SID_sysnr through service.msc

3.Start the Sap instance

Regards,

Subhash

Former Member
0 Kudos

Hi,

I have not found any service with SAP_SID_sysnr.

Not found any errors in the event viewer which are related to this instance...

We are planning to restart the server in the weekend as a last option ...

Thanks,

Subhash.G

Former Member
0 Kudos

Hi all,

Finally i am able to fix the issue and the apps is up now.

I have checked with my windows admin and killed all the process which are with that apps ...

Former Member
0 Kudos

hi,

Go to your profile directory and do this

sappfpar pf=<instance profile> check

it will display the errors and warning .. please paste that ...

I think you have to increase the sharedmemory parameters ...

Thanks,

Deepthi

nirmal_konchada
Active Contributor
0 Kudos

Hi,

Try to perform a shared memory cleanup and then start SAP

cleanipc <instance no.> remove

Regards,

Nirmal.K

Former Member
0 Kudos

Hi,

sappfpar result , no errors and warnings reported.

+++++++++++++++++++++++++++++++++++++++++++++++

Shared memory disposition overview

================================================================

Key: 1 Size: 2000 ( 0.0 MB) System administration

Key: 2 Size: 18828644 ( 18.0 MB) Disp. administration tables

Key: 3 Size: 178144000 ( 169.9 MB) Disp. communication areas

Key: 4 Size: 541048 ( 0.5 MB) statistic area

Key: 5 Size: 4096 ( 0.0 MB) SCSA area

Key: 6 Size: 851968000 ( 812.5 MB) ABAP program buffer

Key: 7 Size: 14838 ( 0.0 MB) Update task administration

Key: 8 Size: 134217828 ( 128.0 MB) Paging buffer

Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer

Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer

Key: 12 Size: 3000000 ( 2.9 MB) TemSe Char-Code convert Buf.

Key: 13 Size: 10500000 ( 10.0 MB) Alert Area

Key: 14 Size: 58500096 ( 55.8 MB) Presentation buffer

Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring

Key: 17 Size: 753764 ( 0.7 MB) Roll administration

Key: 18 Size: 458852 ( 0.4 MB) Paging adminitration

Key: 19 Size: 460000256 ( 438.7 MB) Table-buffer

Key: 30 Size: 91500 ( 0.1 MB) Taskhandler Runtime Admin

Key: 31 Size: 4206000 ( 4.0 MB) Dispatcher request queue

Key: 33 Size: 61440000 ( 58.6 MB) Table buffer, part.buffering

Key: 41 Size: 9010000 ( 8.6 MB) DB statistics buffer

Key: 42 Size: 52900592 ( 50.4 MB) DB TTAB buffer

Key: 43 Size: 87894392 ( 83.8 MB) DB FTAB buffer

Key: 44 Size: 46934392 ( 44.8 MB) DB IREC buffer

Key: 45 Size: 29526392 ( 28.2 MB) DB short nametab buffer

Key: 46 Size: 20480 ( 0.0 MB) DB sync table

Key: 47 Size: 71681024 ( 68.4 MB) DB CUA buffer

Key: 48 Size: 300000 ( 0.3 MB) Number range buffer

Key: 49 Size: 2769392 ( 2.6 MB) Spool admin (SpoolWP+DiaWP)

Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.

Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer

Key: 54 Size: 262152192 ( 250.0 MB) Export/Import buffer

Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist

Key: 57 Size: 1048576 ( 1.0 MB) Profil in shared Memory

Key: 58 Size: 4096 ( 0.0 MB) EnqId

Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0

Nr of operating system shared memory segments: 36

Shared memory resource requirements estimated

================================================================

Total Nr of shared segments required.....: 36

Shared memory segment size required min..: 851968000 ( 812.5 MB)

Swap space requirements estimated

================================================

Shared memory....................: 2370.2 MB

Processes........................: 468.3 MB

Extended Memory .................: 10260.0 MB

-


Total, minimum requirement.......: 13098.4 MB

Process local heaps, worst case..: 1908.0 MB

Total, worst case requirement....: 15006.4 MB

Errors detected..................: 0

Warnings detected................: 0

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

We are windows 2003 with sqlserver 2005, is there any equal command as cleanipc in UNIX for windows to clean the share memory .

Thanks,

Subhash.G

Nibu
Contributor
0 Kudos

Hi

Did you check the system logs, both application and security. Normally a restart will resolve such issue . As suggested , stop the instances , restart the system , stop if any virus scanners firewalls etc for the time being and then try to start the application.

Regards,

Nibu Antony