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?

Similar Messages

Failed to send SLD settings to remote agent

Dear Guru's,
I'm facing problem when trying to register SLD Agent. I have run this command :
/smdsetup.sh sldconf , /smdsetup.sh managingconf and etc but nothing is worked for me.
after i have run those command, Agent is available within system, but when i tried to push SLD Setting i got this error :
"Failed to send SLD settings to remote agent (detail: Failed to save new SLD settings; nested exception is: java.lang.Exception: Unexpected error while changing SLD settings - exit code: -1)"
I just update the Solution Manager ABAP SPS11, but my JAVA SPS is still 07.
Is it because i don't upgrade my Java ?
My DAA Agent is 7.20 patch level 87.
kindly need your help to enlighten me about this issue, i cannot move to other configuration because this error.
thankyou.
Best Regards,
Marvin

Hi Marvin,
Can you explain in details which system are you trying to connect with some screenshot and logs.
Are you trying to connected a non-ABAP/non-AS-java system ?
If yes, you check this thread.
http://scn.sap.com/community/netweaver-administrator/blog/2013/08/11/trex-configuration-with-solution-manager-71--part-1
Also, check this sap KBA for more information.
1147499 - Connection to the System Landscape Directory
If you are registering DAA of SLD.
then Use below command
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>"]
If this is also not working,
Execute the command
smdsetup supportlogs
At the end of the execution of the command, a Zip file is generated in at the following location: /usr/sap/<AGENT_SID>/<AGENT_INSTANCE_NUMBER>/SMDAgent/supportLogs_<TIMESTAMP>.zip.
Ans share the zip file.
Regards,
Divyanshu

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

Standalone SMD Agent for EEM won't connect to SLD

I have installed a standalone SMD agent, which was configured properly (logs verify this) and starts up successfully, but I don't ever see it register in the SLD. Does anyone know of a guide which tells how to manage a standalone SMD agent? I want to get it connected to the SLD in Solution Manager so that I can use it as an EEM robot, but the connectivity so far is not working.
For instance, if there is a way to get something like SM59 in an ABAP system on my SMD agent to change and test connectivity parameters, this may help.
Cheers,
David.

OK, thanks for the reference to the troubleshooting guide, I had not seen that before. Using it, I found the following procedure:
How to check if the Diagnostics agent is registered in SLD?
␣ Go in SLD with the url: http://sldhostname:port/sld
␣ Logon with a J2EE user having the role SAP_SLD_ADMINISTRATOR
␣ Go in the section u2018Administrationu2019
␣ Click on link u2018Content Maintenanceu2019
␣ Select the subset u2018All with Instances and class u2018Diagnostics Agent Instanceu2019
If the class u2018Diagnostics Agent Instanceu2019 does not appear in drop down list, No Diagnostics agent is registered
␣ In column Name of table, check if the Diagnostics agent is present.
This procedure verified that my diagnostics agent is in fact in contact with the SLD, but for some reason, the agent does not show up in the SLD when I go to Home > Technical Systems, nor does it show up when I go to the EEM Administration screen > Robots > Check Agents.
So I'll have to keep researching.
Cheers,
David.

Introscope agent -problem in ISAgent settings retrieval

Hi ,
I have installed a SMD agent for a pure and simple Java stack system.
The SMD agent installation and setup wizard ran fine with no problems.
How ever while trying to setup the introscope agent i have errors.
Diagnostics setup -Managed system -Introscope agent
The error is as following
"Operation failed - X01 - 123456789 - com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied: Please make sure the <user> and <password> parameters are correct.; nested exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]"
The SMD agent is up and running and im not clear which user id the above message is telling about.
The user ID and password of administrator which we give during running the setup wizard is correct.
Also i have installed the SMD agent with connection type "Lookup HTTP connection via message server"
So i understand that the above user id could be the user which the agent is using to connect to the JVM...but im not sure which is that user id or if im right or wrong .
Kindly advise if anyone has an idea how to resolve thsi problem.
Regards,
Sunanda

Hi Sunanda,
I had a similar problem with the ISAgent.
I did a manual installation as described in the Installation guide Wily Introscope, chapter 4.
After that, it worked.
Best Regards,
Jan
PS: Check if note 1149214 applies before restarting the system /if restarting the system fails.

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?

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?

Error in SMD Agent

Hello All,
In order to install Wily Introscope Agent, initially I have installed
a SMD Agent on managed system host.
After the installtion of SMD Agent , while starting the SMD agent I am getting below error .
Starting SMDAgent ...
Establishing connection to server '[host is empty]' on port [port is
empty]
Smd connector is disabled because no SLD association and no credentials
found.
Smd connector is disabled because no SLD association and no credentials
found.
Waiting for connection ...
Checking server availability...
Warning :
Connecting to SMD server null failed - error counter: 0 -
com.sap.engine.services.jndi.persistent.exceptions.NamingException: No
InitialContext can be created because the java.naming.provider.url
property is no specified in the jndi environment.
Next try to push instance data in SLD is Tue May 19 14:36:31 CDT 2009
I have given user SLDAPIUSER in SLDAPICUST transaction. This user
which is not locked and I have also reconfirmed the password of this
user.
Kindly request your suggestion!!!!
Regards,
Suhas

Santosh Asuthkar
I am receiving the same error in my SMD agent log:
Starting SMDAgent ...
Dec 8, 2009 1:43:48 PM [Thread[main,5,main]] Info       Establishing connection to server '[host is empty]' on port [port is empty]
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info       Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info       Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info       [null] Waiting for connection ...
Dec 8, 2009 1:43:52 PM [Thread[SMDAgent connection thread,5,main]] Info       [null] Checking server availability...
Dec 8, 2009 1:43:53 PM [Thread[SMDAgent connection thread,5,main]] Warning    Connecting to SMD server null failed - error counter: 0 - com.sa
p.engine.services.jndi.persistent.exceptions.NamingException: No InitialContext can be created because the java.naming.provider.url property i
s no specified in the jndi environment.
Dec 8, 2009 1:43:54 PM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is Wed Dec 09 01:43:54 EST
2009
Dec 8, 2009 1:46:52 PM [Thread[SLD-AssocWatcher,1,main]] Info       [SLDManagingConnectionMonitor] Next time to check Managing System Associat
ion is Tue Dec 08 14:01:52 EST 2009
Can you please provide details if you found a solution?
Thanks!!!!!
Jeff

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 'HOSTNAME hasn't been found!

Dear,
I have already upgrade the Solution Manager 7.0 EHP1 . I have a problem with my SMD error The SMD Agent 'BASAPI02' hasn't been found!
I want to setup E2E Root Cause Analysis for ERP 6.0 Stack Java system.
So I configured SMSY, I've already installed SMD Agent in managed system successfully also.
When I run the Diagnostics Setup -> Managed System -> Setup WIzard,
in the Setup Parameter Step , it said that " No SMD Agent is currently available (ie not assigned). Please install an agent for BASAPI02 or unassign an existing agent in Agent Administration Why is that so ?
In the Agent Administration ( DIagnostics Administration -> Managed SYstem -> Agent Administration) found that the agent is online.
does anyone know why this happens and how to resolve
Thanks in advance,
Antonio

Hello Antonio
The agent name registration or agent registration on it's own depends on the version of your diagnostics agent.
From diagnostics agent 7.20 and higher if you have installed it using default connection setting in sapinst then you don't need to seperately register the diagnostics agent in the agent candidate management.
Once the agent is known you should see it in the agent administration list. If you don't see the agent in the agent administration list it would mean it is not yet known and you have to go through the agent candidate management first.
The server name assignment is normally done through the managed system setup. After selecting your SAP system to be configured and pushing the setup button you get a screen in which you have to fill in the hostname, user+pass and so on at the left side bar. On the right side you should see one or more lines that represent your SAP system.
You have to expand that line and then select the appropriate agent from the list. After selecting the correct agent from the list your diagnostics agent will get the hostname assignment and you will be prompted to wait and refresh because the agent is then automatically restarted.
Kind regards
Tom

Connection between SMD Agent and SMD server via SAProuter

In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it?
Hope someone can give us your precious advices on this issue.
Karl

Perfect; and thanks for your response. I found this help page for developers to implement P4 support over SAP router: http://help.sap.com/saphelp_nw73/helpdata/en/48/2992d7ad8758d7e10000000a421937/content.htm
But in the SM Diagnostics Setup options I can set up only a direct HTTP adresses and have no options to set up connections over a sap router to P4 ports directly. I can at the moment only solve my problems with NAT or firewall rules.
And also the diagnostic agent setup has no options to config a proxy or sap router. I found yesterday a blog on sdn side with screenshots of the setup with all available connection opetions to SLD... sry I can not post this link today.
This is an official statment of SAP from the current version of SMD guide; it is also possible but why not from the beginning???:
In some network conficurations, the Diagnostics agent has to connect to the Managing system though a SAP router.
This feature will be fully supported in Solution Manager 7 Ehp2 (7.02).
In order to enable this feature in Ehp1, please contact the Diagnostics Agent support team to get information on how to
setup the agent and on which patch level you can perform the installation.
This thread were a long time not answared; proxy and routing connections are mostly stepmotherly handled by SAP; this is also a problem by set up of automatic RFC generations in SMSY; why there are in the setup assitents no options to set up the router string.
I have absolutly no comprehension for this in year 2011. All this technics are good known and long time tested.
In this case the f**k has provoked an answare to this thread and this is what I expected; but sorry for my style You are right I could also writh why the heck
FAQ:
SMD root side on SDN: http://service.sap.com/diagnostics
SM FAQ: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4e49dbea-0c01-0010-91bd-f0b61388c9ae
SM Setup Home: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
SM Diagnostic Troubleshooting Guide: https://websmp201.sap-ag.de/~sapdownload/002007974700000409092009E/DiagAgent_TroubleShooting.pdf
SMD Candidate Setup: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

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é

Preparing Solution Manager for SMD Agents Installation

Hello everyone
I have to configure the Solution Manager of QAS to receive new SMD Agents, I looking at the transaction SOLMAN_SETUP.
Does anybdoy know what do I have to do to prepare the environment for the installation of SMD agents?
Thank

Hi Marcelo,
Check note 1365123 - Installation of Diagnostics Agents, this note shows the agent installation strategy. You must install one SMD agent per host (physical or virtual) . The SMD agent should be installed in all host you want to monitor.
In order to connect the SMD agent into your Solution check the following WIKI:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-Connectionoptions
Also, you can managed the SMD agent in the "Agent Administration", it can be found at:
- SOLMAN_WORKCENTER
- Tab Root Cause Analysis
- "Agent Administration"
I recommend you to use the "Direct connection to solution manager" for your agents. It is easier than the SLD registration.
Regards,
Allam

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

Registration of SMD agent

I have encountered this error when we are trying to register the SMD agent (a few tries already)
As we still cannot see the SMD agent running from our SolMan server
I have tried to search in SDN and SAP Note on this error but cannot find any hints.
Anyone have experience in solving this? Thanks.
java.rmi.RemoteException: Agent Registration failed: [SMDManager.registerPendingAgent] Receive registration for an already existing entry. Registration REJECTED

Hello,
What is your Solution Manager version? Inform the SP and the LM-SERVICE.
Try the following:
1. go to agent admin and enable Maintenance Mode
2. go to tab advanced settings
3. increase the value as follows
Smd.asio.remote.time.out.long.ms = 1800000
smd.asio.remote.time.out.ms = 60000
4. go to NWA page and restart the service
tcsmdserver~service
5. go to agent admin and disable Maintenance Mode
6. restart smd agent and see the result.
Best regards
Guilherme

Problems pushing SLD settings to SMD agent

Similar Messages

Maybe you are looking for