ERROR - Instance dont Start

[Former Member]

Dear all,

I have done the following Steps:

- Configured the client 000

- Copy the client 000 to client 100

- Configured the client 100

Of the Solution Manager. After that we shutdown the Instance. When try to re-start the Instance the Following message appears

- Running but Dialog Queue Standstill, J2EE Stopping the processes

Does any one have any idea what is the Problem?

Best Regards.

[Former Member]

Hi Pedro,

This message you must be getting in MMC. right.

Can you look into the Developer trace files and let me know the content of it.

I think i can help you but i need to know the content of these files.

regards,

Mantosh

[Former Member]

Hi Mantosh,

I am facing the same problem, any hints to solve this issue. Here is the Developer trace

-

---

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

-

---

sysno 00

sid EP1

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 75

intno 20050900

make: multithreaded, Unicode, optimized

pid 4208

Thu Aug 09 09:30:37 2007

kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)

length of sys_adm_ext is 572 bytes

• SWITCH TRC-HIDE on ***

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

shared lib "dw_xml.dll" version 75 successfully loaded

shared lib "dw_xtc.dll" version 75 successfully loaded

shared lib "dw_stl.dll" version 75 successfully loaded

shared lib "dw_gui.dll" version 75 successfully loaded

shared lib "dw_mdm.dll" version 75 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Thu Aug 09 09:30:42 2007

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

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >INST50053319_EP1_00 <

DpShMCreate: sizeof(wp_adm) 18304 (1408)

DpShMCreate: sizeof(tm_adm) 3994272 (19872)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

DpShMCreate: sizeof(comm_adm) 528064 (1048)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1440)

DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 073B0040, size: 4653368)

DpShMCreate: allocated sys_adm at 073B0040

DpShMCreate: allocated wp_adm at 073B1E40

DpShMCreate: allocated tm_adm_list at 073B65C0

DpShMCreate: allocated tm_adm at 073B65F0

DpShMCreate: allocated wp_ca_adm at 07785890

DpShMCreate: allocated appc_ca_adm at 0778B650

DpShMCreate: allocated comm_adm at 0778D590

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 0780E450

DpShMCreate: allocated gw_adm at 0780E490

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 0780E4C0

DpShMCreate: allocated wall_adm at 0780E4C8

MBUF state OFF

DpCommInitTable: init table for 500 entries

Thu Aug 09 09:30:43 2007

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 511 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 7352

argv[0] = D:\usr\sap\EP1\DVEBMGS00\exe\jcontrol.EXE

argv[1] = D:\usr\sap\EP1\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\EP1\SYS\profile\EP1_DVEBMGS00_INST50053319

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=3696

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=EP1

argv[7] = -DSAPMYNAME=INST50053319_EP1_00

argv[8] = -DSAPPROFILE=D:\usr\sap\EP1\SYS\profile\EP1_DVEBMGS00_INST50053319

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1623]

***LOG Q0K=> DpMsAttach, mscon ( INST50053319) [dpxxdisp.c 11586]

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

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

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

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

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

DpMsgAdmin: Set patchno for this platform to 75

Release check o.K.

DpJ2eeLogin: j2ee state = CONNECTED

Thanks in advance.

Ashish

[Former Member]

Hi Pedro,

Look for dev_work trace file, start profile and Instance profile.

you can compare the previous dev_work trace file and current...

reward points if useful

regards

Ganesh

[Former Member]

Hi

It seems that the db connect doesn't return. For this reason the

dispatcher can't forward a request to a work process, because the

work processes are still in the initial state and not able to process

any requests.

Can you paste the dev_work ltrace?Are you using MaxDB/SAPDB.

Reward points if useful