Smd agent problem

I ve got problem with registering agent in solution manager diagnostic. The following message is in the log:
registering agent on server......
Exception - Registering agent on server <hostname>:50104 failed Time out occured when calling method 'configure' on object com.sap.smd.api.IAgentContext_Stub@6eb2c1 possible com.sap.smd.server.util.concurrent.TimeoutException. And this situation is going to repeat all the time

Hello Damian,
Please check your SMD patch? LMSERVICE SP 9 patch 4 or SP10 patch 1.
(See SAP note: 999138)
Also ensure your SMD agent is running, stop it and start it at OS Level on the monitored system.
Hope this helps,
Dolores

Similar Messages

Problems pushing SLD settings to SMD agent

I've managed to push the SLD setting to one of our portal server SMD agents but when I go to push it out to another I get this error -
2009.06.30 10:21:54, Failed to send SLD settings to remote agent: hbssap15 (detail: Failed to save new SLD settings; nested exception is: java.lang.Exception: Unexpected error while changing SLD settings - exit code: -1)
Any idea's?

I got the same problem! Is there any solution?

Start of SMD agent fails!

Hi!
After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error Exception ID: 1160572286256
Registering agent on server myhost.de:50004failed:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
However, the manual setup of the agent succeeds:
./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
SMD Agent Setup is in process ...
- STEP 1: checking JDK location
JDK location is consistent: /usr/java14_64/bin
- STEP 2: checking JDK Version
JDK Version is correct: 1.4.2
- STEP 3: checking Connection to SMD Server
SMD Server check completed successfully
- STEP 4: generating Runtime Properties
runtime.properties has been created.
- STEP 5: generating Launcher
smdagent.bat has been created.
smdagent.sh has been created.
- STEP 6: generating SecStore
secstore.properties: has been created.
secstore.properties: user has been set.
secstore.properties generation completed successfully.
- STEP 7: checking P4 Connection and SMD Agent Registration
SMD Agent Registration succeeded
SMD Agent Setup completed successfully
During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
What can we do?
Thanks for all hints solving our problem!
Greetz,
André Richter

Hi Rahul,
please try SMD Agent 7.00 SP10! We had no problems with this version!
Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
Regards
André

RCA - SMD agent is not getting started

Hello Gurus ,
We have installed SMD agent 7.11 on managed system. It installed smoothly but at the time of starting the agent , it is giving error as follows.
jcmon=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jcmon=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
jcmon=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jcmon=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
I am seeing following errors in logs.
[Thr 01] Tue Apr 6 10:43:05 2010
[Thr 01] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx_mt.c 228]
[Thr 01] Tue Apr 6 10:43:08 2010
[Thr 01] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx_mt.c 228]
[Thr 01] Tue Apr 6 10:43:11 2010
[Thr 01] ***LOG Q0I=> NiPGetHostByName: '' not found: getaddrinfo [niuxi.c 1599]
[Thr 01] *** ERROR => MsIAttachEx: NiBufConnect to /36 failed (rc=NIEHOST_UNKNOWN) [msxxi_mt.c 707]
[Thr 01] *** ERROR => Can't attach to message server [jcmonms_mt.c 138]
[Thr 01] *** ERROR => Can't connect to message server [jcmonxx_mt.c 185]
[Thr 01] Tue Apr 6 10:43:13 2010
[Thr 01] *** ERROR => JsfOpenShm: ShmCreate(79, 4096, ATTACH) failed (rc = 3 SHM segment doesn't exist) [jsfxxshm_mt. 1683]
Please help.

Thanks
It was related to DNS server problem.
It is resolved now.
thanks
Deepak Joshi

SMD Agent SR3 on NW2004s SR2

Hi all,
We are running NW2004s SR2 on our Solution Manager system. We upgraded component ST-SER to 700_2008_1. The older SMD agent appears to not work correctly with this level according to SAP.
My question is, is it possible to install the standalone engine for SMD Agent SR3 without upgrading our entire system to SR3? (kernel, installation, Java)
We tried doing the SMD SR3 standalone install but are seeing some strange issues.
If anyone has an answer for me on whether I have to upgrade the entire system or not that would be much appreciated.
Thank you.

Solution Manager is a combined ABAP + Java installation, components of both must be in sync. It's not advised to install separate support packages or updates for certain components only, there are dependencies between them.
Why don't you upgrade t the latest service pack - for both ABAP + Java? This will avoid lots of compatibility problems...
Markus

No option to install SMD Agent Candidates using the SMD

Dears,
I want to bind a candidate SMD agent to my managing system. According to the guide I have to select one of the agent candidates and a new frame should appear where I can enter a username and a password.
The problem is that this frame does not appear.
Can someone help me out on this one ?
kind regards
Davy

Hi Davy,
This solution is only applicable for SolMan 7.0
1. Kindly check if the Maintenance Mode is OFF.
After selecting the candidate Agent, a new frame will be opened(not a window).
This frame will be just below the table, from where you have selected your Candidate agent.
You need to expand it.
I hope this will help.
For more details ::
https://websmp103.sap-ag.de/diagnostics
End to End Root Cause Analysis > Installation & Configuration > Root Cause Analysis Installation and Upgrade Guide
Refer to page 22( in pdf page 27 of 49).
Best Regards,
Pradeep Bishnoi

Why SMD agent on ABAP only?

OK. I don't get it. Why install SMD Agent on ABAP only systems???
Isn't SMD Agent used primarily for Java???
I have 37 systems of which only 8 have a java component. If I install SMD Agent everywhere I'll
need a much bigger SolMan server!!!
What is SAP policy on SolMan 7 Enh 1 OS/DB migration???
Can I migrate from this little Intel Linux box to a serious AIX LPAR?
Will SAP give me a migration key???
Ken Chamberlain
University of Toronto

About the migration, you can migrate without problems. You'll need study the following process "Heterogeneous system copy".
There's a component that checks just this kind of problems related with migration. BC-INS-MIG.
Check the documentation below.
http://www.sapdb.info/homogeneous-and-heterogeneous-system-copy/
http://www.fulleffectsolutions.co.uk/Html/technical-sap-hetero.html

Solution Manger Diagnostics setup (SMD Agent)

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)

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?

H E A P   C O R R U P T E D - and smd agent shows not running

Hello Gurus,
My SMD agent is goes down every day when i check the status:
I found the heap corroupted everyday with the below warnings:
nbcsaplpa018:nedadm 19> tail hs_err_pid1888352.log
H E A P   C H E C K -
Suspension of other threads succeeded.
Heap corruption found in object at address 0x070000004ac38268. Class of object is not in the reserved heap memory area (0x002e006e006f0072).
H E A P   C O R R U P T E D -
Please suggest
Regards,
Munish

Please fine the file SMDAgentApplication.0.log for logs again : other file in next reply.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[SMDAgentAppLog]/>
<!PATTERN[SMDAgentApplication.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
<!ENCODING[ISO8859_1]/>
<!FILESET[0, 10, 1000000]/>
<!PREVIOUSFILE[SMDAgentApplication.9.log]/>
<!NEXTFILE[SMDAgentApplication.1.log]/>
<!LOGHEADER[END]/>
Mar 24, 2010 1:53:17 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Mar 29, 2010 10:57:12 AM [Thread[Thread-174,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Mar 30, 2010 12:18:05 PM [Thread[Thread-229,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 1, 2010 1:59:00 PM [Thread[Thread-311,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 1, 2010 2:00:32 PM [Thread[Thread-340,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 9, 2010 5:41:47 PM [Thread[Thread-546,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 28, 2010 5:44:24 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 29, 2010 3:26:39 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 29, 2010 9:09:56 AM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 30, 2010 10:13:43 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 31, 2010 4:00:07 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 1, 2010 3:04:42 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 2, 2010 4:09:21 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 2, 2010 9:02:55 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 20, 2010 3:07:02 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 21, 2010 5:32:08 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 12:46:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 8:28:13 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 3:30:13 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 9:15:34 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 7:00:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 2:56:56 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 11:25:29 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found

The SMD Agent 'slcxemw04vu' hasn't been found!

Hi,
We are have problem with SMD agent.
We are executing Setup wizard ( for managed system ) but getting following message
The SMD Agent 'slcxemw04vu' hasn't been found!
Thing is SMD agent is running on host slcxemw04vu but somehow it is not able to detect.
System Install Path: /usr/sap/<Agent SID> :Is this correct Path?
Instance Path:/usr/sap/<Agent SID>/<AgentSID97>Is this correct Path?
Please let me know if you have any information for message'
The SMD Agent 'slcxemw04vu' hasn't been found!
Best Regards,
Tushar
Edited by: TusharC Chavan on Oct 21, 2009 5:44 PM

Hi Rahu,
Now Remark are "
Setup data must be entered for with servers : server0 (running EM Core, Application Server Java) (ITS port number must be provided)"
Now AS Java system will not have ITS . So entered solution manager ITS info.Then I got
"with servers : server0 (running EM Core, Application Server Java)
No setup or configuration steps performed yet"
By the way I can't find Diagnostics Administration --> Diagnostics System --> Self Check. Select your Solution and start a Self Check.Can you please explain it in detail.
Best Regards,
Tushar

SMD agents goes offline in agent administration

Hi,
In my landscape all the SMD agents are directly registered to Solman SPS27.
Each time my solman is restarted, all teh agents in agent administration goes offline. but in actual its runing at OS lvl.
After we take seperate Java stack restart of solman, agents come online in agent admin. This scenario is confusing
Any idea as to how can we overcome this issue ?
Regards,
Shyam

Thanks Guilherme for this very good clearification!
I have a simular problem at the moment and can confirm that the agent connection get disabled because they are not able to authentificate. I will try to implement the workaround with the telnet command to bring the agents in MM... This should help to solve the issue.
Anyway what I don´t understand is that not all agents get disconnected!
For example:
SMDsystem.log of Agent which is offline:
Aug 20, 2011 1:01:15 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Checking server availability...
Aug 20, 2011 1:01:16 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Authentication in progress ...
Aug 20, 2011 1:02:07 AM [Thread[Connector,5,main]] Error      Failed to connect to SMD server - user: SMD_ADMIN
Aug 20, 2011 1:02:07 AM [Thread[Connector,5,main]] Error      Connecting to SMD server ms://jusmp00:8104/P4 failed
com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
Aug 20, 2011 1:02:08 AM [Thread[Connector,5,main]] Warning    Access denied occurs during the registration, smd connector has been disabled (waiting new SLD GUID).
Aug 20, 2011 1:43:20 AM [Thread[SLD-Registration,1,main]] Info       Next try to push instance data in SLD is Sat Aug 20 13:43:06 AST 2011
SMDsystem.log of Agent which is online:
Aug 20, 2011 1:01:12 AM [Thread[Connector,5,main]] Error      ms://jusmp00:8104/P4 Ping failed : com.sap.smd.server.exec.asio.TimeOutError - null
Time out occurred when calling method 'ping' on object com.sap.smd.api.ISMDServerHandle_Stub@54bf219b after 30001 ms.
possible cause: com.sap.smd.server.util.concurrent.TimeoutException
     at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:130)
     at $Proxy1.ping(Unknown Source)
     at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.updateConnectionStatus(SMDConnector.java:230)
     at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.run(SMDConnector.java:189)
     at java.lang.Thread.run(Thread.java:664)
Caused by: com.sap.smd.server.util.concurrent.TimeoutException
     at com.sap.smd.server.util.concurrent.FutureResult.timedGet(FutureResult.java:159)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:122)
     ... 4 more
Aug 20, 2011 1:01:12 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Checking server availability...
Aug 20, 2011 1:40:27 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Authentication in progress ...
Aug 20, 2011 1:40:29 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Connection established .
Aug 20, 2011 1:40:30 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Registering agent on server ...
So you see that the secound agents waits the 40 minutes and start the authentication process after than.
Both agents are 7.11 and application version 7.01.7.3.20110311130810.
Any idea about that?

Configure com.sap.smd.agent.application.portalactivityreport

Hi,
I am trying to use the solution manager diagnostics and the portal activity reports to gather some information about our portal utilization. I have my portal system connected using SMD agent, I am able to run other monitoring application within SMD but when I try to execute the portal activity report I get the following error:
Portal Activity Reporting - Form
Could invoke portal activity report web service properly, please check the configuration
On the configuration of the application there are not parameters to configure, and the agent application seems to be running and deployed:
com.sap.smd.agent.application.portalactivityreport 7.0010.20061020144811.0000 7.0010.20061020144811.0000 Running
If somebody has implemented this functionality or have had the same problem let me know with any idea of pointer.
Thanks in advance for the help,
Zareh Vazquez

Hello,
You have to follow the SAP Note 893101 to set the security zone to Everyone on the Portal Activity Report web service on the portal.
And you need to restart the service com.sap.portal.activity.report.core.
Best regards,
Paula

SMD agent for VMW-based SAP systems

SAP talents:
We have hard time to configure SMD agents for VMW-based SAP systems.
We have followed some SAP documents for non-VMW-based SAP systems, but seems that SMD agent cannot
differentiate the individual system on VMW.
Our SMD agent has no problem for non-VMW-based systems.
Thanks!

Sorry to reply late because we have attempted a lot of fixes but all failed
For example, we have QAX, QAY and QAZ on VMW.
On Wily Introscope:
1) QAZ simply does not show up even we deployed/configured the agents as the procedure specified;
2) under the node QAX, we see QAY's entry as a sub-entry.
Does each SAP system need an agent OR only one agent is enough? We have tried both ways but
seems not working properly either way.
Please help, thanks a lot!

The SMD Agent 'Hades' hasn't been found!

Hello,
I started to install and configure Wily Introscope on one of my satellite
system.
I have one problem on some systems with the name of the server. The name of the satellite system is "hades" with lower letter. I installed the SMDagent on this hades system, this was installed successful (please see the [Agent Administration picture|http://img28.imageshack.us/img28/4707/agentadministration.jpg]). My problem is when I start to configure the agent for hades system on Managed Systems running Managed Systems, here I get "The SMD Agent 'Hades' hasn't
been found!".(please see the [picture|http://img831.imageshack.us/img831/1260/setupwizard.jpg]) I think the problem is because the difference of capital
letter for server name "hades". The server name is "hades" (with lower"h"), and this is the name in Agent Administration (please see the difference between ["Hades and hades|http://img15.imageshack.us/img15/4707/agentadministration.jpg]"), but in Setup Wizard the name of the server is "Hades"(upper "H"). Can you help me with this issue, because I am not able to
continue because Agent is not available.
I want to inform you that I ran SMSY_SETUP in to transfer all the SLD information to SMSY and this was successful transferred.
Can you please tell me from where can come this server name with upper "H(ades)" . Only some systems have this problem, I configured another systems and those worked fine (the name of server was correctly (with lower characters).
Best regards,
Florin Radulea

There are two possibities.
1) You specified the SLD option when you installed the agent (I think this requires NW 7 SMD agent > ~14).
- On SM system go to RCA work center, select Agent Administration, then Agent Candidates. As long as you registered the agent in the same SLD as SM uses, it should be visible in the SLD view. You need to associate the agent with this SM and supply connection information - there is a button for this, but you need to fill in a userid and password...
The agent retrieves connection information (eventually) from SLD.
2) You didn't register the agent in SLD or the agent needs special information to connect to managing SM.
On OS level User smdadm (or DAAadm) there is a scripts directory
/usr/sap/SMD/J##/script - SMD 7.0
/usr/sap/DAA/SMDA##/script -- Diagnostic agent 7.1 or 7.2
Run smdsetup.sh (.bat for windows) - no options gives all the possible sub commands.
You need to specify info for "managingconf" sub command.
If you provided wrong SLD connection information you can correct with this script too. (sldconf subcommand)
You can also specify saprouter info...
With supplied (correct) managing connection information, the agent should show up on the Agent Administration page.
Note hostname is managing hostname, servername should be managed hostname.
smdsetup managingconf      hostname:"sapms://<fqn>" port:"<MS httpPort>"
                              [optional user:"<...>" pwd:"<...>" servername:"<...>"]
smdsetup managingconf      hostname:"<fqn>" port:"<p4 port>"
                              [optional user:"<value>" pwd:"<value>" servername:"<value>"]
The first form uses load balancing the second doesn't. The port in the second should be 5##04.
Ckeck logs in work directory for error information (in case of typos, etc). I think there may be a log in SMDAgent directory too.
Ken

The SMD Agent 'server' hasn't been found

I've seen this question posted, but no answer provided. I'm trying to install Wily Introscope on a Java-only (Netweaver 7) system. The SMD software is installed and the agent is running. I can see in the log files that the Wily agent has connected to the management console.
I'm running EHP1 on the Solution Manager server.
When I go to Introscope Agent - Detailed Selection   and select this server this message is displayed "Failed to connect to server: "server" - Please make sure SMD Agent is up and running"
When I attempt to run the Diagnostic Setup Wizard. I get the following message "the SMD Agent "server" hasn't been found"
1.) I've stopped and started the SMD agent on the client serveral times - Does not fix the problem
2.) I've restarted Solution Manager - does not fix problem
Any idea how to trouble shoot this issue?

Thanks for pointing me in the right direction - here are the steps to resolve this issue.
In my case the problem was caused by dual entries in smsy for the server. I had the hostname and a DNS u2013 cname u2013 for the server in smsy. This was confusing Solution Manager.
1. Use SOLMAN_WORKCENTER
2. GoTo      ROOT CAUSE ANALYSIS  COMMON TASKS  ADMINISTRATION  AGENT ADMINISTRATION
    a. Right-click on the server with the problem and select u201CRESET SERVER NAMEu201D
        i. The SMD agent will be disassociated with the server. Restart the SMD agent on the server.
3. Steps to reassign the server name
    a. Use SOLMAN_WORKCENTER
    b. GoTo     ROOT CAUSE ANALYSIS  COMMON TASKS SETUP and CHECK  DIAGNOSTIC SETUP  DIAGNOSTIC SYSTEMS  UPGRADER
        i. Select the UPGRADE NOW button
    c. Once the UPGRADER tasks completes
    d. GoTo     ROOT CAUSE ANALYSIS  COMMON TASKS SETUP and CHECK  DIAGNOSTIC SETUP MANAGED SYSTEMS  SETUP WIZARD
        i. Select the server
        ii. Reassign the SMD agent to this server
           1. The SMD agent will restart with the correct server name

Smd agent problem

Similar Messages

Maybe you are looking for