Hello,
I'm having problems starting SMDAgent in a NetWeaver 7.0 EHP1 installation. Using SAP Management Console I can verify that its status is always "Starting the processes", but it never turns green.
Doing a deeper analysis inside the Java Process Table node, I see that SMDAgent is stopped. Whenever I try to start it, it gets shut down abnormally. Bellow is the Developer Trace:
trc file: "C:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "701"
-
node name : smdagent
pid : 4956
system name : SMD
system nr. : 98
started at : Mon Oct 25 17:24:04 2010
arguments :
arg[00] : C:\usr\sap\SMD\J98\..\exe\jlaunch.exe
arg[01] : pf=C:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_sapmii
arg[02] : -DSAPINFO=SMD_98_server
arg[03] : pf=C:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_sapmii
**********************************************************************
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\SMD\J98\profile\smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : C:\usr\sap\SMD\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : C:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host :
-> ms port : 36
-> os libs : C:\usr\sap\SMD\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
**********************************************************************
**********************************************************************
Worker nodes
-> [00] smdagent : C:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
[Thr 4500] Mon Oct 25 17:24:04 2010
[Thr 4500] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4500] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2616] JLaunchRequestFunc: Thread 2616 started as listener thread for np messages.
[Thr 1008] WaitSyncSemThread: Thread 1008 started as semaphore monitor thread.
[Thr 4500] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 4500] CPIC (version=701.2009.01.26)
[Thr 4500] JStartupIReadSection: debug mode is specified by program arguments
[Thr 4500] [Node: SMDAgent] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_27-x64
[Thr 4500] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\SMD\exe\jvmx.jar
**********************************************************************
JStartupIReadSection: read node properties [smdagent]
-> node name : SMDAgent
-> node type : server
-> node id : 1
-> node execute : yes
-> java path : C:\j2sdk1.4.2_27-x64
-> java parameters : -DP4ClassLoad=P4Connection
-> java vm version : 1.4.2_27-b03
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 128M
-> init heap size : 128M
-> root path : ..\SMDAgent
-> class path : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> OS libs path : C:\usr\sap\SMD\exe
-> main class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\SMD\exe\jstartup.jar;C:\usr\sap\SMD\exe\jvmx.jar
-> shutdown class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> parameters : run jcontrol
-> debuggable : yes
-> debug mode : yes
-> debug port : 58981
-> shutdown timeout : 20000
**********************************************************************
[Thr 4500] JLaunchISetDebugMode: set debug mode [yes]
[Thr 848] JLaunchIStartFunc: Thread 848 started as Java VM thread.
[Thr 848] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
Java Parameters: -Xss2m
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -DP4ClassLoad=P4Connection
-> arg[ 4]: -Dsys.global.dir=C:\usr\sap\SMD\SYS\global
-> arg[ 5]: -Dapplication.home=C:\usr\sap\SMD\exe
-> arg[ 6]: -Djava.class.path=C:\usr\sap\SMD\exe\jstartup.jar;C:\usr\sap\SMD\exe\jvmx.jar;lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> arg[ 7]: -Djava.library.path=C:\j2sdk1.4.2_27-x64\jre\bin\server;C:\j2sdk1.4.2_27-x64\jre\bin;C:\j2sdk1.4.2_27-x64\bin;C:\usr\sap\SMD\exe;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_27-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\usr\sap\SMD\exe
-> arg[ 8]: -Xdebug
-> arg[ 9]: -Xnoagent
-> arg[ 10]: -Djava.compiler=NONE
-> arg[ 11]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=58981
-> arg[ 12]: -Dmemory.manager=128M
-> arg[ 13]: -Xmx128M
-> arg[ 14]: -Xms128M
-> arg[ 15]: -DLoadBalanceRestricted=no
-> arg[ 16]: -Djstartup.mode=JCONTROL
-> arg[ 17]: -Djstartup.ownProcessId=4956
-> arg[ 18]: -Djstartup.ownHardwareId=B0299142182
-> arg[ 19]: -Djstartup.whoami=server
-> arg[ 20]: -Djstartup.debuggable=yes
-> arg[ 21]: -Xss2m
-> arg[ 22]: -DSAPINFO=SMD_98_server
-> arg[ 23]: -DSAPSTARTUP=1
-> arg[ 24]: -DSAPSYSTEM=98
-> arg[ 25]: -DSAPSYSTEMNAME=SMD
-> arg[ 26]: -DSAPMYNAME=sapmii_SMD_98
-> arg[ 27]: -DSAPDBHOST=
-> arg[ 28]: -Dj2ee.dbhost=
**********************************************************************
[Thr 848] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
**********************************************************************
[Thr 848] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 848] Mon Oct 25 17:24:05 2010
[Thr 848] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 848] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 848] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 848] JLaunchIStartFunc: end of main method (rc = 0)
[Thr 1580] Mon Oct 25 17:24:06 2010
[Thr 1580] JLaunchIExitJava: exit hook is called (rc = -11112)
[Thr 1580] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
**********************************************************************
[Thr 1580] JLaunchCloseProgram: good bye (exitcode = -11112)
What is the meaning of error code -11112?
Regards,
David