- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- disp+work.exe service is not running
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
disp+work.exe service is not running
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 04-06-2015 8:03 AM
Hi ,
I am trying to log in to the SAP BW system but I cannot. I have checked the services and disp+work.exe service is not running . I have checked the trace long and I have seen some error .
Please find the below log file .
---------------------------------------------------
trc file: "dev_disp", trc level: 1, release: "740"
---------------------------------------------------
sysno 00
sid SRI
systemid 562 (PC with Windows NT)
relno 7400
patchlevel 0
patchno 12
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\BI74SERVER\sapmnt\SRI\SYS\profile\SRI_DVEBMGS00_BI74SERVER
pid 6064
Mon Apr 06 12:12:13 2015
kernel runs with dp version 181000(ext=116000) (@(#) DPLIB-INT-VERSION-181000-UC)
length of sys_adm_ext is 500 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 6064) [dpInit.c 548]
shared lib "dw_xml.dll" version 12 successfully loaded
shared lib "dw_xtc.dll" version 12 successfully loaded
shared lib "dw_stl.dll" version 12 successfully loaded
shared lib "dw_gui.dll" version 12 successfully loaded
shared lib "dw_mdm.dll" version 12 successfully loaded
shared lib "dw_rndrt.dll" version 12 successfully loaded
shared lib "dw_abp.dll" version 12 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-5
use internal message server connection to port 3901
rdisp/snapshot(CREATE): DP_CS_RESOURCES_EXHAUSTED
rdisp/snapshot(PERIOD):300 sec
rdisp/snapshot(LINES):10000 lines
DpCommonParamInit: rdisp/core_file_size = default --> no change
Mon Apr 06 12:12:18 2015
*** 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 4919]
MtxInit: 30000 0 0
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >BI74SERVER_SRI_00 <
DpShMCreate: alloate/attach shared memory (mode=CREATE)
DpShMCreate: sizeof(wp_adm) 22848 (1088)
DpShMCreate: sizeof(tm_adm) 7001232 (34832)
DpShMCreate: sizeof(ca_adm) 432000 (72)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1336064/1455152
DpShMCreate: sizeof(comm_adm) 1455152 (2648)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (80)
DpSockTableSize: max/headSize/ftSize/tableSize=500/16/520064/520080
DpShMCreate: sizeof(sock_adm) 520080 (1016)
DpShMCreate: sizeof(vmc_adm) 0 (3208)
DpShMCreate: sizeof(wall_adm) (ft=41664/fi=67472/hd=64/rec=192)
DpShMCreate: sizeof(amc_rec_adm) (ft=86464/fi=67472/hd=64/rec=408)
DpShMCreate: sizeof(websocket_adm) (ft=38464/hd=64/rec=176)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3936
DpShMCreate: SHM_DP_ADM_KEY (addr: 0000000007D50050, size: 9842016)
DpShMCreate: allocated sys_adm at 0000000007D50250
DpShMCreate: allocated wp_adm_list at 0000000007D61C30
DpShMCreate: allocated wp_adm at 0000000007D61F50
DpShMCreate: allocated tm_adm_list at 0000000007D67A90
DpShMCreate: allocated tm_adm at 0000000007D67CD0
DpShMCreate: allocated ca_adm at 0000000008415360
DpShMCreate: allocated comm_adm at 000000000847ECE0
DpShMCreate: system runs without slock table
DpShMCreate: allocated sock_adm at 00000000085E2310
DpShMCreate: allocated vmc_adm_list at 00000000086614A0
DpShMCreate: system runs without VMC
DpShMCreate: allocated gw_adm at 0000000008661740
DpShMCreate: allocated j2ee_adm at 0000000008661970
DpShMCreate: allocated ca_info at 0000000008662AD0
DpShMCreate: allocated wall_adm (ft) at 0000000008662D10
DpShMCreate: allocated wall_adm (fi) at 000000000866D1D0
DpShMCreate: allocated wall_adm (head) at 000000000867DB60
DpShMCreate: allocated amc_rec_adm (ft) at 000000000867DDA0
DpShMCreate: allocated amc_rec_adm (fi) at 0000000008693160
DpShMCreate: allocated amc_rec_adm (head) at 00000000086A3AF0
DpShMCreate: allocated websocket_adm (ft) at 00000000086A3D30
DpShMCreate: allocated websocket_adm (head) at 00000000086AD570
DpShMCreate: initialized 21 eyes
DpSysAdmIntInit: initialize sys_adm
Scheduler info
--------------
WP info
#dia = 10
#btc = 0
#standby = 0
#max = 21
General Scheduler info
preemptionInfo.isActive = true
preemptionInfo.timeslice = 500
preemptionInfo.checkLoad = true
Prio Class High
maxRuntime[RQ_Q_PRIO_HIGH] = 6000 sec
maxRuntimeHalf[RQ_Q_PRIO_HIGH] = 3000 sec
Prio Class Normal
maxRuntime[RQ_Q_PRIO_NORMAL] = 6000 sec
maxRuntimeHalf[RQ_Q_PRIO_NORMAL] = 3000 sec
maxTicketsForPrio[RQ_Q_PRIO_NORMAL] = 8
withPrioTickets[RQ_Q_PRIO_NORMAL] = true
Prio Class Low
maxRuntime[RQ_Q_PRIO_LOW] = infinite
maxRuntimeHalf[RQ_Q_PRIO_LOW] = infinite
maxTicketsForPrio[RQ_Q_PRIO_LOW] = 8
withPrioTickets[RQ_Q_PRIO_LOW] = true
DpCommAttachTable: attached comm table (header=000000000847ECE0/ft=000000000847ECF0/fi=00000000085C4FF0)
DpSockAttachTable: attached sock table (header=00000000085E2310/ft=00000000085E2320)
MBUF state OFF
DpCommInitTable: init table for 500 entries
DpSockInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 21 initializing ....
<ES> EsILock: use spinlock for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 22937MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 22940MB
<ES> Info: disclaim threshold = 0 MB
<ES> Info: disclaim coasting/alloc = 300 s
<ES> Info: disclaim coasting/free = 0 s
<ES> Info: blockdisclaimsize_KB = 0 KB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
*** ERROR => <EsNT> CreateFileMapping name=Global\ES_SEG_00_008 ,size=2044 MB, error=1455 [esnti.c 1278]
*****************************************************
* Memory diagnostic *
*****************************************************
Systeminformation
------------------------------------------------
Processor-Typ : Processor-Count : 8
Operating System : NT 6.1, Build 7601
Service Pack : Service Pack 1
------------------------------------------------
NT Pagefile Informations
------------------------------------------------
Config. minimum size : 12288000 K
Config. maximum size : 12288000 K
Avail. maximum size : 30693804 K
| Num|Pagefile | Min.Size| Max.Size| Avail.Max| Curr.Size|
|----|------------------------------|----------|----------|----------|----------|
| 1|c:\pagefile.sys | 0 K| 0 K|18405804 K|18147756 K|
| 2|d:\pagefile.sys |12288000 K|12288000 K|12288000 K|12288000 K|
------------------------------------------------
NT Task Manager Informations
------------------------------------------------
Total Handles : 32798
Total Threads : 1191
Total Processes : 119
Commit Charge Total : 61896596 K
Commit Charge Limit : 63987888 K
Commit Charge Peak : 61896596 K
Phys.Memory Total : 33553976 K
Phys.Memory Available : 26397724 K
File Cache : 165976 K
Kernel Memory Total : 412596 K
Kernel Memory Paged : 347004 K
Kernel Memory Nonpaged : 65592 K
------------------------------------------------
Memory usage of current process
------------------------------------------------
Total virt.address space : 0000008589934464 K
Avail.virt.address space : 0000008585683196 K
Private Pages : 0 K
Total heap size : 14024 K
Virtual memory regions : 42 K
Uncommitted heap memory : 5096 K
Allocated heap memory : 7852 K
Moveable heap memory : 0 K
DDE shared heap memory : 4344 K
------------------------------------------------
Memory usage of all processes
-----------------------------
| PID|Image |Instance | Work.Set| WS Peak|Priv.Pages| PP Peak|Pg Fault|
|----|--------------------|-----------|----------|----------|----------|----------|--------|
|1352|sapstartsrv.exe | | 42812 K| 98508 K| 69232 K| 127028 K| 25|
|4068|conhost.exe | | 3288 K| 3288 K| 1592 K| 34832 K| 0|
|5316|conhost.exe | | 3296 K| 3296 K| 1592 K| 34832 K| 0|
|5580|msg_server.EXE | | 16376 K| 16376 K| 18540 K| 18544 K| 4|
|5552|conhost.exe | | 3300 K| 3300 K| 1588 K| 1588 K| 0|
|4724|enserver.EXE | | 113852 K| 113852 K| 839228 K| 839232 K| 28|
|4512|conhost.exe | | 3296 K| 3296 K| 1588 K| 1588 K| 0|
|6064|disp+work.EXE | | 57980 K| 57980 K| 79832 K| 122512 K| 21|
|6020|conhost.exe | | 3296 K| 3296 K| 1588 K| 1588 K| 0|
|5308|igswd.EXE | | 9120 K| 9120 K| 6256 K| 7212 K| 2|
|3344|conhost.exe | | 3320 K| 3320 K| 1588 K| 1588 K| 0|
|4748|igsmux.exe | | 37148 K| 37148 K| 37972 K| 38016 K| 9|
|4476|igspw.exe | | 7828 K| 7828 K| 5352 K| 5352 K| 1|
|5860|igspw.exe | | 7832 K| 7832 K| 5352 K| 5352 K| 1|
|----|--------------------|-----------|----------|----------|----------|----------|--------|
| |Sum | | 312744 K|**********| 1071300 K|**********|********|
Mon Apr 06 12:12:19 2015
*** Error 11 while initializing OS dependent part.
*** ERROR => DpEmInit: EmInit failed (1) [dpInit.c 1407]
*** ERROR => DpMemInit: DpEmInit (-1) [dpInit.c 1271]
*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiIWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=981
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Apr 06 12:12:29 2015
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Mon Apr 06 06:42:29 2015
------------------------------------------------------------
*** WARNING => DpGetSnapshotId: dispatcher not alive [dpxxtool2.c 7192]
Number of preemptions : 0
|No |Pid |Type|State |Cause|Err|Prio|Sess-Key |Sess-Type|Locked|Sem|Time |Program |Cli|User |Action |Action-Info |
|---+------+----+-------+-----+---+----+----------------+---------+------+---+-----+----------------------------------------+---+------------+--------------------+--------------------|
Queue Statistics Mon Apr 06 06:42:29 2015
------------------------------------------------------------
Number of lost wakeup datagrams: 0
Max. number of queue elements : 14000
NOWP: 0 (peak 0, writeCount 0, readCount 0)
DIA: 0 (peak 0, writeCount 0, readCount 0)
UPD: 0 (peak 0, writeCount 0, readCount 0)
ENQ: 0 (peak 0, writeCount 0, readCount 0)
BTC: 0 (peak 0, writeCount 0, readCount 0)
SPO: 0 (peak 0, writeCount 0, readCount 0)
UP2: 0 (peak 0, writeCount 0, readCount 0)
Session queue dump (high priority, 0 elements, peak 0):
Session queue dump (normal priority, 0 elements, peak 0):
Session queue dump (low priority, 0 elements, peak 0):
Logon Table Mon Apr 06 06:42:29 2015
------------------------------------------------------------
No logons/sessions found
CA Blocks
0 ca_blk slots of 6000 in use, 0 currently unowned (in request queues)
NiIWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=981
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Apr 06 12:12:34 2015
NiISelect: TIMEOUT occured (5000ms)
********** SERVER SNAPSHOT 1 (Reason: Shutdown) - begin **********
DpMaxWpRuntimeExplicitelySet: return 6000
DpMaxQuotaExplicitlySet: return -1
Scheduler info
--------------
WP info
#dia = 10
#btc = 0
#standby = 0
#max = 21
General Scheduler info
preemptionInfo.isActive = true
preemptionInfo.timeslice = 500
preemptionInfo.checkLoad = true
Prio Class High
maxRuntime[RQ_Q_PRIO_HIGH] = 6000 sec
maxRuntimeHalf[RQ_Q_PRIO_HIGH] = 3000 sec
Prio Class Normal
maxRuntime[RQ_Q_PRIO_NORMAL] = 6000 sec
maxRuntimeHalf[RQ_Q_PRIO_NORMAL] = 3000 sec
maxTicketsForPrio[RQ_Q_PRIO_NORMAL] = 8
withPrioTickets[RQ_Q_PRIO_NORMAL] = true
Prio Class Low
maxRuntime[RQ_Q_PRIO_LOW] = infinite
maxRuntimeHalf[RQ_Q_PRIO_LOW] = infinite
maxTicketsForPrio[RQ_Q_PRIO_LOW] = 8
withPrioTickets[RQ_Q_PRIO_LOW] = true
Actual tickets in use
actTicketsInUseForPrio[RQ_Q_PRIO_NORMAL] = 0
actTicketsInUseForPrio[RQ_Q_PRIO_LOW] = 0
Queue Statistics Mon Apr 06 06:42:34 2015
------------------------------------------------------------
Number of lost wakeup datagrams: 0
Max. number of queue elements : 14000
NOWP: 0 (peak 0, writeCount 0, readCount 0)
DIA: 0 (peak 0, writeCount 0, readCount 0)
UPD: 0 (peak 0, writeCount 0, readCount 0)
ENQ: 0 (peak 0, writeCount 0, readCount 0)
BTC: 0 (peak 0, writeCount 0, readCount 0)
SPO: 0 (peak 0, writeCount 0, readCount 0)
UP2: 0 (peak 0, writeCount 0, readCount 0)
Session queue dump (high priority, 0 elements, peak 0):
Session queue dump (normal priority, 0 elements, peak 0):
Session queue dump (low priority, 0 elements, peak 0):
CA Blocks
0 ca_blk slots of 6000 in use, 0 currently unowned (in request queues)
********** SERVER SNAPSHOT 1 (Reason: Shutdown) - end **********
*** WARNING => DpGetSnapshotId: dispatcher not alive [dpxxtool2.c 7192]
DpTriggerSapSnapshot: last snapshot created at Thu Jan 01 05:30:00 1970
, skip new snapshot
***LOG Q41=> DpDumpInternalTables, () [dpxxdisp.c 3024]
DpHalt: shutdown server >BI74SERVER_SRI_00 < (normal)
DpUpdateStatusFile: update status file D:\usr\sap\SRI\DVEBMGS00\work\disp+work.status, unique number = 1
DpJ2eeDisableRestart
DpHalt: switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
DpHalt: stop work processes
DpHalt: terminate gui connections
DpHalt: wait for end of work processes
DpHalt: not attached to the message server
DpHalt: cleanup EM
EsCleanup( )
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 6064) [dpInit.c 3329]
DpHalt: Good Bye .....
Please help me to resolve this issue.
Thanks & Regards,
Ramana.
- SAP Managed Tags:
- NW AS Java Administrator (NWA)
Accepted Solutions (0)
Answers (6)
Answers (6)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Venkata,
Memory problems, are always interesting to solve. Rather than implementing certain parameters randomly based on suggestion of parameters, I recommend you try and work out what is causing the issue, I had bit of time on my hands today, so here it goes.
From your trace I can see the following:
Your RAM - 32 GB (approx)
Your Windows Paging File Size - 30 GB ( c:\pagefile.sys - 18GB, d:\pagefile.sys - 12GB)
Your total allowable VMM space is: RAM + Paging = 62 GB - this is total for your Windows OS + SAP Application, Windows Server OS will easily eat up atleast 2GB of the total space, so effectively you have 60 GB available for SAP.
Now lets calculate VMM for SAP.
SAP on Windows relies on parameter PHYS_MEMSIZE, if its not set and only em* parameters as set, the kernel assumes PHYS_MEMSIZE to be = RAM.
Since, in the trace we can't see it, I am assuming you haven't set it. SAP kernel will assume it to be 32GB
For kernel 7.20 you have to set it to 20% of RAM. for kernel 7.40 and above you have to set it equal to RAM.
88416 - Zero administration memory management for the ABAP server
1518419 - Page file and virtual memory required by the SAP system
The SAP VMM requirement can be calculated using the formulas in the document below:
Virtual Memory Required by SAP System Components | SCN
The formula would be(assuming you have ABAP only central instance) :
Approx. 500 MB + 1 to 2 times PHYS_MEMSIZE + 2.5 GB + 250 MB per work process
The work processes seem to be 21.
WP info
#dia = 10
#btc = 0
#standby = 0
#max = 21
If you work that out for your application server, the SAP only VMM requirement is: 72GB
Add 2GB to 4GB of VMM for Windows and other applications, your worst case requirement is 74GB-76GB.
If you round that off to 80GB, you are about 20GB short of Windows Pagefile(assuming you can't increase your RAM).
A plausible solution would be either of the following:
- Reduce work processes if you can (if they were increased recently)
- Set PHYS_MEMSIZE as per your kernel and note 88416 and observe the changes in VMM and further refine parameters accordingly.
- Add an additional pagefile in Windows (ask your OS admin to do it).
Hope that helps.
Regards,
Siddhesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I will add on to what Gaurav and Siddhesh are saying, as I concur that the probable issue could be with the PHYS_MEMSIZE parameter (or lack of one).
Is this a central system, with database instance and central instance on the same host? Or is it a central instance with the database isolated to a standalone, separate server? Also, is it the only SAP instance running on the host, or are there more than one? All of these factors influence how you should set PHYS_MEMSIZE.
I'm not sure I agree with the statement that it should be set to 20% of RAM on a 7.20 kernel, though.
If there is no database instance on this host, and there is only a single SAP instance, then normally you would not need to set PHYS_MEMSIZE (i.e., you can leave it at default, which is PHYS_MEMSIZE = RAM, or 32 GB). It would be important, in this case, to ensure that some of the other memory parameters are also left at default, so that the Zero-Admin Memory Management can do its work. I don't think you have too many work processes set, given the amount of memory, so I don't think that's the problem. From the configuration, my guess is that this is actually a dialog instance, and not the central instance, and not the database instance. Is that correct?
So, if that's the case, you should have plenty of pagefile for your operation. Perhaps you are having memory hardware issues on the box?
If you do have more than one instance on the same host, then you must set PHYS_MEMSIZE to divid up the memory between them. It will not work to have them each think they have all the memory to themselves.
Setting PHYS_MEMSIZE to 50% of the RAM and restarting to see if this solves the problem is a good troubleshooting step. That doesn't mean this is the right setting for productive use, but it will give you some more information.
Regards,
Matt
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Venkata,
Could you please execute sappfpar and see if there is any recommendations?
Switch user to sriadm
sappfpar check pf=\sapmnt\SRI\SYS\profile\SRI_DVEBMGS00_BI74SERVER
Regards,
Serhat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Ramana
I think you can perform the full system restart and then try again. is this any port is getting block by antivirus software?
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
To avoid the issue adjust the parameter PHYS_MEMSIZE with half of the physical memory of the system & check again.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello ,
Issue seems to be with Page Memory.
May be you could try increasing page memory and check if it helps.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
| 1278] |
For the issue i would like to suggest you to follow resolution under SAP KBA 1997262 - The shadow instance won't start up. System dev_w* trace files highlight error message 145...
as the KBA suggesting this issue relates with memory parameters & you need to fine tune to get rid of it.
Hope this will help you.
Good luck !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP B1 Service layer: windows service permissions in Technology Q&A
- Kyma Integration with SAP Cloud Logging. Part 2: Let's ship some traces in Technology Blogs by SAP
- Capture Your Own Workload Statistics in the ABAP Environment in the Cloud in Technology Blogs by SAP
- CAP Extensibility: Exended Properties displayed in UI but missing in Requests in Technology Q&A
- Top Picks: Innovations Highlights from SAP Business Technology Platform (Q1/2024) in Technology Blogs by SAP
| User | Count |
|---|---|
| 91 | |
| 10 | |
| 10 | |
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.