SMD Agent Metrics/BOE native code metrics Missing in wily Enterprise Manager

SMD Agent and BOE native code metrics are not updated to wily EM. Previously the metrics were written to Wily EM. This is standalone setup of Wily Ent Manager without Solution Manager.
Environment:
Standalone Wily introscope Eterprise Manager - Introscope Enterprise Manager 9 SP15
DIAGNOSTICS AGENT 7.3 SP03 (incl. HostAgent)
BI 4.0 SP6 Patch 6, Windows 2008, Clustered/Distributed.
Logs:
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Initialization done.
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Service provider initialized.
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Agent Applications started.
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Smd connector has been disabled
Apr 25, 2014 3:54:35 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from INITIAL to CONNECTING
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to DISABLED
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Fatal      com.sap.smd.wily.hostagent.WilyHostService - init(...): Failed to start Agent!
[EXCEPTION]
java.rmi.RemoteException: WilyHostAgent start failed; nested exception is:
com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:122)
at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:111)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:154)
at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:733)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:495)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:354)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:311)
at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:1016)
at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:933)
at com.sap.smd.agent.connection.SMDConnectionTask.startOffline(SMDConnectionTask.java:862)
at com.sap.smd.agent.connection.SMDConnectionTask.internalAttemptConnection(SMDConnectionTask.java:549)
at com.sap.smd.agent.connection.SMDConnectionTask$1.run(SMDConnectionTask.java:107)
at com.sap.smd.agent.connection.P4JNDIContextHelper.executeInSecurityContext(P4JNDIContextHelper.java:148)
at com.sap.smd.agent.connection.SMDConnectionTask.attemptConnection(SMDConnectionTask.java:102)
at com.sap.smd.agent.connection.SMDConnectionTask.run(SMDConnectionTask.java:1282)
at java.lang.Thread.run(Thread.java:743)
Caused by: com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:510)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:99)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
... 26 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
... 29 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1782)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2857)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:235)
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.SAXParser.parse(SAXParser.java:125)
... 31 more

Hello Gopal,
Please refer to section Wily Introscope setup for BOE 4.0 of this wiki:
Managed System Setup of BOE 4.0 system in Solman 7.1 - SAP Solution Manager Setup - SCN Wiki
You may also found interesting
Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
https://service.sap.com/sap/support/notes/1722874
https://service.sap.com/sap/support/notes/1357901
Best Regards.
Luis Roel

Similar Messages

Multiple OC4J instances missing in the Enterprise Manager for a cluster

We have a cluster of 4 OAS instances installed on two Solaris 10 servers. When I login to the Oracle Enterprise Manager, I see only the Administration OC4J Instance. We had this issue earlier but it resolved by itself but this time the issue has been there for quite few days now. Need some help.
Thanks.

As I told you, this is a normal behavior, so there is no workarround, because it has to work fine later, but if you dont see any change tell me...
How did you configure your Cluster?
in a command line window, run the following in any of the node of your cluster
opmnctl @cluster status
it have to list all your components, this has to work on any of the nodes.
Also in the opmn.xml check the tags for <topology> in the firsts lines, if you dont have this in the secondary nodes then the cluster may not be working.
Regards

An error occurred while exporting code metrics

In the function of Calculate Code Metrics for Solution,
a error occurred when I click "Open List in Microsoft Excel" then show a dialog that "An error occurred while exporting code metrics"
But the code metrics result is calculated correctly
It can open correctly a few day ago

Hi happybai,
Which VS version did you use? I test it in my VS2013 version, it works well.
If you test the same project in other VS machine, how about the result? If it works well in other VS machine, we could make sure that it is not your project issue. Maybe you could create a simple app, test it again.
If all projects have the same issue, I doubt that it is your VS IDE issue.
Please make sure that you install the latest update package for your VS, like sp1 for VS2010, update 4 for VS2013 or other, of course, you would think about your current VS version.
Please also make sure that it is not your Excel issue, for example, please make sure that you could open an excel file in your windows.
You'd better run your VS in safe mode to make sure that it is not the VS add-ins or extension tools' issue.
https://msdn.microsoft.com/en-us/library/ms241278.aspx
Anyway, we need to make sure that whether it is the project or the VS IDE issue or others firstly.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to install SMD Agent on a MSCS?

Hello helpers,
we have installed a PI 7.1 (double stack) on a MSCS environment. The next step is to connect the PI 7.1 SAP system to our SolMan and to install the diagnostics agent. Unfortunately I wasn't able to find any documentation explaining an installation of the SMD Agent in a MSCS environment.
Does anybody know what has to be done? Do I have to install 3 agents, one on every MSCS node and one in the SCS/ASCS cluster resource group, or is only one agent needed in the SCS/ASCS cluster resource group?
Looking forward for any answers,
Sascha Piotrowsky

Hi Sascha,
To distribute a solution to the diagnostics the install path must be verified in TC SMDIAG_WIZARD. To verify the install paths an installed SMD-AGENT is neccessary.
Yes
Another point is that we like to monitor the J2EE Servers and Dispatchers from the 2 instances on "nodeA" and "nodeB". So in my opinion at least 2 SMD-Agent should be installed, one on every node. Do you agree?
No, you need one SMD Agent, this agent can then monitor multiple instances on one virtual host. The connection is only between virtual host and agent, not between instance and agent.
But what shall I do with the ASCS00/SCS01 instance. Does an SMD-Agent installation bring any effort on "clusterSID" or is it a must?
It's not a must, only relevant if you want to receive host metrics from this host. As this is only virtual, I would not install one here.
Best regards
Michael

Oracle Enterprise Manager TNSPING Metric

Hi All,
I wonder tns ping metric on OEM is actually representing data for TNSPING to database server from which server?
I'm not really mastering this topic, really appreciate your answer.
Thanks.
Regards,
Jolly

The listener "Response" metric evaluates "tnsPing" and "Status". These metrics are evaluated by the agent, and it does this by running the script lsnrresp.pl which is located in:
<install location of agent>/plugins/oracle.sysman.db.agent.plugin_<latest plugin version>/scripts
eg. on my machine this is /oracle/12cagent/plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0/scripts
ie. so lsnrresp.pl is run on the machine where the agent/database/listener resides.
Although it's running on the local machine it is still making a tcp/ip connection (ie. it's doing the equivalent of:-
tnsping "(ADDRESS=(PROTOCOL=TCP)(HOST=machine1.oracle.com)(PORT=1522))"
You can manually run this same tnsping command yourself from a database home of a remote machine (the machine where you're having difficulties from) and compare the difference.
Make sure that you use the same hostname and port when you run the tnsping command manually as EM is using. You can find out which host and port EM is using by either checking:-
a) the targets.xml (from the machine where the listener is located) -
eg.
<Target TYPE="oracle_listener" NAME="LISTENER11203_machine1.uk.oracle.
com" DISPLAY_NAME="LISTENER11203_machine1.uk.oracle.com" ON_HOST="" EMD_URL="h
ttps://machine1.uk.oracle.com:3872/emd/main/" TIMEZONE_REGION="" IDENTIFIER="T
ARGET_GUID=881E917E1CE1D3BECC361599ACDAEEEB">
                <Property NAME="Machine" VALUE="machine1.uk.oracle.com"/>
                <Property NAME="Port" VALUE="1522"/>
                <Property NAME="LsnrName" VALUE="LISTENER11203"/>
                <Property NAME="ListenerOraDir" VALUE="/oracle/orabase/11203rdbms
/network/admin"/>
or
b) go to Enterprise Manager, go to targets/all targets. Select your listener, click on it (will take you to the listener home page).
Then once on the listener home page, go to 'oracle listener' (drop down menu), pick "target setup"/"Monitoring Configuration"
It would be interesting to run the tnsping command manually from the problem machine (if you have a database home on that machine) and also to just do a 'general' ping from the problem machine to the database machine, and then do the same tnsping and ping command from the database machine itself and compare the difference. It might also be useful to repeat this on both machines but using ipaddress and see if you see any difference in the response time. Also check that the hostname is resolving in the same way (eg. same dns etc.). And to check whether any firewalls are involved.
HTH
Mani

Configuration check error: The SMD Agent is not able to connect the Satellite System (J2EE stack)

Hi friends,
Getting the below error in step 10 (configuration check) in managed system configuration.
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this
System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
The SMD log file referred to in the log above gives the same information and not anything much useful.
Any idea what could be the reason for the above error?
Thanks,
Arindam

Hi All,
Thaks for your suggestions. I chcked the note 182020, but the issue described in the note is for error byte code adapter installation whcih is not my case. The byte cde adapter intallation has been successful in our solman system All the steps from 1 to 9 are green. Only in step 10, check cniguration I am getting the above error.
The logon test wth the user id in step 3 "Enter system parameters" is successful. The message server port is also correct.
Hi Khaja,
I went to the links as suggestedby you but there its about a ifferent error message "Invalid Response Code: (401) Unauthorized.". I am not getting any such kind of error.
All I am getting is this -
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Thanks,
Arindam

SDK: Uncaught exception thrown in native code

We are using java and the DQM SDK, our XML validates and while we are trying to create a MultiRecordTransform, we get the following exception with no information to help diagnose the issue.
com.sap.emdq.EmdqException: Uncaught exception thrown in native code
We are using the dquractransformu shared object and have NCOALink enabled. We have successfully used the URAC transform without NCOALink. We receive no other errors or logs when starting up, and if we turn off NCOALink, it gets past creating the MR transform.
Is there any other information we can get to help us determine what the issue is?

FYI: We found our setting in the XML that enabled NCOA processing to begin ( <PROVIDER_TYPE> ), but it would be much easier if the error indicated what was missing, instead of the generic "Uncaught exception thrown in native code". Maybe there is a config setting to get more informative exception messages?

Error while installing SMD agent

Hi ,
1) Can any one please justify/brief the need of installing SMD agent on ABAP stack?
2) When I tried to install the SMD 711 agent on ABAP stack I could see the below error when i click sapinst.exe.
    " Running msiexec failed with return code 1063: undefined
      command line was :
       msiexec.exe /norestart /L vcredist_x64.log /i vcredist_x64.msi /qn "
I tried with Changing the environment variable of Temp and tmp to C:\usr\sap\<sid>\tmp and also tried with directory c:\temp but in vain .
enivronment:-   Windows 64-bit.
Note:- SMD agent was successfully installed on Development systemn
Please suggest.
Thank you
Jayanth

Hi ,
Log from vcredist_x64.log. Please have a look
" Product: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64) -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Action ended 2:47:00: SxsInstallCA. Return value 3.
Action ended 2:47:00: INSTALL. Return value 3.
MSI (s) (FC:38) [02:47:00:489]: Windows Installer installed the product. Product Name: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64). Product Version: 8.0.50727.762. Product Language: 1033. Installation success or error status: 1603.
Does this mean that , I should download new sapinst file for service market place and try again ??
Thank you
Jayanth

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

Set metric threshold for default metrics

Running Grid Control 10.2.0.4; have not had the time to go through an upgrade to 10.2.0.5 yet.
There are several metrics I am interested in setting a threshold for, specifically the Streams Replication metrics. When I click the "All Metrics" link on the cluster database's homepage I see a category called Streams Process Count as well as several metrics within that group. Right now none of those metrics have thresholds set. I have tried adding a threshold in the monitoring config (Preferences -> Rules -> Database availability and critical states) but the Streams metrics do not appear.
Am I missing something here? I feel kind of ridiculous for asking, but I can't seem to find the answer anywhere...

Not every metric in 'all metrics' is configurable with metric thresholds.
Your workaround is to write an user definied metric.

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?

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?

SMD Agent application - Explanation

Hello,
I have installed SMD. By startind "Agent Administration" from SMD, I get the application list of SMD Agent.
I am editing a guide to explain each application of this SAP SMD Agent. I get an explanation for 10 of 22 applications.
But I miss details regarding the other ones :
Do you have any help or guide which explain me what these SMD applications are used for ?
1. com.sap.smd.agent.application.e2emai
2. com.sap.smd.agent.application.eem
3. com.sap.smd.agent.application.flightrecorderdumpscan
4. com.sap.smd.agent.application.navigation.links
5. com.sap.smd.agent.application.remoteos
6. com.sap.smd.agent.application.runtime
7. com.sap.smd.agent.application.tracing
8. com.sap.smd.agent.application.wily
9. com.sap.smd.agent.application.wily4duet
10. com.sap.smd.agent.application.wily4java
11. com.sap.smd.agent.application.wilyem
12. com.sap.smd.agent.application.wsclient
Thanks
Best regards
PC

Hello,
I have finally foudn an explanation for each SMD Agent application :
1 .com.sap.smd.agent.application.connectors
Provide P4 or JMX connection to the monitored SAP J2EE engine.
2. com.sap.smd.agent.application.database
Access to the DB of the remote system to return table information to the SMD SQL Command Console application.
3. com.sap.smd.agent.application.datacollector
Collects XML based data from monitored systems (replaces the tool u201CComponent Analyzeru201D download feature)
4. com.sap.smd.agent.application.filesystem
Provides access to the remote file system for the u201CSMD File System Browser applicationu201D, and the Gather/Upload functionality.
5. com.sap.smd.agent.application.global.configuration
Global configuration of the SMD Agents.
6. com.sap.smd.agent.application.ldap
Provides remote access to connect to a LDAP server for the SMD LDAP browser application.
7. com.sap.smd.agent.application.logviewer
Provides an access to the file system of a monitored system. Files can be displayed or downloaded.
8. com.sap.smd.agent.application.remoteos
Enables to start remote OS commands console.
9. com.sap.smd.agent.application.remotesetup
Enables to setup the J2EE engine of a monitored system for SMD usage, from the smd/admin application.
10. com.sap.smd.agent.application.telnet
Provides remote access to the J2EE telnet console for the SMD J2EE command console application.
11. com.sap.smd.agent.application.tracing
It is used by the application E2E Trace Analysis (tools of RCA).
12. com.sap.smd.agent.application.wily
It is used by the application Introscope Setup.
13. com.sap.smd.agent.application.wily4duet
It is used by the application Introscope Setup for managed system running on duet.
14. com.sap.smd.agent.application.wily4java
It is used by the application Introscope Setup for managed system running on java.
15. com.sap.smd.agent.application.wilyem
It is used to store the data about Introscope Enterprise Manager (EM) for SMD.
16. com.sap.smd.agent.application.wilyhost
A: The agent application "com.sap.smd.agent.application.wilyhost" contains the HostAgent.
HostAgent = Host-Level Introscope Agent.
The following SMD Agent applications are not for a specific application but for the
general runtime of Root Cause Analysis :
- com.sap.smd.agent.application.e2emai
- com.sap.smd.agent.application.eem
- com.sap.smd.agent.application.wsclient
- com.sap.smd.agent.application.flightrecorderdumpscan
- com.sap.smd.agent.application.runtime
- com.sap.smd.agent.application.navigation.links
Best regards
PCuennet

SMD agent starts, but stderr0 has errors

Hallo Gurus,
we had installed the new Diagnostic Agents 7.11 for our EP.
Now the Agent runs after installation, but in the stderr0 we have the following errors.
(13107436) New Child Process created.
(13107436) Starting local Command:
Command: jc.sapDAA_SMDA97
pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_sapipp
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
In the sdn are no answer for this issue.
Some suggestion???
regards
Chris

We get data from the agent, but i think that is not all data that we can get...
SAPSYSTEMNAME = DAA
SAPSYSTEM = 97
INSTANCE_NAME = SMDA97
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/rs6000_64
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = sapepp
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/DAA_SMDA97_sapepp
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
# Copy SAP Executables
_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
_CPARG1 = list:$(DIR_CT_SAPJVM)/sapjvm_5.lst
_CPARG2 = source:$(DIR_CT_SAPJVM)
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1) $(_CPARG2)
# JStart configuration
SAPJVM_VERSION = 5.1.038
jstartup/vm/home = $(DIR_SAPJVM)
jstartup/bootstrap = no
# Start SMD Agent
_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_JC)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jstart$(FT_EXE) $(_JC)
Start_Program_00 = local $(_JC) pf=$(_PF)
# File generated automatically by the diagnostics agent sapinst.
# Created 2010.09.23 at 12:23:10 GMT
# sapinst classes version: 7.01.2.6.20090526074537
# Title: DAA_SMDA97_sapepp
# Description: File which specify the start parameters used by Jstartup framework for Diagnostics Agent process.
# Don't modifiy manually this script.
smd/agent/type=710
jstartup/instance_properties=$(DIR_INSTANCE)/SMDAgent/smdagent.properties

SMD Agent timeout

Hi everybody,
anyone seen this before?
I have installed a new SMD Agent for a newly installed system.
I chose the message server connection to my SolMan System (connection is available, I check on OS level).
When starting the Agent I get:
[EXCEPTION]
Time out occurred when calling method 'configure' on object [com.sap.smd.api.IAgentContext_Stub@36423801] after 10000 ms.
possible cause: com.sap.smd.server.util.concurrent.TimeoutException
     at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:130)
     at $Proxy23.configure(Unknown Source)
     at com.sap.smd.local.AgentContextWrapper.configure(AgentContextWrapper.java:188)
     at com.sap.smd.SMDServerHandle.registerDeprecatedConfiguration(SMDServerHandle.java:424)
     at com.sap.smd.SMDServerHandle.internalRegisterAgent(SMDServerHandle.java:222)
     at com.sap.smd.SMDServerHandle.registerAgent(SMDServerHandle.java:147)
     at com.sap.smd.SMDServerHandlep4_Skel.dispatch(SMDServerHandlep4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Any ideas?
Thanks in advance and best regards,
Jochen

Hi David,
thanks for all your suggestions. Obviously it was only a load problem on the SolMan system. This monday the agent was suddenly connected....
Best regards,
Jochen
Edited by: Jochen Spieth on Jan 20, 2011 8:52 AM

SMD Agent Metrics/BOE native code metrics Missing in wily Enterprise Manager

Similar Messages

Maybe you are looking for