cancel
Showing results for 
Search instead for 
Did you mean: 

Netweaver fails to startup

Former Member
0 Kudos

Hi,

Netweaver 2004s abap+java stack on windows 2003 with oracle was working fine on a standalone system. The standalone was converted to windows 2003 active domain controller. After a system restart, SAP netweaver does not startup.

The trace file indicate the following error.

-


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

-


-


"*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 17 seconds

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

-


Thu Apr 07 09:02:07 2011

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

length of sys_adm_ext is 576 bytes

      • SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (11 4656) [dpxxdisp.c 1286]

shared lib "dw_xml.dll" version 32 successfully loaded

shared lib "dw_xtc.dll" version 32 successfully loaded

shared lib "dw_stl.dll" version 32 successfully loaded

shared lib "dw_gui.dll" version 32 successfully loaded

shared lib "dw_mdm.dll" version 32 successfully loaded

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

use internal message server connection to port 3911

Thu Apr 07 09:02:20 2011

      • WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0064.qqq.nxst) took 13 seconds

Thu Apr 07 09:02:37 2011

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

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

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >TRXPCS1S_VS1_11 <

DpShMCreate: sizeof(wp_adm) 13632 (1704)

DpShMCreate: sizeof(tm_adm) 4415616 (21968)

DpShMCreate: sizeof(wp_ca_adm) 24064 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

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

DpShMCreate: sizeof(comm_adm) 528064 (1048)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (96)

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

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1544)

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

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 06670040, size: 5070920)

DpShMCreate: allocated sys_adm at 06670040

DpShMCreate: allocated wp_adm at 06672170

DpShMCreate: allocated tm_adm_list at 066756B0

DpShMCreate: allocated tm_adm at 066756E0

DpShMCreate: allocated wp_ca_adm at 06AAB760

DpShMCreate: allocated appc_ca_adm at 06AB1560

DpShMCreate: allocated comm_adm at 06AB34A0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 06B34360

DpShMCreate: allocated gw_adm at 06B343A0

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 06B343D0

DpShMCreate: allocated wall_adm at 06B343D8

MBUF state OFF

DpCommInitTable: init table for 500 entries

rdisp/queue_size_check_value : -> off

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 3598 blocks reserved for free list.

ES initialized.

what could be the likely cause of this error after an active directory installation on the standalone server.

Thanks & Regards,

Junaid

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor
0 Kudos

dev_disp is not showing any mayor issues, can you post dev_w0?

Also, Its unusual to use a SAP system box as a domain controller any reason for that?

Regards

Juan

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Juan,

Many thanks for your reply. The problem is resolved. Further analysing, I realised that the DB users SAPSR3 and SAPSR3DB were locked for some reasons. The problem is resolved now.

You are right, its not a good idea to have a domain contoller on SAP box. Just want to test ADS and SSO intergration with SAP hence tried it.

Thanks & Regards,

Junaid