disp+work.exe is yellow!!

[xinjiang_li]

Hi,everyone:

I met a problem.

In MMC the status of disp+work.exe is yellow.

I restarted the service but not work.

Will I have to uninstall the system?If so,I will have to redo the post-installation,and it is terrible.

The deloper trace of disp+work.exe is below:

-

---

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

-

---

sysno 01

sid X01

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 95

intno 20050900

make: multithreaded, Unicode, optimized

pid 2708

Thu Dec 20 12:55:02 2007

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

length of sys_adm_ext is 572 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (01 2708) [dpxxdisp.c 1239]

shared lib "dw_xml.dll" version 95 successfully loaded

shared lib "dw_xtc.dll" version 95 successfully loaded

shared lib "dw_stl.dll" version 95 successfully loaded

shared lib "dw_gui.dll" version 95 successfully loaded

shared lib "dw_mdm.dll" version 95 successfully loaded

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

use internal message server connection to port 3901

Thu Dec 20 12:55:07 2007

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

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >neuesdnwxi02_X01_01 <

DpShMCreate: sizeof(wp_adm) 18616 (1432)

DpShMCreate: sizeof(tm_adm) 4232256 (21056)

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)

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 (1520)

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

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 060C0040, size: 4891728)

DpShMCreate: allocated sys_adm at 060C0040

DpShMCreate: allocated wp_adm at 060C1E80

DpShMCreate: allocated tm_adm_list at 060C6738

DpShMCreate: allocated tm_adm at 060C6768

DpShMCreate: allocated wp_ca_adm at 064CFBA8

DpShMCreate: allocated appc_ca_adm at 064D5968

DpShMCreate: allocated comm_adm at 064D78A8

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 06558768

DpShMCreate: allocated gw_adm at 065587A8

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 065587D8

DpShMCreate: allocated wall_adm at 065587E0

MBUF state OFF

DpCommInitTable: init table for 500 entries

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> Memory Reset disabled as NT default

<ES> 511 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 5324

argv[0] = C:\usr\sap\X01\DVEBMGS01\exe\jcontrol.EXE

argv[1] = C:\usr\sap\X01\DVEBMGS01\exe\jcontrol.EXE

argv[2] = pf=C:\usr\sap\X01\SYS\profile\X01_DVEBMGS01_neuesdnwxi02

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1595

argv[5] = -DSAPSYSTEM=01

argv[6] = -DSAPSYSTEMNAME=X01

argv[7] = -DSAPMYNAME=neuesdnwxi02_X01_01

argv[8] = -DSAPPROFILE=C:\usr\sap\X01\SYS\profile\X01_DVEBMGS01_neuesdnwxi02

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 1625]

***LOG Q0K=> DpMsAttach, mscon ( neuesdnwxi02) [dpxxdisp.c 11663]

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

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Thu Dec 20 12:55:08 2007

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 95

Release check o.K.

DpJ2eeLogin: j2ee state = CONNECTED

Thu Dec 20 12:55:18 2007

MBUF state ACTIVE

DpModState: change server state from STARTING to ACTIVE

thanks in ads.

Best regards!

[Former Member · Accepted solution]

Did u change any profile parameters to ask especially related to memory. If yes reset those and try to start again. Restarting the server has solved the problem once for me.

Reward points if useful

[Former Member]

Hii u can check r3trans -d from sql command prompt. abap/buffersize (typical size 240,000 – 400,000 KB). You can see this value in ST02. But as u cannot start insert it in instance profile and restart. Remeber if u have changed any profile parameters related to memory especially

reward points if useful

[Former Member]

Hii its a memory leak and adjust the abap buffer. Reduce its value. Also check r3trans -d if the result is 0 then its connected to database otherwise there is an error. Stop all of them ( db,sap) and restart the system

Aaward points if useful

[xinjiang_li]

Help:

the trace is below:

-

---

-

---

stdout/stderr redirect

-

---

-

---

node name : server0

pid : 5324

system name : X01

system nr. : 01

started at : Thu Dec 20 12:55:48 2007

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

Thr 2184 MtxInit: -2 0 0

CompilerOracle: exclude

com/sapportals/portal/pb/layout/taglib/ContainerTag

addIviewResources

CompilerOracle: exclude

com/sap/engine/services/keystore/impl/security/CodeBasedSecurityCon

nector getApplicationDomain

CompilerOracle: exclude

com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils

escapeToJS

CompilerOracle: exclude

com/sapportals/portal/prt/core/broker/PortalServiceItem

startServices

CompilerOracle: exclude

com/sap/engine/services/webservices/server/deploy/WSConfigurationHa

ndler downloadFile

CompilerOracle: exclude

com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalCont

ext lookup

CompilerOracle: exclude

com/sapportals/portal/navigation/cache/CacheNavigationNode

getAttributeValue

CompilerOracle: exclude

com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode

CompilerOracle: exclude

com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode

CompilerOracle: exclude

com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects

CompilerOracle: exclude

com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder

readElement

CompilerOracle: exclude

com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder

readSequence

CompilerOracle: exclude

com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl

initializeRelations

CompilerOracle: exclude

com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComple

xType _loadInto

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading:

LogManager ... 1234 ms.

Loading: PoolManager ... 62 ms.

Loading: ApplicationThreadManager ... 172 ms.

Loading: ThreadManager ... 47 ms.

Loading: IpVerificationManager ... 15 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... 938 ms.

Loading: LockingManager ... 312 ms.

Loading: ConfigurationManager ... 10766 ms.

Loading: LicensingManager ... 31 ms.

Loading: CacheManager ... 3672 ms.

Loading: ServiceManager ...

Loading services.:

Service memory started. (16 ms).

Service DQE started. (0 ms).

Service caf_euodi~mnuacc started. (0 ms).

Service userstore started. (16 ms).

Service cross started. (62 ms).

Service file started. (93 ms).

Service timeout started. (141 ms).

Service caf_eucc~api started. (32 ms).

Service runtimeinfo started. (0 ms).

Service jmx_notification started. (62 ms).

Service trex.service started. (62 ms).

Service p4 started. (250 ms).

Service classpath_resolver started. (31 ms).

Service log_configurator started. (7750 ms).

Service locking started. (0 ms).

Service naming started. (500 ms).

Service failover started. (156 ms).

Service appclient started. (234 ms).

Service ts started. (328 ms).

Service jmsconnector started. (297 ms).

Service javamail started. (312 ms).

Service licensing started. (547 ms).

Service http started. (1391 ms).

Service connector started. (1063 ms).

Service webservices started. (1266 ms).

Service iiop started. (547 ms).

Service deploy started. (16375 ms).

Service MigrationService started. (31 ms).

Service bi_mmrdeployer started. (16 ms).

Service configuration started. (32 ms).

Service MobileArchiveContainer started. (125 ms).

Service MobileSetupGeneration started. (187 ms).

Service dbpool started. (2343 ms).

Service caf_eugp_mailcf started. (31 ms).

Service com.sap.security.core.ume.service started. (2859 ms).

Dec 20, 2007 12:56:37... ...xt.<init>(UserContextSpi, Properties)

[SAPEngine_System_Threadimpl:5]_12 Fatal: Can not instantiate

UserContext with given properties.

service security ================= ERROR =================

Core service security failed. J2EE Engine cannot be started.

com.sap.engine.services.security.exceptions.SecurityServiceExceptio

n: Unexpected exception: at

com.sap.engine.services.security.SecurityServerFrame.start

(SecurityServerFrame.java:179)

at

com.sap.engine.core.service630.container.ServiceRunner.startApplica

tionServiceFrame(ServiceRunner.java:214)

at

com.sap.engine.core.service630.container.ServiceRunner.run

(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute

(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run

(SingleThread.java:150)

Caused by:

com.sap.engine.services.security.exceptions.BaseSecurityException:

No active userstore is set.

at

com.sap.engine.services.security.server.UserStoreFactoryImpl.getAct

iveUserStore(UserStoreFactoryImpl.java:77)

at

com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.

update(LoginModuleHelperImpl.java:402)

at

com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.

<init>(LoginModuleHelperImpl.java:81)

at

com.sap.engine.services.security.server.SecurityContextImpl.<init>

(SecurityContextImpl.java:57)

at

com.sap.engine.services.security.SecurityServerFrame.start

(SecurityServerFrame.java:135)

... 5 more

com.sap.engine.services.security.exceptions.SecurityServiceExceptio

n: Unexpected exception:

at

com.sap.engine.services.security.SecurityServerFrame.start

(SecurityServerFrame.java:179)

at

com.sap.engine.core.service630.container.ServiceRunner.startApplica

tionServiceFrame(ServiceRunner.java:214)

at

com.sap.engine.core.service630.container.ServiceRunner.run

(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute

(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run

(SingleThread.java:150)

Caused by:

com.sap.engine.services.security.exceptions.BaseSecurityException:

No active userstore is set.

at

com.sap.engine.services.security.server.UserStoreFactoryImpl.getAct

iveUserStore(UserStoreFactoryImpl.java:77)

at

com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.

update(LoginModuleHelperImpl.java:402)

at

com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.

<init>(LoginModuleHelperImpl.java:81)

at

com.sap.engine.services.security.server.SecurityContextImpl.<init>

(SecurityContextImpl.java:57)

at

com.sap.engine.services.security.SecurityServerFrame.start

(SecurityServerFrame.java:135)

... 5 more

Framework -> criticalShutdown Core service security failed. J2EE

Engine cannot be started.

Dec 20, 2007 12:56:37... com.sap.engine.core.Framework

[SAPEngine_System_Threadimpl:5]_12 Fatal: Critical shutdown was

invoked. Reason is: Core service security failed. J2EE Engine

cannot be started.

[xinjiang_li]

Hi,venkatesh :

Thank you very much.Could you tell me how to adjut the abap buffer and where to run r3trans -d?

thanks!

[Former Member]

Hi xinjiang

as venkatesh said its right if u changed any parameters reset in rz10 and go to os level execute command R3trans -d then the result is 0000 the db is working properly check and ask me if u have any problem..

Regards

Chandu

awards would be appreciated