Server Process is not running

Hi,
This is the defaulttrace file content, can any one give me idea how to solve.This server contain only WAS JAVA.
Server0 log file
#1.5#02004C4F4F500065000000E000000BE800043A7C9D203457#1190206793437#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9783####35db644066b011dcce2002004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F500058000000FE00000BE800043A7C9D4D3E17#1190206796390#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9767##mmsr17_NW2_28653750#abb#372b8af066b011dcad7802004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005D000000E900000BE800043A7C9F17D3A1#1190206826328#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9787####49b1ab5066b011dcced602004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F50005D000000EA00000BE800043A7C9F1D63A7#1190206826703#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9787####49b1ab5066b011dcced602004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F50005D000000EB00000BE800043A7C9F1D6546#1190206826703#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9787####49b1ab5066b011dcced602004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F500069000000CD00000BE800043A7C9F4D251D#1190206829828#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9767##mmsr17_NW2_28653750#abb#4b1755d066b011dcc24b02004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000580000010200000BE800043A7CB4AFA08D#1190207188609#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9825####21b496c066b111dcc3dd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F5000580000010300000BE800043A7CB4B5ECD8#1190207189031#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9825####21b496c066b111dcc3dd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F5000580000010400000BE800043A7CB4B5EE77#1190207189031#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9825####21b496c066b111dcc3dd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F5000580000010500000BE800043A7CB51B942F#1190207195687#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9767##mmsr17_NW2_28653750#abb#2545acc066b111dcca2802004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500057000000AA00000BE800043A7CB70647BD#1190207227843#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#397425f066b111dca5ca02004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006B0000010000000BE800043A7CB9735CC9#1190207268546#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9835####515ebcc066b111dcc33602004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F50006B0000010100000BE800043A7CB97BC4A7#1190207269109#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9835####515ebcc066b111dcc33602004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F50006B0000010200000BE800043A7CB97BC643#1190207269109#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9835####515ebcc066b111dcc33602004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F50006B0000010300000BE800043A7CB9D88E77#1190207275187#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#547fd2e066b111dcb02f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500053000004FF00000BE800043A7CC3F90739#1190207445093#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9853####ba97620066b111dccdff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F5000530000050000000BE800043A7CC3FE8D9F#1190207445453#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9853####ba97620066b111dccdff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F5000530000050100000BE800043A7CC3FE8F40#1190207445453#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9853####ba97620066b111dccdff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F500069000000CF00000BE800043A7CC4D09825#1190207459218#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#c24af89066b111dc852902004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500068000000F400000BE800043A7CC5D47C31#1190207476250#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9857####cd2bb33066b111dcc51302004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F500068000000F500000BE800043A7CC5DA1A13#1190207476625#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9857####cd2bb33066b111dcc51302004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F500068000000F600000BE800043A7CC5DA1BC3#1190207476625#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9857####cd2bb33066b111dcc51302004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F5000740000010E00000BE800043A7CC6163559#1190207480562#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#cef7e7b066b111dc8cff02004c4f4f50#SAPEngine_Application_Thread[impl:3]_12##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006C0000013E00000BE800043A7CD65676A6#1190207753218#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#Administrator#9886####721bab2066b211dc8da302004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F50006C0000013F00000BE800043A7CD65C1612#1190207753578#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#Administrator#9886####721bab2066b211dc8da302004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: com.sap.portal.navigation.masthead#
#1.5#02004C4F4F50006C0000014000000BE800043A7CD65C17B6#1190207753578#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#Administrator#9886####721bab2066b211dc8da302004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#
#1.5#02004C4F4F500060000000E500000BE800043A7CD6B7B4BB#1190207759578#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#755bbaf066b211dc844002004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000670000010600000BE800043A7CDCB8F09B#1190207860328#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#755bbaf066b211dc844002004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006E000000FA00000BE800043A7CDCE31A93#1190207863093#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9830##mmsr17_NW2_28653750#abb#755bbaf066b211dc844002004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500060000000E700000BE800043A7CE24B0CA4#1190207953796#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9907##mmsr17_NW2_28653750#abb#e9abe24066b211dc8fd102004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006D000000F600000BE800043A7CE51C9D48#1190208001093#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#9907##mmsr17_NW2_28653750#abb#e9abe24066b211dc8fd102004c4f4f50#SAPEngine_Application_Thread[impl:3]_37##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005E000000BB00000BE800043A7CF8F9C059#1190208334359#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###*--Flush data begin--*##
#1.5#02004C4F4F50005E000000BC00000BE800043A7CF8FA31D2#1190208334390#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###2 user ids saved##
#1.5#02004C4F4F50005E000000BD00000BE800043A7CF8FA6CDF#1190208334406#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###5 pages saved##
#1.5#02004C4F4F50005E000000BE00000BE800043A7CF8FAAFCF#1190208334421#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###4 iViews saved##
#1.5#02004C4F4F50005E000000BF00000BE800043A7CF8FAB048#1190208334421#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###*--Flush data end--*##
#1.5#02004C4F4F50005E000000C000000BE800043A7CF8FAB09F#1190208334421#/System/Server##com.sap.portal.activityreport#Guest#0####cd49627066b311dca3aa02004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.activityreport#Java###Duration: 62 millis##
#1.5#02004C4F4F50006F0000019800000BE800043A7D08467C02#1190208591046#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###Operation stopApp on application local/LeaveRequestApproval finished for 15 ms.#
#1.5#02004C4F4F50006F0000019900000BE800043A7D08467C8F#1190208591046#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation stopApp over application local/LeaveRequestApproval finished successfully on server 28653750#
#1.5#02004C4F4F50006F0000019D00000BE800043A7D0848F897#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###Operation startApp on application local/LeaveRequestApproval finished for 15 ms.#
#1.5#02004C4F4F50006F0000019E00000BE800043A7D0848F917#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application local/LeaveRequestApproval finished successfully on server 28653750#
#1.5#02004C4F4F50006F0000019F00000BE800043A7D0849117E#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation update over application local/LeaveRequestApproval finished successfully on server 28653750#
#1.5#02004C4F4F50006F000001A000000BE800043A7D084911F9#1190208591218#/System/Server##com.sap.engine.services.deploy#Administrator#9974####6630e8a266b411dcbbbd02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation update on application local/LeaveRequestApproval finished in whole cluster for 0 ms.#
#1.5#02004C4F4F50006F000001A100000BE800043A7D0ADC615A#1190208634421#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Aggregator Started...##
#1.5#02004C4F4F50006F000001A200000BE800043A7D0ADCAFD3#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Current Database Time: 24 Mar 2008 13:30:34 GMT##
#1.5#02004C4F4F50006F000001A300000BE800043A7D0ADCB048#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java#####
#1.5#02004C4F4F50006F000001A400000BE800043A7D0ADCB09F#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###*********** Aggregating data from 1 Jan 2007 00:00:34 GMT to 24 Mar 2008 13:30:34 GMT ***********##
#1.5#02004C4F4F50006F000001A500000BE800043A7D0ADCB147#1190208634453#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###query = SELECT MAX(TIMESTAMPHOUR) FROM WCR_AGGINFO WHERE AGGREGATIONLEVEL = 'h'##
#1.5#02004C4F4F50006F000001A600000BE800043A7D0ADCE534#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###First run at 3 Mar 2008 11:00:00 GMT##
#1.5#02004C4F4F50006F000001A700000BE800043A7D0ADCE5B0#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Aggregation not possible at least partailly done##
#1.5#02004C4F4F50006F000001A800000BE800043A7D0ADD1519#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_USERNODESTAT WHERE TIMESTAMPHOUR <= 1190208634450##
#1.5#02004C4F4F50006F000001A900000BE800043A7D0ADD19BB#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_WEBCNODESTAT WHERE TIMESTAMPHOUR <= 1190208634450##
#1.5#02004C4F4F50006F000001AA00000BE800043A7D0ADD1D7E#1190208634468#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_USERNODELOGON WHERE TIMESTAMPHOUR <= 1190208634450##
#1.5#02004C4F4F50006F000001AB00000BE800043A7D0ADD20BF#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_USERSTAT WHERE AGGREGATIONLEVEL = 'h' AND TIMESTAMPHOUR <= 1187616634450##
#1.5#02004C4F4F50006F000001AC00000BE800043A7D0ADD241D#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_WEBCONTENTSTAT WHERE AGGREGATIONLEVEL = 'h' AND TIMESTAMPHOUR <= 1187616634450##
#1.5#02004C4F4F50006F000001AD00000BE800043A7D0ADD27D8#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###SQL DELETE: DELETE FROM WCR_AGGINFO WHERE AGGREGATIONLEVEL = 'h' AND TIMESTAMPHOUR <= 1187616634450##
#1.5#02004C4F4F50006F000001AE00000BE800043A7D0ADD2C60#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Commit done##
#1.5#02004C4F4F50006F000001AF00000BE800043A7D0ADD2E59#1190208634484#/System/Server##com.sap.portal.activityreport.aggregator#Guest#0####8023365066b411dc942402004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Aggregation took 47 millis##
#1.5#02004C4F4F50005B000000DA00000BE800043A7D0F813F5D#1190208712343#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_27##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005F000000E800000BE800043A7D0FADB729#1190208715265#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_11##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500066000000E000000BE800043A7D10F2BC5F#1190208736562#/System/Server#sap.com/irj#com.sap.portal.transport#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_17##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#
#1.5#02004C4F4F500069000000D100000BE800043A7D15B9792B#1190208816687#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006A0000010100000BE800043A7D16093270#1190208821921#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500057000000AC00000BE800043A7D1652F937#1190208826750#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005B000000DC00000BE800043A7D1664AD52#1190208827921#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#eca3175066b411dc99de02004c4f4f50#SAPEngine_Application_Thread[impl:3]_27##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000770000002400000BE800043A7D174BD7B4#1190208843062#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50005E000000C100000BE800043A7D174FCACE#1190208843328#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500060000000E900000BE800043A7D1756E330#1190208843781#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50005D000000F000000BE800043A7D17DC4673#1190208852531#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000760000000F00000BE800043A7D182CB14E#1190208857796#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#Thread[PRT-Async 1,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50006A0000010300000BE800043A7D18302082#1190208858031#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000580000010900000BE800043A7D1836CF3D#1190208858468#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500057000000AE00000BE800043A7D18738CEA#1190208862437#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50005A0000010D00000BE800043A7D1B4FBFCB#1190208910437#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005D000000F200000BE800043A7D1BCA6E1F#1190208918468#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000530000050200000BE800043A7D1C2428C4#1190208924359#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000670000010800000BE800043A7D1C4174C7#1190208926265#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006E000000FC00000BE800043A7D1C5B3935#1190208927968#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000560000013E00000BE800043A7D1CCBA9CB#1190208935328#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#ae6a49e066b411dcc70202004c4f4f50#SAPEngine_Application_Thread[impl:3]_5##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006F000001B000000BE800043A7D1E1AD259#1190208957296#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002####4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000590000010700000BE800043A7D1E63EE6C#1190208962093#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_6##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500065000000E300000BE800043A7D1ED83B46#1190208969703#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F5000670000010A00000BE800043A7D1EF0DAC4#1190208971328#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005F000000EA00000BE800043A7D1FF3A223#1190208988281#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#4093bd1066b511dc848002004c4f4f50#SAPEngine_Application_Thread[impl:3]_11##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006F000001B200000BE800043A7D217D9D64#1190209014109#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990####62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006E000000FE00000BE800043A7D21CF6D5E#1190209019468#/System/Server#sap.com/irj#com.sap.portal.transport#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#
#1.5#02004C4F4F5000770000002600000BE800043A7D22933859#1190209032296#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000610000014100000BE800043A7D22972C3A#1190209032562#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_3##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000620000010200000BE800043A7D22A03409#1190209033140#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_26##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50006D000000FA00000BE800043A7D24030209#1190209056406#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_37##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500068000000F700000BE800043A7D2542795E#1190209077343#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500069000000D300000BE800043A7D25560CD2#1190209078625#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_29##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500065000000E500000BE800043A7D259497E1#1190209082718#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500065000000E700000BE800043A7D25AE33C8#1190209084406#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#8c16a40066b511dc816302004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500068000000FA00000BE800043A7D25F4DC7D#1190209089031#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005C0000018900000BE800043A7D26CCFBDB#1190209103187#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#9990##mmsr17_NW2_28653750#Administrator#62708fd066b511dcb19f02004c4f4f50#SAPEngine_Application_Thread[impl:3]_21##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000610000014400000BE800043A7D27782A46#1190209114406#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_3##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F500060000000EB00000BE800043A7D281E236F#1190209125296#/System/Server#sap.com/irj#com.sap.portal.sapapplication#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50005B000000E000000BE800043A7D286921AD#1190209130203#/System/Server#sap.com/irj#com.sap.portal.transport#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_27##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#
#1.5#02004C4F4F5000770000002800000BE800043A7D2B3A9FE6#1190209177484#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000720000013200000BE800043A7D2B3E90B6#1190209177750#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500068000000FC00000BE800043A7D2B485A1B#1190209178390#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_9##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000530000050400000BE800043A7D2BB72C5E#1190209185656#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_14##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000580000010B00000BE800043A7D2BF23F09#1190209189531#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500065000000E900000BE800043A7D2C13D341#1190209191718#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_25##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500057000000B000000BE800043A7D2CC288CF#1190209203171#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F500063000000EE00000BE800043A7D2CD6EAC9#1190209204515#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50006E000000FF00000BE800043A7D2D18DDC7#1190209208828#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50005E000000C300000BE800043A7D2EEEEB90#1190209239640#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#9dcfd77066b511dccc8002004c4f4f50#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50006C0000014100000BE800043A7D2FBF6A71#1190209253296#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#f0c617a066b511dcb83802004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50006C0000014300000BE800043A7D2FF14676#1190209256578#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#abb#10002##mmsr17_NW2_28653750#abb#f0c617a066b511dcb83802004c4f4f50#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.httpconnectivity.urliviews on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.httpconnectivity.urliviews#library:com.sap.portal.common#
#1.5#02004C4F4F50008D0000000000000BE800043A7D30545B8A#1190209263062#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#27b45fa166ad11dcafed02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/cafeugpuirt~comp finished successfully on server 28653750#
#1.5#02004C4F4F50008D0000000100000BE800043A7D30545BF9#1190209263062#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#27b45fa166ad11dcafed02004c4f4f50#SAPEngine_System_Thread[impl:5]_70##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/cafeugpuirt~comp finished on current cluster node for 47 ms.#
#1.5#02004C4F4F5000730000000600000BE800043A7D3083A0B8#1190209266156#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#a7c92c31669d11dcb80f02004c4f4f50#SAPEngine_System_Thread[impl:5]_86##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application com.test/csreq_cr finished successfully on server 28653750#
#1.5#02004C4F4F5000730000000700000BE800043A7D3083A125#1190209266156#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#a7c92c31669d11dcb80f02004c4f4f50#SAPEngine_System_Thread[impl:5]_86##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application com.test/csreq_cr finished on current cluster node for 94 ms.#
#1.5#02004C4F4F50005F000000EC00000BE800043A7D3181F8EB#1190209282828#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50006B0000010700000BE800043A7D31B78BF5#1190209286343#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_31##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F5000610000014600000BE800043A7D31EB1162#1190209289718#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_3##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50005A0000010F00000BE800043A7D322FF621#1190209294234#/System/Server#sap.com/irj#com.sap.portal.pcdadmintools#Administrator#10034##mmsr17_NW2_28653750#Administrator#01a16e3066b611dc954c02004c4f4f50#SAPEngine_Application_Thread[impl:3]_23##0#0#Warning#1#/System/Server#Plain### [com.sapportals.portal.pcd.admintools.roleeditor.RoleEditorCompContextHandler] Ex.msg:null#
#1.5#02004C4F4F50005A0000011100000BE800043A7D327E4387#1190209299359#/System/Server#sap.com/irj#com.sap.portal.sapapplication#abb#10002##mmsr17_NW2_28653750#abb#0c35dd9066b611dcacd902004c4f4f50#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#/System/Server#Plain###Undefined User Attribute debugParameters; return empty string#
#1.5#02004C4F4F50002C0000000700000BE800043A7D391C52A4#1190209410390#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#329208a1668f11dca53302004c4f4f50#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application com.test/csblock finished successfully on server 28653750#
#1.5#02004C4F4F50002C0000000800000BE800043A7D391C5310#1190209410390#/System/Server##com.sap.engine.services.deploy####mmsr17_NW2_28653750#Guest#329208a1668f11dca53302004c4f4f50#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application com.test/csblock finished on current cluster node for 125 ms.#
#1.5#02004C4F4F50008E0000000100000BE800043A7D3AA688E4#1190209436234#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008F0000000100000BE800043A7D3AA7F5D5#1190209436328#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008F0000000300000BE800043A7D3AA841A2#1190209436343#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008F0000000500000BE800043A7D3AA842A3#1190209436343#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000000700000BE800043A7D3AA8440E#1190209436343#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008E0000000300000BE800043A7D3AAD14A6#1190209436656#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008E0000000500000BE800043A7D3AAD16F9#1190209436656#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008E0000000700000BE800043A7D3AAD17A3#1190209436656#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008E0000000900000BE800043A7D3AAD189B#1190209436656#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000000900000BE800043A7D3AB1E837#1190209436968#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008F0000000B00000BE800043A7D3AB1EA83#1190209436968#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008F0000000D00000BE800043A7D3AB1EB2E#1190209436968#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000000F00000BE800043A7D3AB1EC1A#1190209436968#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008E0000000B00000BE800043A7D3AB6BCCC#1190209437296#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008E0000000D00000BE800043A7D3AB6BF2B#1190209437296#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008E0000000F00000BE800043A7D3AB6BFE8#1190209437296#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008E0000001100000BE800043A7D3AB6C0D3#1190209437296#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000001100000BE800043A7D3ABB91E2#1190209437609#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008F0000001300000BE800043A7D3ABB94EC#1190209437609#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008F0000001500000BE800043A7D3ABB959E#1190209437609#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000001700000BE800043A7D3ABB9695#1190209437609#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000001900000BE800043A7D3AC067E1#1190209437921#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008F0000001B00000BE800043A7D3AC06A2F#1190209437921#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008F0000001D00000BE800043A7D3AC06ADA#1190209437921#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000001F00000BE800043A7D3AC06C14#1190209437921#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008E0000001300000BE800043A7D3AC55E9F#1190209438250#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008E0000001500000BE800043A7D3AC560F5#1190209438250#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008E0000001700000BE800043A7D3AC561A8#1190209438250#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008E0000001900000BE800043A7D3AC5629E#1190209438250#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e0e2aa066b611dcca9a02004c4f4f50#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000002100000BE800043A7D3ACA31F2#1190209438562#/System/Server##com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor#Plain###A runtime exception ocurred: null#
#1.5#02004C4F4F50008F0000002300000BE800043A7D3ACA344F#1190209438562#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.status.StatusWriter#Plain###Process stopped#
#1.5#02004C4F4F50008F0000002500000BE800043A7D3ACA3502#1190209438562#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
#1.5#02004C4F4F50008F0000002700000BE800043A7D3ACA35F2#1190209438562#/System/Server##com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Guest#0####5e1c828066b611dcafa102004c4f4f50#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessor#Plain###Process stopped#
Thanks,
Vivek.

Hi,
default trace can be very misleading. The root cause might be in the default trace it might not be. One common problem is that your license is expired. I know just a wild guess, but may be it is a hit.
Regards,
Jochen

Similar Messages

Server Process is not running in the WAS JAVA

Hi,
The WAS JAVA have the resources Netweaver7.0 and java is j2sdk1.4.2_13 version Operating system is Windows2003 and database server is SQLserver2005.
Previously it was running properly Now it giving the following Error.
Any one of you please give me suggestions how to solve it .
Devolper trace for the jcontol.exe process is as follows
trc file: "D:\usr\sap\NW2\JC02\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 4516
system name : NW2
system nr. : 02
started at : Mon Mar 24 17:07:20 2008
arguments :
 arg[00] : D:\usr\sap\NW2\JC02\exe\jcontrol.EXE
 arg[01] : pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
-> ms host : mmsr17
-> ms port : 3903
-> OS libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : mmsr17
-> ms port : 3903
-> os libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] sdm : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 4512] [Node: bootstrap] java home is set by profile parameter
 Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> node execute : yes
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0286537
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlExecuteBootstrap: read instance values after global bootstrap
[Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
-> ms host : mmsr17
-> ms port : 3903
-> OS libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
[Thr 4512] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : mmsr17
-> ms port : 3903
-> os libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] sdm : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653700]
[Thr 4512] [Node: dispatcher bootstrap] java home is set by profile parameter
 Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID28653700]
-> node name : dispatcher bootstrap
-> node type : bootstrap
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653700
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap_ID28653700
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653700.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653700.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653700
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653750]
[Thr 4512] [Node: server0 bootstrap] java home is set by profile parameter
 Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID28653750]
-> node name : server0 bootstrap
-> node type : bootstrap
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653750
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap_ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653750.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653750.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653750
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5144] JControlRequestFunc: Thread 5144 started as listener thread for np messages.
[Thr 4512] [Node: dispatcher] java home is set by profile parameter
 Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [ID28653700]
-> node name : dispatcher
-> node type : dispatcher
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -XX:NewSize=57m -XX:MaxNewSize=57m -XX:NewRatio=3 -XX:DisableExplicitGC -verbose:gc -XX:UseConcMarkSweepGC
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 170M
-> init heap size : 170M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster\dispatcher
-> class path : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 4512] [Node: server0] java home is set by profile parameter
 Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [ID28653750]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 1024M
-> init heap size : 1024M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters :
-> debuggable : yes
-> debug mode : yes
-> debug port : 50221
-> shutdown timeout : 120000
[Thr 4512] INFO: Invalid property value [Debbugable=yes]
[Thr 4512] [Node: SDM] java home is set by profile parameter
 Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\j2sdk1.4.2_13
-> java parameters :
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\SDM\program
-> class path : D:\usr\sap\NW2\JC02\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\NW2\JC02\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 4512] JControlMSConnect: attached to message server (mmsr17/3903)
[Thr 5340] JControlMSMessageFunc: Thread 5340 started as listener thread for ms messages.
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653700
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_dispatcher.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process dispatcher started (PID:5444)
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = -debugMode=yes
-> arg[12] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4684)
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_sdm.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_sdm.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process SDM started (PID:5472)
[Thr 4512] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlMSSendLogon: insert SDM logon information (port=50218; rc=0)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4684) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (1)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856249 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:3944)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:3944) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (2)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856314 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4308)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4308) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (3)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856350 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:2616)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:2616) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856405 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
[Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
[Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c 1403]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:19, argument:1 from pid:0
[Thr 5144] JControlITraceIncrement: increment trace level for server0
[Thr 5144] *** ERROR => Can't send command for trace level increment (rc=-3) [jcntrxxi.c 1434]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:3556)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:3556) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (5)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856490 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:2872)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:2872) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (6)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189858000 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
[Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
[Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c 1403]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4836)
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] JControlIProcessSoftKill: soft kill of process server0 (pid:4836)
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4836) died (STOPPING)
[Thr 4512] JControlIResetProcess: reset process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:5428)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:5428) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (7)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860005 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:5196)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:5196) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (8)
[Thr 4512] JControlICheckProcessList: running flight recorder:
 C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860117 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
Thanks,
Vivek

Hi Vivek,
FYI :
JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
The above message can be ignored. You will see that message often in perfectly up/running systems as well.
Also, the dev_jcontrol file shows that the server process was terminating !
You need to check std_server0.out file for the errors/exceptions as to why server0 was terminating abruptly. The reason should be apparent from dev_server0 and std_server0 most of the times unless its a startup framework bug where the error messages are not written to the log files.
So, whenever the server process or dispatcher process fails to start, you should check the corresponding dev_server<n> or dev_dispatcher and std_server<n> / std_dispatcher files. Also, usually, there will be some exception (if its application related) in the defaultrace file as well under server<n>\log or dispatcher\log depending on which one is failing to start.
e.g. if server0 is failing to start due to some UME issues, you will see the mention of it in std_server0.out (definitely) and more ellaborate info/exceptions in deafultrace under server0\log as well.
Hope the above helps.

OID is up & running but "ldap" process are not running

Hi all,
Oracle Internet Directory is up & running but LDAP processes ( Not Running ---- Process oidmon
Not Running ---- Process oidldapd
Not Running ---- Process oidrepld
Not Running ---- Process odisrv) are not running.
I am trying to configure SSO for reverse proxy server and ran the command ssocfg.sh https proxyServerName proxyServerPort
and when i am trying to go for next step that is ldapmodify -D cn=orcladmin -w welcome1 -v -f setdasurl.ldif
it is showing up cannot connect to LDAP server. and also when i am trying to acess SSO admin Server the redirection url is showing up with 404 page not found error.
pls help me
Thanks

Do 'oidctl status' and check if the 'oidldapd' is up and running. If not, start 'oidmon' by executing the command 'oidmon start'.
To start 'oidldapd', use 'oidctl' command.
Eg: oidctl connect=<sid_name> server=oidldapd instance=<instance_num> start
Sometimes, when you start 'oidmon', the 'oidldapd' process is also started. So, its a good idea to do 'oidctl status' after 'oidmon start'

The server process could not be started because the configured identity is incorrect

Good morning
I have the same problem as here, every moning i must writing pasword.
https://social.msdn.microsoft.com/Forums/en-US/f95ee480-dda1-42fd-96af-596531e7ac2e/the-server-process-could-not-be-started-because-the-configured-identity-is-incorrect?forum=windowstransactionsprogramming
But my configuration is the same as was answer in this post, may be you can help me with another idea?. Thanks.
Windows 2008 R2 64Bit

Both machines start with an automatic login so technically there is an interactive user.
Nevertheless, it is an interesting point. i will try to configure the applications to run under a particular user and see if that changes anything.
Thank you
Peter

Apache Web Server Listener is not running

Hi,
when starting E_BUSINESS issuing this
adstrtal.sh apps/apps
, I have this error message :
Apache Web Server Listener is not running.
Starting Apache Web Server Listener (dedicated HTTP) ...
Apache Web Server Listener (PLSQL) is not running.
Starting Apache Web Server Listener (dedicated PLSQL) ...
What might be the problem ? How can I launch Apache Web Server Listener to see why it can not start and where to see it's log file ?
Many thanks

hsawwan,
I stopped all services, and killed process that were using port 8103. Then restarted all. In jserv.log we have
[09/11/2007 15:36:27:798 CET] Host os02ebsx.ourdomain.net not found and not allowed to connect
[09/11/2007 15:37:29:146 CET] Repository /Data/oracle/d03/prdacomn/java/apps.zip doesn't exist!
[09/11/2007 15:37:29:178 CET] oracle.apps.icx.common.InitSystemProperties: init
[09/11/2007 15:37:29:233 CET] oracle.apps.fnd.tcf.SocketServer: init
[09/11/2007 15:37:29:247 CET] weboamLocal/oracle.apps.fnd.oam.servlet.ui.OAMServlet: init
[09/11/2007 15:37:30:005 CET] weboamLocal/oracle.apps.fnd.oam.servlet.ui.OAMServlet: Sucessfully initialize oaosu.OAMServlet
[09/11/2007 15:37:30:156 CET] oracle.apps.mwa.wap.engine.WapServlet: init
[09/11/2007 15:37:30:156 CET] oracle.apps.mwa = /Data/oracle/d03/prdaappl/mwa/11.5.0
[09/11/2007 15:37:33:271 CET] Fatal error in parsing device registration file. See system log file for de-tails.
but in Context.xml file we do not have os02ebsx.ourdomain.net. Where does java server pick up this host ?
Thanks and regards.

This process will not run on a client version of lookout?

I get the following error message when I try to upload my process for web
access: "This process will not run on a client version of lookout?"
Why am I getting this?
Regards,
Tommy Scharmann

Hello Tommy,
You're probably trying to upload a process which has a Driver object in it
(like Modbus, AB, etc.) As you are aware, Lookout Clients (and Web CLients)
do not have Driver Objects and that's the reason you're getting the message.
You will normally upload your Client process -- a process which doesn't have
driver objects but talks to a Server Process in turn.
Regards,
Khalid
"Thomas Scharmann" wrote:
I get the following error message when I try to upload my process for web>access:
"This process will not run on a client version of lookout?"
Why am I getting this?
Regards,
Tommy Scharmann

The report server service is not running on Reporting Service Point server

Hi,
I have encountered a problem, my reporting service point has stopped working. (SCCM 2012 R2)
In srsrp.log:
Check state SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Check server health. SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Successfully created srsserver SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Reporting Services URL from Registry [https://s-hub-sql1.domain.local/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
3152 (0x0C50)
The request failed with HTTP status 404: Not Found.
SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
3152 (0x0C50)
(!) SRS not detected as running SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Failures reported during periodic health check by the SRS Server S-HUB-SQL1.domain.local.
SMS_SRS_REPORTING_POINT 12/15/2014 5:48:54 AM
3152 (0x0C50)
Registry change SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT
12/15/2014 5:48:54 AM 3152 (0x0C50)
Timed Out... SMS_SRS_REPORTING_POINT
12/15/2014 5:49:54 AM 3152 (0x0C50)
Set configuration SMS_SRS_REPORTING_POINT
12/15/2014 5:49:54 AM 3152 (0x0C50)
In windows event log:
On 12/15/2014 6:39:28 PM, component SMS_SRS_REPORTING_POINT on computer S-HUB-SQL1 reported: The report server service is not running on Reporting Service Point server "S-HUB-SQL1"; start the service to enable reporting.
In configuration manager service manager, the service sms_srs_reporting_point is running.
In Reporting services configuration manager, the service is running.
If I restart the reporting service, it doesn't helps.
What is not properly?

I've already found the reason why all stopped working - someone deleted the report manager URL HTTPS bindings (in Report services configuration manager). Added it back, than reporting started to work. Awww!

Golden gate extract and replicate process are not running.

All,
I am trying replicate data between two oracle databases using golden gate.
I am trying this scenario in a single machine(two databases and golden gate are on same windows machine)
1. I have two databases PROD, UAT both are running on 11.2 oracle home.
2. Created the ggate user both the databases, and enabled supplemental logging.
3. Ran the following scripts in both databases.
SQL> @marker_setup.sql
SQL> @ddl_setup.sql
SQL> @role_setup.sql
SQL> grant GGS_GGSUSER_ROLE to ggate;
SQL> @ddl_enable.sql
4. Connected the source database (PROD) in ggsci prompt
GGSCI (home-c07402bbc5) 79> add extract ext1, tranlog, begin now
add exttrail C:\app\Bhanu\Goldengate\lt, extract ext1
edit params ext1
EXTRACT ext1
USERID ggate@PROD, PASSWORD 123456
RMTHOST home-c07402bbc5, MGRPORT 7840
rmttrail C:\app\Bhanu\Goldengate\lt
ddl include mapped objname bhanu.* // bhanu is a schema in PROD database.
TABLE bhanu.*;
5. Connected the target database(UAT) in ggsci prompt
add checkpointtable ggate.checkpoint
edit params ./GLOBALS
GGSCHEMA ggate
CHECKPOINTTABLE ggate.checkpoint
add replicat rep1, exttrail C:\app\Bhanu\Goldengate\Mt,checkpointtable ggate.checkpoint
edit params rep1
replicat rep1
ASSUMETARGETDEFS
userid ggate@UAT, password 123456
discardfile C:\app\Bhanu\Goldengate\rep1_discard.txt, append, megabytes 10
map bhanu.*, target kiran.*;
After that started the extract, replicat using
start extract ext1, start replicate rep1
Now the status.
GGSCI (home-c07402bbc5) 103> info all
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT STOPPED EXT1 00:00:00 00:11:43
REPLICAT STOPPED REP1 00:00:00 00:21:16
Can you please help me what is wrong in my setup and why extract and replicate process are not running.
Edited by: user12178861 on Nov 19, 2011 11:22 AM

Thanks for your quick reply.
I have done few changes but extract, replicate process not running.
couple of points I would like to share with you regarding my setup.
1. I am using single golden date instance to replicate the data between PROD and UAT databases.
2. GGSCI (home-c07402bbc5) 1> dblogin userid ggate@PROD,PASSWORD 123456
Successfully logged into database.
GGSCI (home-c07402bbc5) 2> info all
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT STOPPED EXT1 00:00:00 01:23:29
REPLICAT STOPPED REP1 00:00:00 01:33:02
GGSCI (home-c07402bbc5) 3> VIEW REPORT EXT1
ERROR: REPORT file EXT1 does not exist.
GGSCI (home-c07402bbc5) 4> start er *
Sending START request to MANAGER ...
EXTRACT EXT1 starting
Sending START request to MANAGER ...
REPLICAT REP1 starting
GGSCI (home-c07402bbc5) 5> VIEW REPORT EXT1
ERROR: REPORT file EXT1 does not exist.
GGSCI (home-c07402bbc5) 6> info all
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT STOPPED EXT1 00:00:00 01:24:10
REPLICAT STOPPED REP1 00:00:00 01:33:44
Target :
GGSCI (home-c07402bbc5) 1> dblogin ggate@UAT,PASSWORD 123456
ERROR: Unrecognized parameter (GGATE@UAT), expected USERID.
GGSCI (home-c07402bbc5) 2> dblogin userid ggate@UAT,PASSWORD 123456
Successfully logged into database.
GGSCI (home-c07402bbc5) 5> add replicat rep1, exttrail C:\app\Bhanu\Goldengate/lt,checkpointtable ggate.checkpoint
ERROR: REPLICAT REP1 already exists.
GGSCI (home-c07402bbc5) 6> delete replicat rep1
Deleted REPLICAT REP1.
GGSCI (home-c07402bbc5) 7> add replicat rep1, exttrail C:\app\Bhanu\Goldengate/lt,checkpointtable ggate.checkpoint
REPLICAT added.
GGSCI (home-c07402bbc5) 8> edit params rep1
GGSCI (home-c07402bbc5) 9> start er *
Sending START request to MANAGER ...
EXTRACT EXT1 starting
Sending START request to MANAGER ...
REPLICAT REP1 starting
GGSCI (home-c07402bbc5) 10> info all
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT STOPPED EXT1 00:00:00 01:29:46
REPLICAT STOPPED REP1 00:00:00 00:00:48
3. Is mandatory that I need two golden gate instances running each side ?
Thanks for spending your time on this problem.

Central/dialog instance Server Process numbering not reset

Hi All,
we have a small 'problem' with our J2EE Web AS 640 server. This server was in the past set-up to run two server processes on the central instance. (server process 0 and 1). For some reason the server process 1 was removed and later on it was added again. But when you remove an server process it wil not reset the numbering. Therefore after recreation of the server process, the numbering started at two. So now we have server process 0 and server process 2...
It is not a very urgent problem at the moment, but we want to keep the system landscape exactly the same over all the different servers. Therefore we would be very happy if it was somehow possible to reset the numbering of the server processes.
If anyone is able to help us then we would be very thankfull!!.
Kind Regards,
Nico van der Linden

You can perform this in the offline config tool

Mailbox Server Role Services not running: MSExchangeDelivery

Running Exchange 2013 CU7 on Server 2012R2.
Ive been working on this project on and off for the last few months, as I am the only IT guy, and a new office construction at my company has had me running cable, moving offices, workstations, and phones.
This install of Exchange was working fine up until about a week ago. When I came back to finish its setup, I noticed that I was not able to send email internally anymore. Connecting to OWA says the message was sent, but it never arrives. After some more
investigation, it turns out the MSExchageDelivery service will not run.
Checking on this service, it indicates that it is starting/stopping, but never getting to the running stage. I have tried everything that I can think of, including uninstalling and re-installing the software. I have scoured the internet looking for solutions,
but not finding one that will take care of the problem.
Looking in the event viewer under Windows Logs -> Application I do see alot of information about MSExchangeTransportDelivery. Seems to be looping through a set of events....
1. Error MSExchangeTransportDelivery Failed to start listening (Error: 10048). Binding: 0.0.0.0:475
2. Error MSExchangeTransportDelivery This address is already in use. Binding: 0.0.0.0:475.
3. Error MSExchangeTransportDelivery Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsfot Exchage is [%2]. Make sure EdgeSync is running properly.
4. Information MSExchangeTransportDelivery The service will be stopped. Reason TCP/IP socket error. The service will stop.
5. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.TransportServerConfiguration has successfully completed.
6. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Data.Directory.SystemConfiguration.MailboxTransportServer has successfully completed.
7. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.X400AuthoritativeDomainTable has successfully completed.
8.Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.AcceptedDomainTable has successfully completed.
9.Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
10. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.RemoteDomainTable has successfully completed.
11.Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.TransportSettingsConfiguration has successfully completed.
12.Information MSExchangeTransportDelivery We are doing a full mailbox database reload as part of routing tables loading due to: First read.
Not sure where to go from here... any and all help is appreciated.

You're getting a tcp socket error and This address is already in use. Binding: 0.0.0.0:475.
Are you sure port 475 is not being used for some other service? Go to services and check if the
MSExchangeTransportDelivery is
currently stopped. If it is, open cmd and type netstat -ano and see if port 475 is showing up. If the MSExchangeTransportDelivery
is stopped it should not show up, if it is then it's being binded somewhere else and prob causing a conflict.
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Thank you for your help. MSExchangeTransportDelivery was stopped. When I ran the netstat command, it shows:
TCP    0.0.0.0:475            0.0.0.0:0              LISTENING       1600
TCP    127.0.0.1:475          127.0.0.1:35056        ESTABLISHED     1600
TCP    127.0.0.1:475          127.0.0.1:35231        ESTABLISHED     1600
TCP    127.0.0.1:475          127.0.0.1:35386        ESTABLISHED     1600
TCP    127.0.0.1:475          127.0.0.1:35559        ESTABLISHED     1600
TCP    127.0.0.1:475          127.0.0.1:35657        ESTABLISHED     1600
UDP    0.0.0.0:475            *:*
1600
So we can see that 475 is indeed in use. I followed this up with Process Explorer to find out what process had PID 1600. Turns out that a security dongle we use for network licensing is using that port. I will be moving the dongle to another server, and
will follow up here when I have results.

Application Server (Process Scheduler) Not Booting

Hello to all!
Having a quite difficult time booting the App. Server. Not sure what is going on? Not to my knowledge has anything changed to make the App. Server not boot this time. Probably a clinch, but still want to share my frustration. I presently run an Oracle 10g DB, PeopleSoft 8.50, Windows 7 Ulimate PC and here's what I am experiencing (see below):
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\afam>cd\
C:\>cd pt8.50\appserv
C:\PT8.50\appserv>psadmin
PSADMIN -- Tools Release: 8.50.14
Copyright (c) 1988, 2009, Oracle. All rights reserved.
PeopleSoft Server Administration
1) Application Server
2) Process Scheduler
3) Search Server
4) Service Setup
q) Quit
Command to execute (1-4, q): 1
PeopleSoft Application Server Administration
1) Administer a domain
2) Create a domain
3) Delete a domain
4) Import domain configuration
q) Quit
Command to execute (1-4, q) : 1
Tuxedo domain list:
1) INNOVATI
Select domain number to administer: 1
PeopleSoft Domain Administration
Domain Name: INNOVATI
1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit
Command to execute (1-10, q) : 1
PeopleSoft Domain Boot Menu
Domain Name: INNOVATI
1) Boot (Serial Boot)
2) Parallel Boot
q) Quit
Command to execute (1-2, q) [q]: 1
Attempting to boot bulletin board...
tmadmin - Copyright (c) 2007-2008 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
No bulletin board exists. Entering boot mode.
INFO: Oracle Tuxedo, Version 10.3.0.0 with VS2005, 32-bit, Patch Level (none)Booting admin processes ...
exec BBL -A :
process id=8068 ... Started.
1 process started.
Attaching to active bulletin board.
Attempting to boot ...INFO: Oracle Tuxedo, Version 10.3.0.0 with VS2005, 32-bit, Patch Level (none)
Booting server processes ...
exec PSWATCHSRV -o ".\LOGS\stdout" -e ".\LOGS\stderr" -A -- -ID 49520 -D INNOVAT
I -S PSWATCHSRV :
process id=6852 ... Started.
exec PSAPPSRV -o ".\LOGS\stdout" -e ".\LOGS\stderr" [email protected] -- -D INNOVA
TI -S PSAPPSRV :
CMDTUX_CAT:1685: ERROR: Application initialization failure
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error ha
ndler
tmshutdown -qy
==============ERROR!================
Boot attempt encountered errors!. Check the TUXEDO log for details.
==============ERROR!================
Do you wish to see the error messages in the APPSRV.LOG file? (y/n) [n] :y
PSADMIN.7352 (0) [12/17/12 21:00:02](0) Begin boot attempt on domain INNOVATI
PSAPPSRV.4832 (0) [12/17/12 21:00:13](0) PeopleTools Release 8.50.14 (WinX86) st
arting. Tuxedo server is APPSRV(99)/2
PSAPPSRV.4832 (0) [12/17/12 21:00:14](0) Cache Directory being used: C:\PT8.50\a
ppserv\appserv\INNOVATI\CACHE\PSAPPSRV_2\
PSAPPSRV.4832 (0) [12/17/12 21:00:14](3) File: SQL Access ManagerSQL error. Stmt
#: 2 Error Position: 0 Return: 1033 - ORA-01033: ORACLE initialization or shu
tdown in progress
PSAPPSRV.4832 (0) [12/17/12 21:00:14](1) GenMessageBox(200, 0, M): SQL Access Ma
nager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return:
1033 - ORA-01033: ORACLE initialization or shutdown in progress
PSAPPSRV.4832 (0) [12/17/12 21:00:14](1) GenMessageBox(0, 0, M): Database Signon
: Could not sign on to database INNOVATI with user PS.
PSAPPSRV.4832 (0) [12/17/12 21:00:14](0) Server failed to start
PSADMIN.7352 (0) [12/17/12 21:00:21](0) End boot attempt on domain INNOVATI
Do you wish to see the error messages in the TUXLOG.121712 file? (y/n) [n] :y
210002.KELVIN!PSADMIN.7352: Begin attempt on domain INNOVATI
210006.KELVIN!tmadmin.7744.5444.-2: TMADMIN_CAT:1330: INFO: Command: boot -A
210008.KELVIN!tmboot.7652.7332.-2: 12-17-2012: Tuxedo Version 10.3.0.0 with VS20
05, 32-bit
210008.KELVIN!tmboot.7652.7332.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set
to 120 seconds
210008.KELVIN!tmboot.7652.7332.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL op
tion is selected
210010.KELVIN!BBL.8068.7320.0: 12-17-2012: Tuxedo Version 10.3.0.0 with VS2005,
32-bit, Patch Level (none)
210010.KELVIN!BBL.8068.7320.0: LIBTUX_CAT:262: INFO: Standard main starting
210012.KELVIN!tmboot.7248.3440.-2: 12-17-2012: Tuxedo Version 10.3.0.0 with VS20
05, 32-bit
210012.KELVIN!tmboot.7248.3440.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set
to 120 seconds
210012.KELVIN!tmboot.7248.3440.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL op
tion is selected
210012.KELVIN!PSWATCHSRV.6852.4148.-2: 12-17-2012: Tuxedo Version 10.3.0.0 with
VS2005, 32-bit
210012.KELVIN!PSWATCHSRV.6852.4148.-2: LIBTUX_CAT:262: INFO: Standard main start
ing
210013.KELVIN!PSAPPSRV.4832.4956.0: 12-17-2012: Tuxedo Version 10.3.0.0 with VS2
005, 32-bit
210013.KELVIN!PSAPPSRV.4832.4956.0: LIBTUX_CAT:262: INFO: Standard main starting
210014.KELVIN!PSAPPSRV.4832.4956.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
210014.KELVIN!tmboot.7248.3440.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error en
countered; initiating user error handler
210018.KELVIN!BBL.8068.7320.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
210021.KELVIN!PSADMIN.7352: End boot attempt on domain INNOVATI
Press Enter to continue...
PeopleSoft Domain Administration
Domain Name: INNOVATI
1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit
Command to execute (1-10, q) :
Any help would be greatly appreciated! Thanks. Be Blessed

Herald:
Thanks for getting back to me! I think you are right in that this would be a question more geared toward to the Peoplesoft folks. The post is there, so thank you for that. However, you noted a key observation that led me to want to investigate more. If we look at a past post that speaks to your observation (ORACLE Initialization or shutdown in progress I believe it gave me more clues to go by. I do shared the same thought as the poster in that, the DB should have started as the service started for the DB as already. At any rate, I ran the instructed command in SQL, I got this script:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\afam>cd\
C:\>sqlplus/nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 18 05:36:02 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys/manager as sysdba
Connected.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 293601280 bytes
Fixed Size 1248600 bytes
Variable Size 83886760 bytes
Database Buffers 201326592 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-16038: log 1 sequence# 1337 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\INNOVATI\REDO01.LOG'
SQL>
What can be made from this observation? Be Blessed

ITunes in Processes but not running

My iTunes is running the the processes, but is not running in the applications. I have removed and uninstalled iTunes and Quicktime and reinstalled the most recent version. Quicktime opens and there are no error messages in the Quicktime Prefs. Any ideas? Thanks

If you see the exe but itunes never fully opens, polydorus' post here might help -
http://discussions.apple.com/thread.jspa?threadID=1875404&tstart=0

Server side script not running on stand-alone XE

Hello,
In my application I created a Server side script (AJAX) which presents a select-list based on other fields on the page. The very same application runs on a 10g+APEX3.0.1 database AND on a standard XE+APEX2.1 database, which are both accessed via a HTTP-server. The application with the script runs fine on this platform (XP).
I have two other XP-machines on which I also installed XE+APEX2.1. Both are stand-alone versions NOT accessed via a HTTP-server. I installed exactly the same application which runs on the platform with HTTP server on both of the machines. While testing the correct functioning, I noticed that everything works ok, EXCEPT the server side script which gives me a better select list. Instead of this I get the old-fashioned version of the select-list which is not able to use the value elsewhere on the page.
I found a similar problem on the XE forum (Re: Server side scripts features ) but it doesn't answer my question how to get the script working on a standalone version of XE (= without access via a HTTP-server).
Can anybody please help me?
Thanks & regards,
Jan.
Message was edited by: Jan
J. Hulsing

Carl,
Thanks for your suggestion to install FireFox and the Firebug tool (which I wasn't aware of).
After having looked at the problem for hours, I found what I think is the problem: the htmldb_html_elements.js script.
As already mentioned, the properly functioning XE on my local PC is accessed via a HTTP-server, as well as the 10gR2+APEX3.0.1 version also running on that PC.
On the laptop, not running HTTP-server, I get the message: 
$x is not defined 
 f_21_select_kpn(input#P21_GBREKNR 405, "P21_KOSTENPOST") 
onblur(blur )
 
That is in the 'Console' of Firebug.
When changing to Script I do see a remarkable difference.
On the PC there the following text is found in the first lines of htmldb_html_elements.js:
/*htmld_elements will contain the lower level html access js*/ 
var gDebug = true; 
var gkeyPressTime; 
var gLastTab=false; 
var gRegex=false; 
var ie=(document.all)?true:false; 
if(ie){document.expando=true;} 
var gDebugWindow = false; 
/* 
$x functions have to do with either single elements or array of elements 
$v functions have to have to do with manipulating values or interaction based off a value 
$xml function have to do with manipulating xml values 
$a functions are based on ajax 
$d functions are specific dhtml constructs 
*/ 
/* begin $x functions */ 
function $x(pNd){ 
try{ 
var node; 
... 
On the laptop however the first few lines are: 
/*htmld_elements will contain the lower level html access js*/ 
 
var gDebug = true; 
var gkeyPressTime; 
var gLastTab=false; 
var gRegex=false; 
if(document.all){document.expando = true;} 
// Elements // 
 
function html_GetElement(pNd){ 
try{ 
var node; 
switch(typeof (pNd)){ 
... 
I think that the difference is in these two scripts.
But why are the scripts different: it is the same XE that is installed on the laptop and the PC. The answer I found in the images/javascript directory of APEX3.0.1 which is located in the APACHE directory-tree (you have to copy the images to APACHE when you use the HTTP-server). And indeed: the htmldb_html_elements.js has exactly the same text as what I see in Firebug on the PC. So XE on the PC is using the javascripts in the image-directory of APACHE on the PC and not the XE-version of the scripts, embedded in XE.
 
So the answer seems to be: copy the APEX3.0.1 versions of the script over to the PC and try to get them into the database. Or...???
 
Can it be loaded into the database? Will XE accept it?
 
Would be nice to have answers if the conclusion I found is the right one and if it can be fixed by loading the js into XE.
 
Best regards and thanks for your help so far.
 
Jan.

Adobe Media Server Installer does not run

I am trying to install Adobe Media Server 5 on Windows 2008 R2 64 bit on i3 logged in as an administarive user over RDP.
The installer simply does not run - a very short hourglass then nothing. Not logs in applicaiton, system of setup logs.
The bundled Adobe Media Gateway installer runs just fine.
Tried a machine restart, and still no go...
Any ideas gratefully received
Simon

ok, got it... go properties on the file and 'unblock'
This was because I downloaded it on another machine, and then copied it over. Windows 2008 knew it had not been made locally and silently blocked execution.

FA - Asset accidentally deleted but depreciation process was not run

Hi,
Accidentally I have deleted an asset that I should not delete but I did not run the depreciation process.
If I go to Transaction details, it says in status = “Pending”
Is there any way to rollback this or to cancel the transaction and make the asset active again?
Thanks,
Facundo.

This are the steps that I made:
1. Go to Assets -> Asset workbench
2. Look to the asset and click on retirements
3. I complete all needed information and save it.
That´s all what I did. If I go to the transaction, the field status shows "Pending".
Is there any way to cancel this retirement?

Server Process is not running

Similar Messages

Maybe you are looking for