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">
<!-- Last collection: 2010/04/06 16:55:46 -->
  <OperatingSystem>
        <property name="OpSysRelease">
          <value>Windows NT</value>
          <!-- Version of operating system, `uname -r&apos; -->
        </property>
        <property name="OpSysReleaseName">
          <value>Windows NT 5.2</value>
          <!-- freely choosable text describing OS release name, e.g. &apos;SUSE LINUX Enterprise Server 9 (i586)&apos; -->
        </property>
        <property name="OpSysCategory">
          <value>Windows NT</value>
          <!-- MANDATORY: operating system, e.g. &apos;HP-UX&apos;, &apos;Linux&apos;, &apos;Windows NT&apos;, ... -->
        </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.

Similar Messages

  • Diagnostics Setup - Warning on Step "SSO"

    Hi All
    After getting rid of one issue with this setup I have managed to com across another which I am finding difficult to solve.
    I am getting the following issues with SSO:
    Step SSO Details
    The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
    The Login Modules for validating SSO tickets were already installed
    The ticket ACL already contained : sys=SMP,169 iss=OU=J2EE,CN=SMP dn=OU=J2EE,CN=SMP
    The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
    The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
    The Authentication template for component sap.com/tcmonitoringsysteminfo*sap_monitoring was already set to ticket
    The Authentication template for component sap.com/tcwddispwda*webdynpro_dispatcher was already set to ticket
    The Authentication template for component sap.com/tcwddispwda*webdynpro_welcome was already set to ticket
    SSO Abap Ticket certificate of Diagnostics system not available : can not perform SSO setup. Please make sure ABAP PSE is not empty and not locked by transaction STRUSTSSO2 on Diagnostics system
    The Login Modules for validating SSO tickets were already installed
    SSO certificate data not available : Ticket login module can not be updated
    SSO setup failed : error while updating login modules : SSO certificate data not available : Ticket login module can not be updated.
    SMD Agent Log:
    Apr 7, 2010 11:58:34 AM [Thread[SapStartSrv_perth_EPD_04,5,main]] Warning    com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun: 
    [EXCEPTION]
    javax.xml.rpc.soap.SOAPFaultException: JCMON_ShmAdminOpen failed
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
         at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2247)
         at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2262)
         at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getJ2EEProcessList(SapControlAction.java:498)
         at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:957)
         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)
    Apr 7, 2010 11:58:34 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Apr 7, 2010 11:59:34 AM [Thread[SapStartSrv_perth_EPD_04,5,main]] Warning    com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun: 
    [EXCEPTION]
    javax.xml.rpc.soap.SOAPFaultException: JCMON_ShmAdminOpen failed
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
         at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2247)
         at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2262)
         at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getJ2EEProcessList(SapControlAction.java:498)
         at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:957)
         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)
    Apr 7, 2010 12:00:30 PM [Thread[Thread-3,5,main]] Error      [Setup]No ABAP SSO ticket certificate file received. Please check Monitoring host logs and look for SSO ticket cert read failure
    Apr 7, 2010 12:00:30 PM [Thread[Thread-3,5,main]] Warning    [Setup]No SSO Cert loaded => Options of EvaluateTicketLoginModule will *not* be updated properly
    Apr 7, 2010 12:00:30 PM [Thread[Thread-3,5,main]] Error      [Setup]SSO setup failed : error while updating login modules
    [EXCEPTION]
    java.lang.IllegalArgumentException: SSO certificate data not available : Ticket login module can not be updated
         at com.sap.smd.agent.plugins.remotesetup.SecurityContextAdapter.updateTicketModules(SecurityContextAdapter.java:100)
         at com.sap.smd.agent.plugins.remotesetup.SetupManager.updateLoginMonitoredModules(SetupManager.java:319)
         at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.setupSSO(RemoteSetupStep.java:239)
         at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.setupSSO(RemoteSetupStep.java:195)
         at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.execute(RemoteSetupStep.java:116)
         at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
         at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService._setup(RemoteSetupService.java:159)
         at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService.setup(RemoteSetupService.java:86)
         at com.sap.smd.agent.plugins.remotesetup.RemoteSetupServicep4_Skel.dispatch(RemoteSetupServicep4_Skel.java:112)
         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.DispatchImpl.run(DispatchImpl.java:721)
         at java.lang.Thread.run(Thread.java:664)
    Apr 7, 2010 12:00:34 PM [Thread[SapStartSrv_perth_EPD_04,5,main]] Warning    com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun: 
    [EXCEPTION]
    javax.xml.rpc.soap.SOAPFaultException: JCMON_ShmAdminOpen failed
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
         at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2247)
         at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2262)
         at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getJ2EEProcessList(SapControlAction.java:498)
         at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:957)
         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)
    I have check STRUSTsso2 in Solution Manager and all seems to be fine (Status Green), it does not appear to be locked and I am now unsure what else to try.
    Any ideas?

    Thanks for your response.
    Our current LM-TOOLS version is below:
    sap.com        LM-TOOLS        7.01 SP5 (1000.7.01.5.2.20091119080143)        SAP AG        MAIN_NW701P05_C        20100323084604
    I have been through both of the notes and the issue appears to be with Solution Manager as we get the same error for ALL systems.

  • Wilyhost Agent could connect to the Enterprise Manager

    Hi Gurus,
    I'm trying to setup Diagnostic for Solman 7.0. I'd installed Wily Introscope and SDM Agent in Solution Manager. The Agent was configured for this server. The Application Agent in Diagnostic Setup -> Managed system was OK, but when I try to run the Setup Wizard for Self-Monitoring, every steps are in green (OK) but the first was in red with this error:
    Step Wilyhost Agent Details
    Created destination SM1_DVEBMGS00_server0
    Created destination SM1|qfmasr003_SM1_00
    Created action SAP GC|SM1_DVEBMGS00_server0 - SAP GC|SM1_DVEBMGS00_server0
    Created action SM1 - SM1 AbapSystem
    Created action SM1|qfmasr003_SM1_00 - SM1|qfmasr003_SM1_00 AbapInstance
    Created 3 action(s).
    0 Wilyhost Agent(s) and 0 EP Agent(s) from host qfmasr003 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (qfmasr003.xxxxxxxx.com:6000) no Wilyhost Agent was detected from host qfmasr003. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    The file jvm_smdagent.out  said this:
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=qfmasr003_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    file.encoding=UTF-8
    file.encoding.pkg=sun.io
    file.separator=/
    j2ee.dbhost=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/exe/jstartup.jar:/usr/sap/SMD/exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.00.15.20080806065909/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.endorsed.dirs=/j2sdk1.4.2_17/jre/lib/endorsed
    java.ext.dirs=/j2sdk1.4.2_17/jre/lib/ext
    java.home=/j2sdk1.4.2_17/jre
    java.io.tmpdir=/tmp
    java.library.path=/j2sdk1.4.2_17/jre/lib/i386/server:/j2sdk1.4.2_17/jre/lib/i386:/j2sdk1.4.2_17/jre/../lib/i386:/usr/sap/SMD/exe:/tmp/sapinst_exe.18845.1222346568:/usr/sap/SMD/exe:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=1.4.2_17-b06
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=Sun Microsystems Inc.
    java.vendor.url=http://java.sun.com/
    java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
    java.version=1.4.2_17
    java.vm.info=mixed mode
    java.vm.name=Java HotSpot(TM) Server VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=Sun Microsystems Inc.
    java.vm.version=1.4.2_17-b06
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=G1082288837
    jstartup.ownProcessId=1666
    jstartup.whoami=server
    line.separator=
    memory.manager=128M
    os.arch=i386
    os.name=Linux
    os.version=2.6.9-5.ELsmp
    path.separator=:
    sun.arch.data.model=32
    sun.boot.class.path=/j2sdk1.4.2_17/jre/lib/rt.jar:/j2sdk1.4.2_17/jre/lib/i18n.jar:/j2sdk1.4.2_17/jre/lib/sunrsasign.jar:/j2sdk1.4.2_17/jre/lib/jsse.jar:/j2sdk1.4.2_17/jre/lib/jce.jar:/j2sdk1.4.2_17/jre/lib/charsets.jar:/j2sdk1.4.2_17/jre/classes
    sun.boot.library.path=/j2sdk1.4.2_17/jre/lib/i386
    sun.cpu.endian=little
    sun.cpu.isalist=
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sun.os.patch.level=unknown
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    Running SMD Agent ...
    [Runtime] START
    ==> Loading application com.sap.smd.agent.application.runtime : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.global.configuration : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.connectors : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.wily : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.filesystem : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.tracing : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.remotesetup : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.wilyhost : 7.0015.20080806065229.0000
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent Release 7.2.0.0 (Build 540138)
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) Server VM 1.4.2_17" from Sun Microsystems Inc.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Loaded file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set.  No extensions will be loaded.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent startup complete.               
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Property "com.wily.introscope.agent.agentName".
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at qfmasr003.quickfood.com.ar:6000,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "qfmasr003", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
    10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent] Remote Agent Configuration Service is enabled
    ==> Loading application com.sap.smd.agent.application.logviewer : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.flightrecorderdumpscan : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.telnet : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.database : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.datacollector : 7.0015.20080806065229.0000
    Initialization done.
    [ms://qfmasr003.xxxxxxxxxxxxxxxxxx:8101/P4] Agent ready.
    ==> Loading application com.sap.smd.agent.application.remoteos : 7.0015.20080806065229.0000
    only Initial Configuration files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only file configuration information will be considered
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    only Abap configuration will be considered
    only Abap configuration will be considered
    only file version information will be considered
    only End2End log files will be considered
    only software change logs will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    10/15/08 01:16:17 PM ARST [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly.  Keeping the connection alive.
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only file configuration information will be considered
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    only Abap configuration will be considered
    only Abap configuration will be considered
    only file version information will be considered
    only End2End log files will be considered
    only software change logs will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only Initial Configuration files will be considered
    This error is the same, when I try to connecto other system for Diagnostics,
    Any comments, suggestions, recomendations.... anythings.....
    Thanks in advice,
    Sergio Mazzeo.

    Hi Sergio,
    did you already stop and start your SMD agent on OS level ? It is not enough to restart it from the SMD.
    kind regards
    Davy

  • Wilyhost Agent setup finished successfully with limitations - SMD SPS15

    Dear all,
    we have connected different SAP J2EE systems to our Solution Manager Diagnostics without any problems. Now we are trying to connect the corresponding ABAP backend systems to the SMD. The Setup Wizard for these systems are completed with a warning. Everything seems to work fine, but the warning are spurious (we get only the yellow light, not a green one).
    Did anyone has the same "problems" with ABAP managed systems and has anyone a solution for the yellow light ?
    Thanks and best regards
    Patrick
    Error/Warning Message -
    Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager.
    Created destination RT5|s3p5012_RT5_00
    Created action RT5 - RT5 AbapSystem
    Created action RT5|s3p5012_RT5_00 - RT5|s3p5012_RT5_00 AbapInstance
    Created 2 action(s).
    1 Wilyhost Agent(s) and 0 EP Agent(s) from host s3p2012 are connected to the EM.
    90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: RT5
    90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: RT5|s3p5012_RT5_00
    Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager.
    Error/Warning Message -

    Hi to all,
    I have addition information about the Wily HostAgent problem. Here are some other alerts/warnigs from another SAP portal :
    ============================================================================
    Jul 15, 2008 10:34:15 AM [Thread[SAP GC|FB7_J02_server3,5,main]] Error      com.sap.smd.wily.hostagent.action.GcScannerAction - scanInitial(): scan for file /usr/sap/FB7/J02/j2ee/../work/std_server3.outterminated: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
    Jul 15, 2008 10:34:15 AM [Thread[SAP GC|FB7_J02_server3,5,main]] Error      com.sap.smd.wily.hostagent.action.GcScannerAction - doRun(): Action temporarily stopped: SAP GC|FB7_J02_server3
    [EXCEPTION]
    com.sap.smd.wily.hostagent.TransientException: java.io.FileNotFoundException: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
            at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:259)
            at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:391)
            at com.sap.smd.wily.hostagent.action.GcScannerAction.doRun(GcScannerAction.java:135)
            at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:52)
            at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
            at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.FileNotFoundException: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
            at java.io.RandomAccessFile.open(Native Method)
            at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
            at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:372)
            ... 4 more
    Jul 15, 2008 10:35:15 AM [Thread[Thread-364,5,main]] Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|FB7_J02_server2 not running because status is WAITING_FOR_DESTINATION
    Jul 15, 2008 10:35:15 AM [Thread[Thread-366,5,main]] Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|FB7_J02_server1 not running because status is WAITING_FOR_DESTINATION
    ============================================================================

  • Wilyhost Agent setup finished successfully with limitations.

    Solution Manager EHP1
    While executing Managed system for Non-ABAP ( JAVA ) System , we are getting the problem
    The Wily & SMD agent is already installed on the managed system
    The error in Managed System Configuration :
    Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager
    Logs of the SMDAgentApplication :
    *Oct 12, 2009 2:33:23 PM [Thread[Thread-165,5,main]] Error      Error to retrieve the process from Message Server (detail: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine)*
    [EXCEPTION] java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    Oct 12, 2009 2:33:35 PM [Thread[Thread-177,5,main]] Error      RemoteOSService: operation failed - command is: mode=jstartup,mshost=epdev,msport=0,node=733441 [EXCEPTION]
    com.sap.smd.plugin.remoteos.exception.ThreadDumpCommandException: Message Server Port must be specified!
    at com.sap.smd.plugin.command.tda.ThreadDumpCommand.init(ThreadDumpCommand.java:89)
    at com.sap.smd.plugin.remoteos.RemoteOSService.triggerDump(RemoteOSService.java:276)
    Oct 12, 2009 3:03:27 PM [Thread[Thread-165,5,main]] Error      com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed
    [EXCEPTION]
    com.sap.smd.wily.hostagent.PermanentException: Configuration Error: invalid property sysno for destination SapStartSrv_epdev_EPD_ at com.sap.smd.wily.hostagent.sapcontrol.SapControlDestination.open(SapControlDestination.java:52)
    at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:82)
    Oct 12, 2009 3:03:27 PM [Thread[Thread-165,5,main]] Error      com.sap.smd.wily.hostagent.SapAgent - startActions():
    [EXCEPTION]
    com.sap.smd.wily.hostagent.PermanentException: java.io.IOException: CreateProcess: saposcol error=2 at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:324)
    at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:467)
    at com.sap.smd.wily.hostagent.action.SapOsColAction.initSapOsCol(SapOsColAction.java:405)
    at com.sap.smd.wily.hostagent.action.SapOsColAction.init(SapOsColAction.java:110)
    at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:383)

    Hi Rohan Pawar,
    did you find some solutions. I've not the same problem but perhaps you now what the error means
    i don't know which folder is expected.
    Best regards
    Thorsten Stracke
    ]] Error      com.sap.smd.wily.hostagent.SapAgent - startActions():
    [EXCEPTION]
    com.sap.smd.wily.hostagent.PermanentException: java.io.IOException: error=2, No such file or directory
            at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:324)
            at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:467)
            at com.sap.smd.wily.hostagent.action.SapOsColAction.initSapOsCol(SapOsColAction.java:405)
            at com.sap.smd.wily.hostagent.action.SapOsColAction.init(SapOsColAction.java:110)
            at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:383)
            at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:96)
            at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:112)
            at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:62)
            at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:119)
            at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:233)
            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:307)
            at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
            at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:271)
            at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:145)
            at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:504)
            at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:381)
            at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)
            at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:253)
            at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:164)
            at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:300)
            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
            at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
            at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
            at java.lang.Thread.run(Thread.java:664)
    Caused by: java.io.IOException: error=2, No such file or directory
            at java.lang.UNIXProcess.forkAndExec(Native Method)
            at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
            at java.lang.ProcessImpl.start(ProcessImpl.java:65)
            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.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:465)
            ... 23 more

  • Error during Managed system setup "Wilyhost Agent" type

    Hello All,
    Managed system setup finished with one error. Iam using this for selfmonitoring (solman itself as managed system)
    Error msg as follows.
    0 Wilyhost Agent(s) from host inbbssun02 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (TDCTBI.india.tcs.com:6001) no Wilyhost Agent was detected from host inbbssun02. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    I checked jvm_SMDAgent.out. and log as follows.
    /06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.4.2_20-rev" from S
    un Microsystems Inc.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.ag
    entProfile"
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sa
    p.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.ag
    ent.application.wilyhost/IntroscopeSapAgent.profile
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval i
    s set to 1800
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to
    500
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is
    set to 3000
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to
    locate the extensions directory.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/SMD/J98/SMDAgent/applications.config/
    com.sap.smd.agent.application.wilyhost/ext was successfully located
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Pro
    perty "com.wily.introscope.agent.agentName".
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    1/06/10 02:55:30 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
    [p4://inbbssun02:50004] Agent ready.
    1/06/10 02:55:34 PM IST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise
    Manager at TDCTBI.india.tcs.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "inbbssun02", Proce
    ss = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
    Is there any seperate setting for wilyhost agent connection to EM ?
    Regards,
    Shyam

    I have restarted the agent at OS level and it appears in the Agent Admin page.
    I then re-ran the Managed System Config for this system and receive the same error.
    I have looked at the jvm_smdagent.out file on the wilyhost and found the following errors
    1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
    1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
    1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    1/19/10 12:34:08 PM CET [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly.  Keeping the connection alive.
    The agent on the solution manager box is version 7.0 and the version od the agent on the PI box is 7.11
    Regards
    Stephen

  • 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?

  • EM view setup is failing in secure agent step

    EM view setup is failing in secure agent step.
    Is it known issue ?
    Any WA available ?
    Thanks
    -Ashish

    Since you don't have had any reaction yet it may be time to a bit more specific. "EM view setup" does not ring a bell to me.
    What are you trying to do?
    OMS/Agent version? Platform?
    Eric

  • Wilyhost Agent(s) from host hostname are connected to the EM

    Hi All!
    I tried complte setup managed system/. And received following message:
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (host:port) no Wilyhost Agent was detected from host SSM. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    in jvm_smdagent.out:
    11/12/09 03:40:40 PM GMT+03:00 [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    11/12/09 03:40:40 PM GMT+03:00 [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com.sap.guid.GUIDGeneratorFactory
    11/12/09 03:40:41 PM GMT+03:00 [INFO] [IntroscopeAgent] Started Error Reporting service
    11/12/09 03:40:42 PM GMT+03:00 [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at host:port,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "HOST", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com.sap.guid.GUIDGeneratorFactory
    Could anybody help me resolve it?
    Thanks for your advance,
    Alexander

    Hi,
    we also have the same error...
    LM-SERVICE  7.01 SP5 (1000.7.01.5.2.20091211060559) 
    LM-TOOLS  7.01 SP4 (1000.7.01.4.2.20090723091137)
    My problem is that I don't get any data of our KWP ABAPsystem in Wily. The Agent is running and is well connected (The lights in agent administration are all green). Also in the logs I don't see any probs.
    I have restarted the agent 1000 times..., reseted the server name and ran the agent setup again... I also registered it via
    ./smdsetup.sh sldconf hostname:"solman" port:"59500" user:"username" pwd:"xxxxx"
    ./smdsetup.sh managingconf hostname:"sapms://solman" port:"8196" user:"SMD_ADMIN" pwd:"xxxxx"
    Do u have any ideas???
    Regards
    Johannes

  • A failure occured while calling Diagnostics Setup web service

    Hi Guys.
    When performing the Automatic Activities of the Solution Manager 7.1 Basic Configuration, on one step you can execute the Diagnostics Configuration.
    When clicking on the details it shows the following message.
    SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 401 : Unauthorized")
    Error when processing Web service call
    I tried running the configuration a user having SAP_ALL, also j2ee_admin, so no clue where is the authorization fault.
    Any ideas what is causing this Authorization Error?
    I also tried to access SMD manually on saphost:8000/SMD but it says Root Cause Analysis Setup has been moved and Call transaction SOLMAN_SETUP from the SAP GUI to configure SAP Solution Manager.
    Is there any url to access to SMD directlty without going thru SOLMAN_SETUP since i dont see where is the url.
    Thanks!

    Please make sure that your solman box meet the software prerequisit as per this note below
    1483508 : Solution Manager 7.1: Root Cause Analysis pre-requisites
    This will solve that ptoblem .
    Best Regards
    Jai Wardhan

  • Diagnostics Setup - remembers old settings

    Hi,
    have a strange problem and it's really giving me a headache. We did set up solution manager diagnostics earlier ago and it worked fine. Recently I logged on again to the SolMan Diagnostics page and got the message that Diagnostics was not running because the WEBADMIN connection did not work.
    I checked in Visual Admin (JCo RFC Provider) and it was really down. The reason was the user which was entered for the connection did not exist anymore. So I changed it to something else and it was started up fine.
    But I also had to re-run a Diagnostics Setup -> Diagnostics System -> Setup Wizard due to upgrade we made.
    Magically this again changed the old connection parameters back in Visual Admin's WEBADMIN connection. On the very first page of the diagnostics wizard you can maintain the connection parameters to the ABAP system and I also changed that to the new user but when the setup proceeds it always fails at the ABAP connection step saying the user ID and password is not correct (and stating the old user which really surprises me).
    So it seems whatever data you gave for the very first time the wizard just can't forget it and brings them up even you already changed the connection parameters...and it also overrides the WEBADMIN connection parameters back to the obsolete parameters.
    Anybody has an idea how can I overcome this issue? Is it somewhere buffered and I need to empty the buffer?
    Our solman is a 7.0 at SPS17
    Cheers

    Hi, thanks for the reply - the problem is not in the ABAP stack. It's on the java side when you try to open the http://hostname:port/smd link and try to do a diagnostics setup wizards.
    On this first page there are some parameters you need to provide like:
    Support User   
    Please enter the UserId of the SMD Support User. If not yet existing, the User will be created with password set in advanced setup (default : 'init1234')
    ABAP Connection   
    Please enter the settings of the Solution Manager Backend ISM
    ABAP Client
    ABAP Admin User Id
    ABAP Admin Password
    ITS port  
    Is BW installed in a separate...  Client ?  System ?
    J2EE Administrator 
    Please enter admin User Id and password of the SAP J2EE administrator of Solution Manager
    J2EE Admin User Id
    J2EE Admin Password 
    Etc etc...
    my problem is that at the very first time I populated the ABAP connection parameters using a user ID called e.g. SMD_RFC_XYZ.
    Now when I change this to e.g. SMD_COMMUINICATION user and run the setup wizard with the changed parameters in the error log I still see SMD_RFC_XYZ user id for some reason I don't know where the system gets it from.

  • I didn't setup a two step verification for my apple Id , and then when i login into my account on the browser it prompt to enter my verification code !!! HOW COME

    i didn't setup a two step verification for my apple Id , and then when i login into my account on the browser it prompt to enter my verification code !!! HOW COME
    please help because all my data are stored in the cloud

    - See if it is listed here for downloading. If it is then redownload it..
    Downloading past purchases from the App Store, iBookstore, and iTunes Store
    - If not there then contact iTunes.
    Contact iTunes

  • Two calls at the same time on agent detail

    Hi All,
    Pulling an agent detail report for an agent im showing two calls with exact same start and end time.  The first is listed as inbound non-acd and the second is listed as inbound acd, assigned to a queue which the agent is assigned to.
    never saw it before and cant begin to understand it.  Has anyone saw this before?

    Hey tomas.micovcin,
    I'm slightly confused by your question so i'd like to try and clarify a few things. 
    You have two AD7760. Each AD7760 is then connected to its own CED1Z. Is that correct?
    Next i'm confused between which of the two following scenario's you're interested in. 
    1.You're interested in taking measurement from the AD7760 and bringing them into LabVIEW using the CED1Z as a USB interface. This would involve building a USB driver to bring the data into the LabVIEW environment.
    2. You're interested in building code in LabVIEW that will acquire and process the data from the hardware. You then want to deploy this code to your Evaluation Board.
    Which of these scenarios are you interested in? If none of these, what are you trying to accomplish?
    Also... could you go into more detail on what you mean by "if is possible use LabView program \download from www.analog.com\, becouse i can,t find in "source code " place where i can choose name of usb port where is connect." I'm kind of confused as to what you're asking here. 
    Tim A.
    National Instruments

  • ABAP/4 u0096 Step by Step Main Concept details

    can any one give the details of ABAP/4 – Step by Step Main Concept details and Links.

    Hi
    Start with this.Refer this
    http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html
    http://www.****************/InterviewQ/interviewQ.htm
    http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm
    Reports
    http://www.sapgenie.com/abap/reports.htm
    http://www.allsaplinks.com/material.html
    http://www.sapdevelopment.co.uk/reporting/reportinghome.htm
    http://www.sapfans.com/forums/viewtopic.php?t=58286
    http://www.sapfans.com/forums/viewtopic.php?t=76490
    http://www.sapfans.com/forums/viewtopic.php?t=20591
    http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    Check these step-by-step links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
    https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
    for Smartforms material
    http://www.sap-basis-abap.com/sapsf001.htm
    http://www.sap-press.com/downloads/h955_preview.pdf
    http://www.ossincorp.com/Black_Box/Black_Box_2.htm
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    http://www.sap-img.com/smartforms/smartform-tutorial.htm
    http://www.sapgenie.com/abap/smartforms.htm
    How to trace smartform
    http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
    http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
    http://www.sap-img.com/smartforms/smart-006.htm
    http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
    Re: Need FAQ's
    check most imp link
    http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
    step by step good ex link is....
    http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
    SAPScripts
    http://esnips.com/doc/1ff9f8e8-0a4c-42a7-8819-6e3ff9e7ab44/sapscripts.pdf
    http://esnips.com/doc/1e487f0c-8009-4ae1-9f9c-c07bd953dbfa/script-command.pdf
    http://esnips.com/doc/64d4eccb-e09b-48e1-9be9-e2818d73f074/faqss.pdf
    http://esnips.com/doc/cb7e39b4-3161-437f-bfc6-21e6a50e1b39/sscript.pdf
    http://esnips.com/doc/fced4d36-ba52-4df9-ab35-b3d194830bbf/symbols-in-scripts.pdf
    http://esnips.com/doc/b57e8989-ccf0-40d0-8992-8183be831030/sapscript-how-to-calculate-totals-and-subtotals.htm
    SAP SCRIPT FIELDS
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/8033ea454211d189710000e8322d00/content.htm
    scripts easy material
    http://www.allsaplinks.com/sap_script_made_easy.html
    Debugging Document.
    http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
    http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
    http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
    http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
    http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
    Reward points if useful
    Regards
    Anji

  • Cisco Agent Detail Report

    When running the Cisoc Agent Detail Report I am seeing the following SQL commented out:
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
                INSERT #selected_agents(agentID, profileid)
                SELECT DISTINCT r.resourceID, r.profileid
                FROM db_cra.dbo.ResourceGroup rg, db_cra.dbo.Resource r, #selected_names sn
                WHERE       rg.resourceGroupID = r.resourceGroupID AND
                      rg.resourceGroupName = sn.name and
                      rg.profileid = r.profileid and
                       (r.active = 1 or
                      r.dateinactive >= @starttime)
    which is making it difficult to report by Resource Group. My question is has anyone run into the root cause that this has been commented out? My concern is that it was commented out becuase it caused some undesirable outcome. Thank you in advance.

    ICD_Agent_Call_Summary [ us_en ] version which refers to
    Exec db_cra.dbo.sp_agent_call_summary '$StartDate', '$EndDate', $SortBy, N'$ResourceGroup', N'$AgentName', N'$SkillName', N'$TeamName'
    which then calls getListOfAgents which takes in the resourcegroup passed and does parse2 [ so far so good ].
    * Parse2 in turn calls ParSeString which inserts the each token ( rather resource name ) in a temporary table selected_names
    --defective code
    Then irrespective of the resourcegroup passed, it does select on resource table to get a list of agents and inserts into the temp table #selected_agents.
    So both temporary table selected_names and selected_agents are now populated.
    Back @ sp_agent_call_summary immediately following exec of getListOfAgents, it does not touch selected_names again, selected_agents is touched only for joins with other tables in my version.  I would think that even for most sloppiest code, selected_names would be used to delete agents from "selected_agents" who do not belong to any resourcegroup in the selected_names table before using it for joins.
    In some of the other reports I see how parse2 and selected_names and selected_agents is used to get the right list of agents, however not on this one.
    Thanks for your help.
    sd

Maybe you are looking for