SAP Dialog Instance cannot up

[Former Member]

Hi All,

FYI, my SAP PRD running on 3 tier SAP server configuration. Yesterday, after stop the instances, i start the services.

So far 2 servers instances (CI & DI) can be started, but 1 DI server could not be started.I had restart the dialog instance server but the the SAP still can't start.

Below is the log file for DEV_DISP:

-

---

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

-

---

Fri Mar 26 15:07:41 2010

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

length of sys_adm_ext is 312 bytes

sysno 03

sid PRD

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 129

intno 20020600

make: multithreaded, ASCII

pid 3524

***LOG Q00=> DpSapEnvInit, DPStart (03 3524) [dpxxdisp.c 1098]

Fri Mar 26 15:07:42 2010

shared lib "dw_xml.dll" version 129 successfully loaded

shared lib "dw_xtc.dll" version 129 successfully loaded

shared lib "dw_stl.dll" version 129 successfully loaded

shared lib "dw_gui.dll" version 129 successfully loaded

shared lib "dw_mdm.dll" version 129 successfully loaded

Fri Mar 26 15:07:46 2010

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

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpIPCInit2: start server >bashful_PRD_03 <

DpShMCreate: sizeof(wp_adm) 18216 (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: 05830040, size: 2677040)

DpShMCreate: allocated sys_adm at 05830040

DpShMCreate: allocated wp_adm at 058317D0

DpShMCreate: allocated tm_adm_list at 05835EF8

DpShMCreate: allocated tm_adm at 05835F20

DpShMCreate: allocated wp_ca_adm at 05A7AF60

DpShMCreate: allocated appc_ca_adm at 05A7F5B0

DpShMCreate: allocated comm_adm_list at 05A80D20

DpShMCreate: allocated comm_adm at 05A80D38

DpShMCreate: allocated vmc_adm_list at 05AAFB38

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 05AAFB60

DpShMCreate: allocated wall_adm at 05AAFB68

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

Fri Mar 26 15:07:47 2010

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 12499 blocks reserved for free list.

ES initialized.

Fri Mar 26 15:07:48 2010

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( sneezyapp) [dpxxdisp.c 9915]

DpStartStopMsg: send start message (myname is >bashful_PRD_03 <)

DpStartStopMsg: start msg sent

Fri Mar 26 15:07:49 2010

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 40000000 for monitoring segment.

CCMS: start to initalize 3.X shared alert area (first segment).

Release check o.K.

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]

Fri Mar 26 15:08:28 2010

• ERROR => W0 (pid 2592) died [dpxxdisp.c 12414]

• ERROR => W1 (pid 2596) died [dpxxdisp.c 12414]

• ERROR => W2 (pid 2624) died [dpxxdisp.c 12414]

• ERROR => W3 (pid 2632) died [dpxxdisp.c 12414]

• ERROR => W4 (pid 2644) died [dpxxdisp.c 12414]

• ERROR => W5 (pid 2648) died [dpxxdisp.c 12414]

• ERROR => W6 (pid 2672) died [dpxxdisp.c 12414]

• ERROR => W7 (pid 2680) died [dpxxdisp.c 12414]

• ERROR => W8 (pid 2700) died [dpxxdisp.c 12414]

• ERROR => W9 (pid 2708) died [dpxxdisp.c 12414]

• ERROR => W10 (pid 2712) died [dpxxdisp.c 12414]

• ERROR => W11 (pid 2720) died [dpxxdisp.c 12414]

my types changed after wp death/restart 0x9b --> 0x9a

• ERROR => W12 (pid 2736) died [dpxxdisp.c 12414]

• ERROR => W13 (pid 2744) died [dpxxdisp.c 12414]

• ERROR => W14 (pid 2764) died [dpxxdisp.c 12414]

• ERROR => W15 (pid 2788) died [dpxxdisp.c 12414]

• ERROR => W16 (pid 2812) died [dpxxdisp.c 12414]

• ERROR => W19 (pid 2852) died [dpxxdisp.c 12414]

• ERROR => W20 (pid 2864) died [dpxxdisp.c 12414]

my types changed after wp death/restart 0x9a --> 0x92

• ERROR => W21 (pid 2892) died [dpxxdisp.c 12414]

my types changed after wp death/restart 0x92 --> 0x82

And below is the file for DEV_W0:

-

---

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

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, M

*

B

B Fri Mar 26 15:07:50 2010

B create_con (con_name=R/3)

B Loading DB library 'D:\usr\sap\PRD\D03\exe\dbmssslib.dll' ...

B Library 'D:\usr\sap\PRD\D03\exe\dbmssslib.dll' loaded

B Version of 'D:\usr\sap\PRD\D03\exe\dbmssslib.dll' is "640.00", patchlevel (0.126)

B New connection 0 created

M sysno 03

M sid PRD

M systemid 560 (PC with Windows NT)

M relno 6400

M patchlevel 0

M patchno 129

M intno 20020600

M make: multithreaded, ASCII

M pid 2592

M

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2592) [dpxxdisp.c 1158]

I MtxInit: -2 0 0

M DpSysAdmExtCreate: ABAP is active

M DpShMCreate: sizeof(wp_adm) 18216 (828)

M DpShMCreate: sizeof(tm_adm) 2379840 (11840)

M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

M DpShMCreate: sizeof(comm_adm) 192000 (384)

M DpShMCreate: sizeof(vmc_adm) 0 (364)

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

M DpShMCreate: SHM_DP_ADM_KEY (addr: 06030040, size: 2677040)

M DpShMCreate: allocated sys_adm at 06030040

M DpShMCreate: allocated wp_adm at 060317D0

M DpShMCreate: allocated tm_adm_list at 06035EF8

M DpShMCreate: allocated tm_adm at 06035F20

M DpShMCreate: allocated wp_ca_adm at 0627AF60

M DpShMCreate: allocated appc_ca_adm at 0627F5B0

M DpShMCreate: allocated comm_adm_list at 06280D20

M DpShMCreate: allocated comm_adm at 06280D38

M DpShMCreate: allocated vmc_adm_list at 062AFB38

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 062AFB60

M DpShMCreate: allocated wall_adm at 062AFB68

X EmInit: MmSetImplementation( 2 ).

X <ES> client 0 initializing ....

X Using implementation flat

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

M

M Fri Mar 26 15:07:51 2010

M calling db_connect ...

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'D:\usr\sap\PRD\D03\exe\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 126

C patchcomment MSSQL: Unknown table in FOR ALL ENTRIES (945910)

C Network connection used from BASHFUL to kingdomdb using tcp:kingdomdb

C CopyLocalParameters: dbuser is 'prd'

C Provider SQLNCLI could not be initialized. See note #734034 for more information.

C Using provider SQLOLEDB instead.

C OpenOledbConnection: MARS property was not set.

C

C Fri Mar 26 15:07:54 2010

C Provider Release:08.10.1830

C Provider SQLNCLI could not be initialized. See note #734034 for more information.

C Using provider SQLOLEDB instead.

C

C Fri Mar 26 15:07:55 2010

C Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes

C Using shared procedure name cache KINGDOMDB_PRDPRD_PRD_MEM initialized by another process.

C Connected to db server : [kingdomdb] server_used : [tcp:kingdomdb], dbname: PRD, dbuser: prd

C pn_id:KINGDOMDB_PRDPRD_PRD

C Not using MARS (on sql 8.0)

B Connection 0 opened (DBSL handle 0)

B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20100326 150751 KINGDOMDB

C The IRow interface is supported by this OLEDB provider

M db_connect o.k.

M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif

I

I Fri Mar 26 15:07:59 2010

I MtxInit: 0 0 0

M SHM_PRES_BUF (addr: 0A730040, size: 20000768)

M SHM_ROLL_AREA (addr: 61AF0040, size: 268435456)

M SHM_PAGING_AREA (addr: 103C0040, size: 134217728)

M SHM_ROLL_ADM (addr: 0BA50040, size: 2678942)

M SHM_PAGING_ADM (addr: 0BCE0040, size: 525344)

M ThCreateNoBuffer allocated 324144 bytes for 1000 entries at 0BD70040

M ThCreateNoBuffer index size: 3000 elems

M ThCreateVBAdm allocated 7424 bytes (50 server) at 0BDC0040

X EmInit: MmSetImplementation( 2 ).

X <ES> client 0 initializing ....

X Using implementation flat

X ES initialized.

B db_con_shm_ini: WP_ID = 0, WP_CNT = 22, CON_ID = -1

I *** ERROR => [CreateOsShm] CreateFileMapping(19,97656 KB) failed with Err=1450

ERROR_NO_SYSTEM_RESOURCES: Insufficient system resources exist to complete the requested service. [shmnt.c 2130]

I *** ERROR => ShmCreate: Create (19,99999904,1) failed [shmnt.c 469]

May i know why the dialog instance is down. And I dont know what should i do now. Need your advice.

Thank You

regards,

Anang78

[former_member204746 · Accepted solution]

ERROR_NO_SYSTEM_RESOURCES: Insufficient system resources exist to complete the requested service.

you should add more memory or use smaller memory-related values.

[Former Member · Accepted solution]

Hi,

One of the dialog instance is up and running fine. I dont think the memory is the issue. Need more advice on this issue.

regards,

anang78

[Former Member · Accepted solution]

Hi,

Some memory parameter must have been changed, which results ERROR_NO_SYSTEM_RESOURCES Messages.

Backup the current DI Instance profile and rename old version of DI Profile (which is having .BAK extension).

Check the "TIME STAMP" when DI instance was working fine to select the backup version of the profile.

Then try again to start the DI Instance and post the log again.

Later you can analyse the system load and tune the parameters accordingly...

If requred, increase the Physical Memory.

Regards.

Rajesh Narkhede

[Former Member · Accepted solution]

can anyone tell me how dialog instance is configure in SAP what are the steps?

yasir

[Former Member · Accepted solution]

Hi,

Can anybody share the experience why after I shut down the servers, my instances could not be started.

Hence, I am curious why it happen. And after the instance cannot start, I shutdown and reboot then only it works. Why all this always happens with my window machine. How to avoid to shutdown the server.

Thank you.

[Former Member · Accepted solution]

nd after the instance cannot start, I shutdown and reboot then only it works. Why all this always happens with my window machine. How to avoid to shutdown the server.

Are you have 32 bit windows ? if yes then answer use 64 bit ....

Some times i observe this situation on 64 bit windows to( but it looks like an exception, compared with 32 bit win), all this situations are related to SHARED MEMORY .......

You can find error's in dev_disp log directly after restart sap (and it can't start) or try to check in dev_disp.old , or in

dev_w0 --> dev_w0.old

Regards.

[Former Member]

Hi,

are you running two Dialog instances on one server ?

Mark

[Former Member]

Hi,

No the dialog instance is running with separate server (two server).

[Former Member]

Hi,

Check value of parameter "PHYS_MEMSIZE " & update as per requirment.

BR,

Darshan..

[Former Member]

Hi All,

Thank you very much for your sharing knowledge on this issue. The problem has been resolved. We had change the PHYS_MEM size in profile and the sap services is up and running fine now.

[Former Member]

Hi. You need listen note 88416. And check size of your page file..

[Former Member]

Hi,

Sorry, but I can't read your message : it hurts my eyes too much...

Regards,

Olivier