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?

Similar Messages

Solution Manager Diagnostics - Installation

I have installed SM EHP1 and have also installed SMD. However during the Basic configuration of SM, I'm getting Diagnostics Configuration errors during the Automatic Configuration phase of the Diagnostics configuration. The errors showing up are:
1. Cannot call Diagnostics Setup web service
2. Web Service URL: http://atl-osm-01.oversightsystems.com:8100/DiagSetupServices/Di...
3. SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
4. Error when processing Web service call
5. Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
What am I missing here?
Thanks for the help.

Hello Hans.
Have you solved the problem? We have a similar problem with Solution Manager 7.0 EHP1 SP27.
Errormessage (parts are in German):
Web Service URL: http://solman.company.com:8100/DiagSetupServices/DiagSetupConfig?style=document
Cannot call Diagnostics Setup web service
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not found")
Beim Prozessieren eines Web Service-Aufrufs ist ein Fehler aufgetreten.
Fehler beim Aufruf von Funktionen der SOAP Runtime: SRT: Unsupported xstream found: ("HTTP Code 404 : Not found")
Note: We have changed the http and https-Ports of ICM. Solution Manager is working fine, but Solution Manager Diagnostics Setup does not work.
Thank you for a hint.
Best regards,
Tobias

Monitoring SMD Agent with CCMS

Hi gurues, I need to know if there is any way to monitor SMD Agent installed in an application server via CCMS CEN system on a Solution Manager.
Right now we have CEN Monitoring define on Solution Manager, and several SMD Agents over the whole landscape, and it is critical for us to get alerted when this SMD goes down, so we are thinking about monitoring through Solutin Manager, isthat possible or we must do it in another way?
Regards
Gustavo

It's so typical SAP; I was looking for exactly the same question. SAP changed from 7.1 the OSCOL to run by the host agent instance and will not install the OSCOL to the SAP instance. You also will not be able to download OSCOL separatly.
But OSCOL is needed to monitor processes on host side. If the host agent don't starts also the OSCOL will not start (on LINUX side) and so you are not be able to monitor the SMD process.
The only chance is to start the SMD via init script.
A better way would be to implement a GRMG availability monitoring; this can be implemented in the CEN system independent from the monitored host. In the first solution the host has to be create itself the basis to monitor itself... that's nonsense.
I absolutly don't understand why SAP always and everywhere ignore his own design concept and reinvent the wheel. It would be so easy to design and implement the availability moniroring on SAP development side but they don't have a focus on that. It is the same with SAP router connection via host agent to the CEN system. It was implemented as very last feature after a lot of disgruntled customers (administrators).

Solution manger daa agent giving error

Hi
i want to configure manged system in my solman, i got error with daa agenet iam unable to assigin the daa agent attached the screen shot 1.
i got the bellow error server name assignment on the agent failed. how to troubleshoot the issue
regards
vreddy

Hi,
prior to all, You need to register the agent either to the solution manager directly or to the SLD during the installation of diagnostic agent itself.
If you registered before only, you can see the agents in managed system configuration on step 4 'Assign Diagnostics Agent' -> Assign agent. Else you can see empty as in your image 2.
Please follow the below link and make sure you done registration of smd agents.
Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki
Thanks
Jansii

Diagnostics Setup - Warning on Step "Wilyhost Agent Details"

Hi All
I am having a bit of dificulty configuring the Wily Agent via Solution Manager diagnostics.
I am currently getting the following errors when trying to set up the Wilyhost Agent when I run the setup wizard I am getting the following results:
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(solman:6001).
Step Wilyhost Agent Details
Created destination EPT_JC01_server0
Created destination SapStartSrv_nwportal_EPD_04
Created destination EPD_JC04_server0
Created destination SapStartSrv_nwportal_EPT_01
Created action SAP GC|EPT_JC01_server0 - SAP GC|EPT_JC01_server0
Created action EPD|perth_EPD_04 - SapStartSrv_nwportal_EPD_04
Created action SAP GC|EPD_JC04_server0 - SAP GC|EPD_JC04_server0
Created action EPT|perth_EPT_01 - SapStartSrv_nwportal_EPT_01
Created 4 action(s).
1 Wilyhost Agent(s) from host perth is connected to the EM.
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: SAP OsCol - null
Please check SMDAgentApplication log files for warnings and errors.
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(solman:6001).
The Diagnostics agent log is:
Apr 6, 2010 4:56:35 PM [Thread[SAPOsCol,5,main]] Error      com.sap.smd.wily.hostagent.action.SapOsColAction - processXml(): Error processing saposcol output: saposcol -xml
AdjustTokenPrivileges failed with 1300
<?xml version="1.0" encoding="utf-8" ?>
<saposcol version="COLL 20.95 700 - 20.65 NT 08/02/06" date="1270569346" status="running">

<OperatingSystem>
        <property name="OpSysRelease">
          <value>Windows NT</value>
          
        </property>
        <property name="OpSysReleaseName">
          <value>Windows NT 5.2</value>
          
        </property>
        <property name="OpSysCategory">
          <value>Windows NT</value>
          
        </property>
</OperatingSystem>
[EXCEPTION]
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
     at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:146)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:420)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:146)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:420)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
     at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     ... 6 more

Hi,
This seems to be a bug and please install the saposcol version 710 as saposcol 710 is downward compatible with release 700 and this issue must be resolved.

Does solution manager 4.0 require SMD Agent?

we have solman 4.0 abap+java with sp11.we are in the process of configuring sol mananager diagnostics for sattlite systems.
for monitoring solution manager java stack it self from solution manager do we need to install SMD AGENT even thogh solution manger it self has SMD server ? still solution manger need SMD AGENT ?

Hi,
SMD Agents are mandatory to run Diagnostics on sattelite systems.
Each Agent is connected to SMD Server and is able to run task or collect information from central request (SMD Server).
If you do not have them, you will not be able to run any tools in Diag.
SMD Server is one sub-component of Solution Manager 4.0.
Regards,
Frederic

SMD Agent 7.00 or Diagnostics Agent 7.11

Hello,
Our managed systems are running on NetWeaver 7.00.
We are currently implementing SAP Solution Manager Diagnostics using SOLMAN_SETUP guided procedure.
In https://service.sap.com/swdc -
Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" Entry by Component" Agents for managed
there are 2 kinds of Diagnostcis Agents :
1. SMD Agent 7.00
2. Diagnostics Agent 7.11
Question :
Can we install a Diagnostic Agent 7.11 on our managed systems running on NetWeaver 7.00 or must we install SMD Agent 7.00 ?
Are Diagnostics Agent 7.11 supported for managed systems running on NW 7.00 ?
Best regards
PC

Hi
To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release
that the SAP systems already installed on the host.
Refer the doc in this [link|https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000526434&_OBJECT=002007974700000409092009E&_SCENARIO=01100035870000000112&] Section 2.3 Managed system page no:8
Hope this helps you
regards
Naveen

Diagnostics Agent 7.11 vs SMD Agent 7.00

Hello,
In our SAP System environment, most of managed systems are running under SAP NW 7.0 platform.
We are currently installing SMD Agent 7.00. The installation is not finished and I was wondering if we can install Diagnostics Agent 7.11 on managed systems running on SAP NW 7.0 ?
In other terms :
SMD Agent 7.00 have to be installed only on SAP NW 7.00
Diagnostics Agents 7.11 have to be installed only on SAP NW 7.11 or also on SAP NW 7.00 ?
Thanks in advance for your feedback
Best regards
P. Cuennet

Yes you can install diagnostics agent 7.11 for a managed system 7.00
It's even possible for a managed system 6.40
Prerequisite is that your Solution Manager stack verison is 20 or higher (EHP1)
You can find the details in the installation guide for diagnostics agent 7.11 on SAP service marketplace:
[https://service.sap.com/diagnostics]

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

How to setup system monitoring of EP 7 to Solution Manger 7.0

Hi Experts,
I need help for configuring EP 7 (only JAVA engine) for system to Solution Manger 7.0. IF anyone of you have steps or config guide pls help me ???

Hi Vikas,
In general, system monitoring in SAP Solution Manager use CCMS as the data supplier, which means that, you need to configure CCMS alert infrastructure for your EP system.
General steps:
1. Configure solution manager or other ABAP system as the CEN (central) system as the CCMS infrastructure.
2. Install SAPCCMSR agent (which is part of CCMS Agent), and connect the agent to CEN system
3. Setup system monitoring in Solution Manager
For more information, you can access the help portal of SAP.
Hope that helps.
Thanks, Jett

Solution Manage Diagnostics - error in the system setup

Hello,
I have installed SMD and I installed one system with the Setup Wizard of the SMD. According to the result of the setup, it was successful.
However, when I do a self check in SMD, I get the five following errors in the Monitored Setup node :
5 error(s) found:
No DB agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No JVM startup parameters setting status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Roles assignment status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No SSO Setup status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Telnet agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
Can anybody help me ?
Thank you

If you goto http://server:port/smd >>> Diagnostic Setup >>> Diagnostic System >>> Setup Wizard, do you have a message similar to:
Last Diagnostics setup wizard execution on Tue Oct 09 13:34:44 2007 :
- 0 setup steps disabled by user
- 13 setup steps succesfully executed
- 0 setup steps executed with warnings
- 0 setup steps in error
If you do, your Diagnostic server is correctly setup.
For Managed system, same thing, http://server:port/smd >>> Diagnostic Setup >>> Managed Systems >>> Setup Wizard, or check setup results to make sure it's completed.

Urgent!! Setup of SMD Agent failed due to Remote Error....

I am getting the following error when i tried to Setup the Smd agent using setup wizard:
<b>The assignment of server frces4153 to SMD Agent failed
Remote error occurs during the connection to the smd agent for agent frces4153</b>
Can you please give me the solution for this...
<b>Reward points of all the replies....</b>
Ajay Kande

Thnx for ur suggestions, Now i colud see the following error "[Setup]Failed to assign SMD Agent to frces4146/EP7 (frces4146)
[EXCEPTION]
Time out occurred when calling method 'getService' on object [com.sap.smd.api.IAgentContext_Stub@7fc07fc] after 10000 ms.... [siehe Details]
from the logs....
Ajay Kande

Solution Manager Diagnostics: Agent Architecture

Hi there,
current I write a degree dissertation about Solution Manager Diagnostics. In different books, documentations and manuals I read about Agents which must be installed on the managed system. But I find no exactly description about the agents architecture. In a book about the Solution Manager is written, that the structure includes two tiers. The first tier are the core agents, but there is nothing explained about the second tier ... Is a core agent the same like a host agent?
Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
Thanks and best regards,
Andreas

> Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
I would start with
http://service.sap.com/diagnostics
There are lots of (detailed) documentations available.
Markus

Diagnostics - How to patch SMD Agent

Dear SAP Colleague,
I will have to install the SMD Agent on all managed system of my SAP landscape.
Do you know how this agent is patched ?
I know that both Wily IS Agent (Introscope Java Agent) and Host-level Introscope Agent) are updated from SAP Solution Manager and deployed to all managed systems.
But how do we patch the SMD Agent (Java instance) ?
Thanks
Best regards
P.C.

Hello folks,
Was wondering too if any way to update / patch SMD Host Agentu2019s executable.
I could not find any SAP document on that.
Checking our own AIX kernel that came with the install e.g. u201Cjstart u2013Vu201D, I saw that the patch # was 37, in the context of kernel 7.11_REL UNICODE, compile time Jun 6 2009. It to be noticed that in the exe directory there are just some of the u201Cfullu201D kernel folders present (it makes sense, because it is just a Java env.).. In my case there are 79 u201Cfoldersu201D in the exe dir. Please note that one of it, u201Cservicehttpu201D is a directory.
Thus, my thoughts on a potential way to patch the SMD Host Agent SAP Kernel is to apply that pool of kernel components that matches the SMD Agentu2019s executables.
Thus, first download the kernel 7.11 latest patches e.g. from (Entry by Application Group -> Additional Components -> SAP Kernel -> SAP Kernel 64 BIT UNICODE -> SAP Kernel 7.11 64 BIT UNICODE , then uncar these and rm a script that will copy only the folders that are present in the installed exe SMD Host Agent exe dir as well. Also, is should be checked to that all the files in the SMD Agent should be part of the updated kernel. If not, then I will not recommend to do it, since SAP may have something special for the SMD SAP Kernel.
Have not tried yet to perform this procedure, but is very tempting, since for 7.11 AIX the default install is at patch level 37 while today the corresponding 7.11 patch level is 92.
Please, note that this is just a personal look at this issue and absolute not a SAP recommendation. Maybe the fist question should be u201Cwhatu2019s the need for the SAP SMD Agent u201CSAP Kernel Upgradeu201D? The more correct and recommended way will be to open a customer message with SAP, e.g. asking to u201Cblessu201D the SMD Agent Kernel upgrade procedure described above.
Kind regards,
C.P.

SMD agent passowrd issue

Hi Experts,
In our solution manger system, we forgot the SMD agent password. without i can't able to do EWA for java stack. So kindly help me to how to reset the password for this.
Thanks & Regards,
Sampath.

Hi
when you performed the SMD Setup Wizard in the managing system, created the SMD_ADMIN user and the enter the passowrd
please reset the password for the smd_admin user in the managing system (satelite system and try)
else use the section 4.9.2 in the diagnostics setup guide 7.11 on [https://websmp108.sap-ag.de/diagnostics|https://websmp108.sap-ag.de/diagnostics] > media library as below
4.9.2 Change the Diagnostics Agent credentials
This section provides information about how to change the credentials (login and/or password) of the J2EE user used to connect the Diagnostics Agent to the Managing System.
Prerequisites
All the Diagnostics Agents must be connected to the Managing System before updating the password of the J2EE user used by these Diagnostics Agents
Procedure
1. You can either change the password of the J2EE user used by the agents or create a new J2EE user in User Management.
2. Open the Agent Administration application
In the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.
3. All the agents are disconnected and reconnected with the new credentials
jansi

Solution Manger Diagnostics setup (SMD Agent)

Similar Messages

Maybe you are looking for