SMD Agent is not starting

[Former Member]

Hi Gurus,

We are configuring Solman Diagnstic configuration,our SMD agent is not starting , here the trace file

-

---

trc file: "F:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "700"

-

---

node name : smdagent

pid : 3008

system name : SMD

system nr. : 98

started at : Tue Mar 24 06:54:13 2009

arguments :

arg[00] : F:\usr\sap\SMD\J98\..\exe\jlaunch.exe

arg[01] : pf=F:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_vmsapdevsm

arg[02] : -DSAPINFO=SMD_98_server

arg[03] : pf=F:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_vmsapdevsm

**********************************************************************

JStartupReadInstanceProperties: read instance properties [F:\usr\sap\SMD\J98\profile\smd.properties]

-> ms host :

-> ms port : 36

-> OS libs : F:\usr\sap\SMD\exe

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Used property files

-> files [00] : F:\usr\sap\SMD\J98\profile\smd.properties

**********************************************************************

**********************************************************************

Instance properties

-> ms host :

-> ms port : 36

-> os libs : F:\usr\sap\SMD\exe

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Bootstrap nodes

**********************************************************************

**********************************************************************

Worker nodes

-> [00] smdagent : F:\usr\sap\SMD\J98\profile\smd.properties

**********************************************************************

[Thr 3800] Tue Mar 24 06:54:13 2009

[Thr 3800] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 3800] JLaunchRequestQueueInit: create pipe listener thread

[Thr 3856] JLaunchRequestFunc: Thread 3856 started as listener thread for np messages.

[Thr 4000] WaitSyncSemThread: Thread 4000 started as semaphore monitor thread.

[Thr 3800] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 3800] CPIC (version=700.2006.09.13)

[Thr 3800] [Node: SMDAgent] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_17-x64

[Thr 3800] JStartupICheckFrameworkPackage: can't find framework package F:\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_17-x64

-> java parameters : -DP4ClassLoad=P4Connection

-> java vm version : 1.4.2_17-b06

-> 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 : F:\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 : F:\usr\sap\SMD\exe\jstartup.jar;F:\usr\sap\SMD\exe\jvmx.jar

-> shutdown class : com.sap.smd.agent.launcher.SMDAgentLauncher

-> parameters : run jcontrol

-> debuggable : yes

-> debug mode : no

-> debug port : 58981

-> shutdown timeout : 20000

**********************************************************************

[Thr 3800] JLaunchISetDebugMode: set debug mode [no]

[Thr 3096] JLaunchIStartFunc: Thread 3096 started as Java VM thread.

[Thr 3096] [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=F:\usr\sap\SMD\SYS\global

-> arg[ 5]: -Dapplication.home=F:\usr\sap\SMD\exe

-> arg[ 6]: -Djava.class.path=F:\usr\sap\SMD\exe\jstartup.jar;F:\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_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\j2sdk1.4.2_17-x64\bin;F:\usr\sap\SMD\exe;C:\Program Files\Legato\nsr\bin;C:\Program Files (x86)\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;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\;F:\usr\sap\SMD\exe

-> arg[ 8]: -Dmemory.manager=128M

-> arg[ 9]: -Xmx128M

-> arg[ 10]: -Xms128M

-> arg[ 11]: -DLoadBalanceRestricted=no

-> arg[ 12]: -Djstartup.mode=JCONTROL

-> arg[ 13]: -Djstartup.ownProcessId=3008

-> arg[ 14]: -Djstartup.ownHardwareId=H0430968350

-> arg[ 15]: -Djstartup.whoami=server

-> arg[ 16]: -Djstartup.debuggable=yes

-> arg[ 17]: -Xss2m

-> arg[ 18]: -DSAPINFO=SMD_98_server

-> arg[ 19]: -DSAPSTARTUP=1

-> arg[ 20]: -DSAPSYSTEM=98

-> arg[ 21]: -DSAPSYSTEMNAME=SMD

-> arg[ 22]: -DSAPMYNAME=vmsapdevsm_SMD_98

-> arg[ 23]: -DSAPDBHOST=

-> arg[ 24]: -Dj2ee.dbhost=

**********************************************************************

[Thr 3096] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [SMDAgent]

-> arg[ 0]: run

-> arg[ 1]: jcontrol

**********************************************************************

[Thr 3096] Tue Mar 24 06:54:14 2009

[Thr 3096] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 3096] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 3096] JLaunchISetState: change state from [Waiting for start (1)] to [Initial (0)]

[Thr 3096] JLaunchISetState: change state from [Initial (0)] to [Starting (2)]

[Thr 2132] JLaunchIExitJava: exit hook is called (rc = -11112)

[Thr 2132] **********************************************************************

• 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 2132] JLaunchCloseProgram: good bye (exitcode = -11112)

-

---

trc file: "F:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "700"

-

---

node name : smdagent

pid : 3024

system name : SMD

system nr. : 98

started at : Wed Mar 25 08:29:26 2009

arguments :

arg[00] : F:\usr\sap\SMD\J98\..\exe\jlaunch.exe

arg[01] : pf=F:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_vmsapdevsm

arg[02] : -DSAPINFO=SMD_98_server

arg[03] : pf=F:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_vmsapdevsm

**********************************************************************

JStartupReadInstanceProperties: read instance properties [F:\usr\sap\SMD\J98\profile\smd.properties]

-> ms host :

-> ms port : 36

-> OS libs : F:\usr\sap\SMD\exe

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Used property files

-> files [00] : F:\usr\sap\SMD\J98\profile\smd.properties

**********************************************************************

**********************************************************************

Instance properties

-> ms host :

-> ms port : 36

-> os libs : F:\usr\sap\SMD\exe

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Bootstrap nodes

**********************************************************************

**********************************************************************

Worker nodes

-> [00] smdagent : F:\usr\sap\SMD\J98\profile\smd.properties

**********************************************************************

[Thr 3052] Wed Mar 25 08:29:26 2009

[Thr 3052] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 3052] JLaunchRequestQueueInit: create pipe listener thread

[Thr 5700] JLaunchRequestFunc: Thread 5700 started as listener thread for np messages.

[Thr 2376] WaitSyncSemThread: Thread 2376 started as semaphore monitor thread.

[Thr 3052] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 3052] CPIC (version=700.2006.09.13)

[Thr 3052] [Node: SMDAgent] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_17-x64

[Thr 3052] JStartupICheckFrameworkPackage: can't find framework package F:\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_17-x64

-> java parameters : -DP4ClassLoad=P4Connection

-> java vm version : 1.4.2_17-b06

-> 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 : F:\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 : F:\usr\sap\SMD\exe\jstartup.jar;F:\usr\sap\SMD\exe\jvmx.jar

-> shutdown class : com.sap.smd.agent.launcher.SMDAgentLauncher

-> parameters : run jcontrol

-> debuggable : yes

-> debug mode : no

-> debug port : 58981

-> shutdown timeout : 20000

**********************************************************************

[Thr 3052] JLaunchISetDebugMode: set debug mode [no]

[Thr 948] JLaunchIStartFunc: Thread 948 started as Java VM thread.

[Thr 948] [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=F:\usr\sap\SMD\SYS\global

-> arg[ 5]: -Dapplication.home=F:\usr\sap\SMD\exe

-> arg[ 6]: -Djava.class.path=F:\usr\sap\SMD\exe\jstartup.jar;F:\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_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\j2sdk1.4.2_17-x64\bin;F:\usr\sap\SMD\exe;C:\Program Files\Legato\nsr\bin;C:\Program Files (x86)\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;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\;F:\usr\sap\SMD\exe

-> arg[ 8]: -Dmemory.manager=128M

-> arg[ 9]: -Xmx128M

-> arg[ 10]: -Xms128M

-> arg[ 11]: -DLoadBalanceRestricted=no

-> arg[ 12]: -Djstartup.mode=JCONTROL

-> arg[ 13]: -Djstartup.ownProcessId=3024

-> arg[ 14]: -Djstartup.ownHardwareId=H0430968350

-> arg[ 15]: -Djstartup.whoami=server

-> arg[ 16]: -Djstartup.debuggable=yes

-> arg[ 17]: -Xss2m

-> arg[ 18]: -DSAPINFO=SMD_98_server

-> arg[ 19]: -DSAPSTARTUP=1

-> arg[ 20]: -DSAPSYSTEM=98

-> arg[ 21]: -DSAPSYSTEMNAME=SMD

-> arg[ 22]: -DSAPMYNAME=vmsapdevsm_SMD_98

-> arg[ 23]: -DSAPDBHOST=

-> arg[ 24]: -Dj2ee.dbhost=

**********************************************************************

[Thr 948] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [SMDAgent]

-> arg[ 0]: run

-> arg[ 1]: jcontrol

**********************************************************************

[Thr 948] Wed Mar 25 08:29:28 2009

[Thr 948] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 948] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 948] JLaunchISetState: change state from [Waiting for start (1)] to [Initial (0)]

[Thr 948] JLaunchISetState: change state from [Initial (0)] to [Starting (2)]

[Thr 356] Wed Mar 25 08:29:29 2009

[Thr 356] JLaunchIExitJava: exit hook is called (rc = -11112)

[Thr 356] **********************************************************************

• 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 356] JLaunchCloseProgram: good bye (exitcode = -11112)

Please Help ME

CHEERS

[Former Member]

Hello,

have you installed this agent manually or automatically with your SAP installation? (SR3).

Is the agent already connected to a solution manager system?

If not please connect it, after that it should start.

BR,

Andreas

[Former Member]

Hi Andreas

Thanks for Quick reply,

actually SDM was done with the installation, and i can see SDM in MMC , how can we cheack weather it was connected with solution manager, if not connected with solman , please help me how to connect to Solman

Waiting for your reaply

CHEERS

[Former Member]

Hello,

which SPS is your solman on?

BR,

Andreas

Edited by: Andreas Jankowiak on Mar 25, 2009 11:13 AM

[Former Member]

Hi Andreas,

actually when i follwing the procss which you said , i can see the solutions which i created for abap systems , and it's not showing solman SID , in the setup wizard,

cheers

[Former Member]

Hi,

is your installed SR3 system already connected to an SLD?

Please have a look in the documentation "Diagnostics Agent Setup Guide" under http://service.sap.com/diagnostics -> Installation and configuration.

The guide describes your scenario.

Please award points if my response was helpful.

BR,

Andreas