Solution Manger Diagnostics setup (SMD Agent)

[Former Member]

Hi All

I have managed to setup Solution Manager Diagnostics and Deploy on of the agents to out DEV BI Server (JAVA), however I keep getting the message:

"Failed to connect to server: bidevdb - Please make sure SMD Agent is up and running"

Now I can see in the SAPMSC that the SMD agent is running - so I am not sure why this is the case. Does SMD require SAPCCMS setup as a windoes service on the BI Server?

Or what else can I check to find out what the issue might be?

Thanks all in advance (will award points for helpfull answers)

[Former Member]

Hi,

do you configure or connect your Solution Manager to your Central SLD? You can check which SLD is used via the SMD Agent Administration page:

http://<solution manager hostname>:<HTTP Port>/webdynpro/dispatcher/sap.com/tc_smdnavigation/StandaloneApp?APP_ID=ADMIN_AGENT

or

Go to the SM Workcenter Diagnostics and click on Agent Administration

On the Agent Administration page click on the Agent Candidates Management link:

http://<solution manager hostname>:<HTTP Port>/webdynpro/dispatcher/sap.com/tc_smdserver_agentadmin/SLDAgentCandidates

Here you can see which is your leading SLD for Solution Manager and SMD agents.

Also check the attached document from SAP Note 1148028 - Setup SLD in the scope of Solution Manager 7.0

For SMD agent not running msg, check Agent Administration whether agent is displayed there with green signal.

Hope this helps

Regards,

Shyam.

[Former Member]

Thanks Shyam that was great - have no managed to get my SMD Agent into Agent Administration. However I have noticed that the Server Name column is set to <no server name>. I have tried to reset the server name but still no joy.

Any ideas?

[Former Member]

Ah managed to sort that now with the following command:

smdsetup changeservername servername:"<server name>"

[Former Member]

Thanks, Phil. Did a search and found your answer. Worked for me as well.

[mateus_pedroso]

II need the following informations to help you.

1) http://<SMD host>:<Java HTTP port>/sap/monitoring/ComponentInfo

and the complete ABAP

System -> Status ->Component Information (magnifying glass)

2) Attach in the message the results of these two log files too.

SMDSystem.X.log where X is the latest log file created/modified.

and

SMDAgentApplication.X.log where X is the latest log file created/modified.

With these informations I can help you in this case.

[Former Member]

SMDSystem.x.log

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[SMDSystemLog]/>

<!PATTERN[SMDSystem.log]/>

<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>

<!ENCODING[Cp1252]/>

<!FILESET[0, 10, 1000000]/>

<!PREVIOUSFILE[SMDSystem.9.log]/>

<!NEXTFILE[SMDSystem.1.log]/>

<!LOGHEADER[END]/>

Mar 25, 2010 2:23:08 PM [Thread[main,5,main]] Info Starting SMDAgent ...

Mar 25, 2010 2:23:09 PM [Thread[main,5,main]] Info ===> Establishing connection to server '[host is empty]' on port [port is empty]

Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info Smd connector is disabled because no SLD association and no credentials found.

Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info Smd connector is disabled because no SLD association and no credentials found.

Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Error Cannot retrieve saposcol hardware info for SLD data instance.

[EXCEPTION]

java.io.IOException: CreateProcess: ..\..\exe\saposcol -b error=2

at java.lang.ProcessImpl.create(Native Method)

at java.lang.ProcessImpl.<init>(ProcessImpl.java:85)

at java.lang.ProcessImpl.start(ProcessImpl.java:30)

at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)

at java.lang.Runtime.exec(Runtime.java:591)

at java.lang.Runtime.exec(Runtime.java:429)

at java.lang.Runtime.exec(Runtime.java:326)

at com.sap.smd.agent.util.RunExec.exec(RunExec.java:78)

at com.sap.smd.agent.util.RunExec.exec(RunExec.java:55)

at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:158)

at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:148)

at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.getSAPOSColHostInfo(SLDAgentDataBuilder.java:254)

at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addAgentHostMember(SLDAgentDataBuilder.java:195)

at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addGroupAgentInstance(SLDAgentDataBuilder.java:132)

at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addSLDInfoNodeForAgentRegistration(SLDAgentDataBuilder.java:498)

at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.writeAgentInstanceData(SLDAgentDataBuilder.java:597)

at com.sap.smd.agent.connection.sld.SLDQueryBuilder.registerAgentInstanceData(SLDQueryBuilder.java:604)

at com.sap.smd.agent.connection.sld.process.SLDReg.run(SLDReg.java:68)

at java.lang.Thread.run(Thread.java:664)

Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Info [SLDReg] Next try to push instance data in SLD is Fri Mar 26 02:23:12 GMT 2010

Could not find the SMDAgentApplication.X.log

Does that help?

[Former Member]

I have also noticed that the SMD Agent (Sid = DSP) does not show up in our SLD!