SMD agent is not able to start. .

[Former Member]

Hi Friends .

I am trying to start SMD instance in MMC console but it is in yellow from 10 hrs.

By default SDM agent was installed when pi 7.1 installation.

P.I 7.1 server is up and running fine.

1. is this because of JDK (java version)?

2. do we need to upgrade the kernal ?

please advice..........friends

-

---

trc file: "E:\usr\sap\DAA\SMDA97\work\dev_jstart.8460", trc level: 1, release: "711"

-

---

-

---

trc file: "dev_jstart.new", trc level: 1, release: "711"

-

---

sysno 97

sid DAA

systemid 562 (PC with Windows NT)

relno 7110

patchlevel 0

patchno 19

intno 20020600

make multithreaded, Unicode, 64 bit, optimized

profile E:\usr\sap\DAA\SYS\profile\DAA_SMDA97_WSAMXPID01

pid 8460

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

Thu Aug 18 13:23:57 2011

*

• trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

arg[ 0] : E:\usr\sap\DAA\SMDA97\exe\jstart.EXE

arg[ 1] : pf=E:\usr\sap\DAA\SYS\profile\DAA_SMDA97_WSAMXPID01

-

---

trc file: "E:\usr\sap\DAA\SMDA97\work\dev_jstart", trc level: 1, release: "711"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

F

F [Thr 7532] Thu Aug 18 13:23:57 2011

F [Thr 7532] *** ERROR => SfCheckJeeVersion: Cannot find JEE binary directory E:\usr\sap\DAA\SMDA97\j2ee\cluster\bin. [sfxxmain.cpp 848]

//raja

[Former Member · Accepted solution]

Hello Raja,

only the agent logs are relevant to understand the cause of problem, the agent logs are located under SID/SMDAXX/SMDAgent/log.

In your case the problem is due to athentication failure (exit code -11112 ) , the problem is described in agent troubleshooting guide avalaible on Service Market Place.

So open the SMDSystem.log in agent log folder, find the error stacktrace to confirm the authentication failure. Redo the smdsetup script to update the credentials (all information about the smdsetup script are available in agent troubleshooting guide)

Best Regards

Fabrice

[Former Member]

Hi friends

I have understand the problem why it was not starting because it was not connected to SLD , and not registered when system was installed. and the below two files are missing in usr\sap\daa\smda97\smdagent\configuration\

1. rutime.properties

2. secstore. properties

/ raja

[Former Member]

hi friends .

some more log info of dev_smdagent.

Thu Aug 18 14:12:21 2011

F ********************************************************************************

F Java environment properties

F root directory : E:\usr\sap\DAA\SMDA97\exe\sapjvm_5

F vendor : SAP AG

F version : 1.5.0_14

F cpu : amd64

F java vm type : server

F java vm version : 5.1.027

F jvm library name : jvm.dll

F library path : E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\jre\bin\server;E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\jre\bin

F executable path : E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\bin

F SAP extensions : available

F ********************************************************************************

I [Thr 8544] MtxInit: 10000 0 2

M [Thr 8544] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=502;cur=2048)

M [Thr 8544] *** ERROR => CCMS: Parameter "system/type" set to illegal value: SMDA [alxxappl.c 493]

M [Thr 8544] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

M [Thr 8544] CCMS: Initalized shared memory of size 60000000 for monitoring segment.

M [Thr 8544] CCMS: Checking Downtime Configuration of Monitoring Segment.

M [Thr 8544] CCMS: AlMsUpload called by wp 1004.

M [Thr 8544] CCMS: AlMsUpload failed for E:\usr\sap\DAA\SMDA97\log\ALMTTREE.DAT.

M [Thr 8544] CCMS: CCMS Monitoring Initialization finished, rc=0.

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

F SAP JVM arguments:

F arg[ 0] = vfprintf

F arg[ 1] = abort

F arg[ 2] = exit

F arg[ 3] = -XmonGcCallback

F arg[ 4] = -XdebugStateChangeCallback

F arg[ 5] = -DSAPSTARTUP=1

F arg[ 6] = -DSAPSYSTEM=97

F arg[ 7] = -DSAPSYSTEMNAME=DAA

F arg[ 8] = -DSAPMYNAME=WSAMXPID01_DAA_97

F arg[ 9] = -DSAPDBHOST=

F arg[10] = -DSAPINFO=DAA_97_smdagent

F arg[11] = -Dj2ee.dbhost=

F arg[12] = -Dsun.java.launcher=jstart

F arg[13] = -Dsun.java.command=com.sap.smd.agent.launcher.SMDAgentLauncher run jcontrol

F arg[14] = -Djstartup.mode=JSTART

F arg[15] = -Djstartup.whoami=java

F arg[16] = -Djstartup.ownProcessId=8980

F arg[17] = -Djstartup.ownHardwareId=E0473977352

F arg[18] = -Xss2097152

F arg[19] = -Djstartup.debuggable=yes

F arg[20] = -DLoadBalanceRestricted=false

F arg[21] = -XdebugPortRange:58971-58971

F arg[22] = -Denv.class.path=

F arg[23] = -Dsys.global.dir=E:\usr\sap\DAA\SYS\global

F arg[24] = -Dapplication.home=E:\usr\sap\DAA\SMDA97\exe

F arg[25] = -Djava.class.path=E:\usr\sap\DAA\SMDA97\exe\jstart71.jar;E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\lib\jvmx.jar;E:\usr\sap\DAA\SMDA97\exe\jre\lib\iqlib.jar;E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\lib\tools.jar;lib\launcher\smdagentlauncher.jar;..\exe\jstartupapi.jar;..\exe\jstartupimpl.jar

F arg[26] = -Djava.library.path=E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\jre\bin\server;E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\jre\bin;E:\usr\sap\DAA\SMDA97\j2ee\os_libs;E:\usr\sap\DAA\SMDA97\exe\sapjvm_5\bin;E:\usr\sap\DAA\SMDA97\exe;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn

F arg[27] = -DP4ClassLoad=P4Connection

F arg[28] = -Xmx128m

F arg[29] = -Xms128m

F ignore unrecognized options : no

F ********************************************************************************

F [Thr 7676] *** LOG => SfCJavaVm: Java VM started.

F ********************************************************************************

F Main method arguments:

F arg[ 0] = run

F arg[ 1] = jcontrol

F ********************************************************************************

F

F [Thr 7676] Thu Aug 18 14:19:06 2011

F [Thr 7676] *** LOG => State changed from 0 (Initial) to 0 (Initial).

F [Thr 7676] *** LOG state real time: 1.453 CPU time: 0.109 sys, 1.125 usr

F [Thr 7676] *** LOG total real time: 1.453 CPU time: 0.109 sys, 1.125 usr

F [Thr 7676]

F [Thr 7676] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).

F [Thr 7676] *** LOG state real time: 0.000 CPU time: 0.000 sys, 0.000 usr

F [Thr 7676] *** LOG total real time: 1.453 CPU time: 0.109 sys, 1.125 usr

F [Thr 7676]

F [Thr 7676] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).

F [Thr 7676] *** LOG state real time: 0.171 CPU time: 0.031 sys, 0.140 usr

F [Thr 7676] *** LOG total real time: 1.625 CPU time: 0.140 sys, 1.265 usr

F [Thr 7676]

F [Thr 7676] *** LOG => State changed from 2 (Starting framework) to 3 (Running).

F [Thr 7676] *** LOG state real time: 0.171 CPU time: 0.062 sys, 0.093 usr

F [Thr 7676] *** LOG total real time: 1.796 CPU time: 0.203 sys, 1.359 usr

F [Thr 7676]

F [Thr 7676] *** LOG => SfCJavaVm: main method finished.

F

F [Thr 9024] Thu Aug 18 14:19:06 2011

F [Thr 9024] *** LOG => SfCJavaVm: exit hook is called. (rc = -11112)

F [Thr 9024] *** LOG => exiting (exitcode -11112, retcode 2).

M [Thr 9024] CCMS: CCMS Monitoring Cleanup finished successfully.

[Former Member]

Hi,

Try with the following points, It should resolve the issue.

1. Start the ABAP transaction SU01 on Solution Manager.

Check if the J2EE user (SMD_ADMIN) is not locked

2. Logon to the Agent administration tool with the J2EE user (SMD_ADMIN) to check that the logon module of

the Java stack works correctly.

3. Call the smdsetup to update only the credentials to be sure the password is up-to-date.

localhost\sapmnt\SMD\J98\script\smdsetup.bat

You'll see a list of options including the SLD config (sldconf) for SMD.

EX:

smdsetup sldconf localhost:<solman host> port:50000 user:SMD_ADMIN pass:password.

4. Restart the Diagnostic agent.In a cmd prompt, run the smdsetup from the directory

Cheers, RamS