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

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

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

Similar Messages

  • 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

  • Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

    Hi guys,
    we are using PI 7.11.
    With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
    This works fine.
    Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
    I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
    Afterwards I treied to restart the message.
    Following error occurs.
    com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
    I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
    trying restart the failed message ends up in the error specified aboce.
    Anyone faced the same issue already?
    Kind regards
    Jochen

    HI Jochen,
    I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
    To do a CPA Cache Refresh from the Adapter Engine:
    To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
    http://<host>:<port>/CPACache/refresh?mode=delta|full
    The Monitoring url is like this:
    http://<host>:<port>/CPACache
    Check this How-to Guide on Cache, it will be useful:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
    Thanks
    Dhwani

  • Configuration of SAP R/3 application component in Source system of SAP BW

    Hi , Can someone guide me through the installation of SAP R/3 application components in SAP BW. It will highly appreciated if I can get some guidance on it.
    Subramanian

    Hi,
    Please check the link below.
    http://help.sap.com/bestpractices/BBLibrary/documentation/B03_BB_ConfigGuide_EN_DE.doc
    Rgds,
    Suman

  • Com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or passwo

    Hi All,
    I'm configuring the Solution Manager Diagnostics.
    I have all my agent SMD and IS installed.... but when I run the Setup Wizard, I received the following error:
    Step Wilyhost Agent Details
    Created destination BD1_DVEBMGS00_server0
    Created destination SapStartSrv_bnsr3dci_BD1_00
    Created destination BD1|bnsr3dci_BD1_00
    Created action SAP GC|BD1_DVEBMGS00_server0 - SAP GC|BD1_DVEBMGS00_server0
    Created action BD1|bnsr3dci_BD1_00 - SapStartSrv_bnsr3dci_BD1_00
    Created action BD1 - BD1 AbapSystem
    Created action BD1|bnsr3dci_BD1_00 - BD1|bnsr3dci_BD1_00 AbapInstance
    Created 4 action(s).
    0 Wilyhost Agent(s) from host bnsr3dci are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (bnssmpci.bns.local:6001) no Wilyhost Agent was detected from host bnsr3dci. 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.
    and checking the jvm_smdagent.out file on managed system
    Running SMD Agent ...
    [ms://bnssmpci:8101/P4] Agent ready.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.5.0_17" from SAP AG
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily
    host/IntroscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/Int
    roscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions director
    y.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The agent extensions directory /sap_mirrlog/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.ap
    plication.wilyhost/ext was successfully located
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA97" based on the value of the System Property "com.wily.introscope.a
    gent.agentName".
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA97
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Started Error Reporting service
    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
    10/27/09 02:58:20 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (1).
    Initialization done.
    10/27/09 02:58:30 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (2).
    10/27/09 02:58:40 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (3).
    10/27/09 02:58:50 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (4).
    10/27/09 02:59:00 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (5).
    10/27/09 02:59:11 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (6).
    10/27/09 02:59:21 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (7).
    10/27/09 02:59:31 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (8).
    10/27/09 02:59:41 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (9).
    10/27/09 02:59:51 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (10).
    10/27/09 02:59:51 PM EDT [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further fai
    lures will not be logged.
    [ms://bnssmpci:8101/P4] Agent ready.
    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
    Initialization done.
    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
    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
    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
    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
    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
    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
    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
    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
    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
    This is error common ?
    Any idea ?
    Weird for me is this line:
    "Failed to connect to the Introscope Enterprise Manager at localhost:6001"
    Because my INtroscope Enterprise Manager name is bnssmpci
    Thanks and Regars,
    Juan.

    SOLVED !!!
    Restart the J2EE Managed System and check the SAP Note - WilyHost agent fails to connect to ABAP stack (bad password

  • Failed to update VM parameters - com.sap.smdagent.vmmanager.VMManagerExcept

    Hi
    Anyone come across the error below when setting up the introscope agent:
    Failed to update VM parameters - com.sap.smdagent.vmmanager.VMManagerException: A test vm could not be started, the vm parameters seems to be incorrect:-Djco.jarm=1 -XX:MaxPermSize=512M -XX:PermSize=512M -Xms2048M -Xmx2048 -XX:NewSize=320M -XX:MaxNewSize=320M -XX:DisableExplicitGC -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:UseTLAB -XX:UseParNewGC: -XX:HandlePromotionFailure -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.krb5.conf=F:\usr\sap\EPX\SYS\global\kerberos\ID80419\krb5.conf -Dsun.security.krb5.debug=true -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-08-24/wily/connectors/AutoProbeConnector.jar;F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-08-24/wily/Agent.jar -Dcom.wily.introscope.agent.agentName=EPX_JC00_server0 -Dcom.wily.introscope.agentProfile=F:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-08-24/wily/IntroscopeAgent.profile
    From the notes the only parameter that seems to be know to cause conflicts is -Xloggc:<file>.
    Does anyone have a list of known parameters which cause the above problem. We are running on:
    Managed system : Java 701
    Agent : 720
    ISAGENT.8.2.2.0-2010-08-24
    Solman 701 sp25
    vm parameters on managed system
    -Djava.awt.headless=true
    -Djava.security.egd=file:/dev/urandom
    -Djava.security.krb5.conf=F:\usr\sap\EPX\SYS\global\kerberos\ID80419\krb5.conf
    -Djava.security.policy=./java.policy
    -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -Djavax.security.auth.useSubjectCredsOnly=false
    -Djco.jarm=1
    -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -Dsun.io.useCanonCaches=false
    -Dsun.security.krb5.debug=true
    -XX:+DisableExplicitGC
    -XX:+HandlePromotionFailure
    -XX:+JavaMonitorsInStackTrace
    -XX:+PrintGCDetails
    -XX:+PrintGCTimeStamps
    -XX:+UseParNewGC:
    -XX:+UseTLAB
    -XX:MaxNewSize=320M
    -XX:MaxPermSize=512M
    -XX:NewSize=320M
    -XX:PermSize=512M
    -XX:SoftRefLRUPolicyMSPerMB=1
    -XX:SurvivorRatio=2
    -XX:TargetSurvivorRatio=90
    -Xms2048M
    -Xmx2048
    -verbose:gc
    Thanks in advance
    Jim

    Hi Allam,,
    I also got the same issue, while configuring Wily agent.
    I did the changes as per your solution.(selected scope is where agent is deployed, not global)
    I also restarted DAA/SMD agent. But still error remains same for me. please suggest.

  • SR3 SMD Agent on SP15

    Hi
    Our Solution Manager is on SP14 and Managed System is on SP15. I want to install the SMD Agent. As per the note 1126895 it is possible and suported. LMSERVICE is SP14.
    I used note 1170855 to install it and it was successfull but the status is "in Progress" in http:////<hostname>:<port>/smd page. It says "DEPLOYING APPLICATION". It never finishes.
    I checked the log file jvm_SMDAgent.out and it says that
    Starting SMDAgent ...
    Running SMD Agent ...
    Establishing connection to server 'ms://<hostname>:8177/P4
    [ms://<hostname>:8177/P4] Waiting for connection ...
    [ms://<hostname>:8177/P4] Checking server availability...
    [ms://<hostname>:8177/P4] Authentication in progress ...
    [ms://<hostname>:8177/P4] Connection established .
    [ms://<hostname>:8177/P4] Registering agent on server ...
    Exception occured. Please check log files.[Exception ID:1219178405804 ]
    [ms://<hostname>:8177/P4] Waiting for connection ...
    [ms://<hostname>:8177/P4] Checking server availability...
    [ms://<hostname>:8177/P4] Authentication in progress ...
    [ms://<hostname>:8177/P4] Connection established .
    [ms://<hostname>:8177/P4] Registering agent on server ...
    It never finishes.
    It is failing at deployment application.
    The log file SMDSystem.0.log states following -
    Aug 19, 2008 4:30:04 PM [Thread[Thread-2,5,main]] Info
    [AgentContext.offlineDeployApplication] ENTERING - deploying file
    com.sap.smd.agent.application.runtime_7.0014.20080429115048.0000.war
    Aug 19, 2008 4:40:05 PM [Thread[SMDAgent connection thread,5,main]]
    Error [Exception ID: 1219178405804 ] java.rmi.RemoteException -
    error counter: 1
    [EXCEPTION]
    java.rmi.RemoteException: Agent Registration failed: Time out occurred
    when calling method 'offlineDeployApplication' on object
    [com.sap.smd.api.IAgentContext_Stub@1de64fc2] after 600000 ms.
    possible cause: com.sap.smd.server.util.concurrent.TimeoutException
    at com.sap.smd.SMDServerHandle.internalRegisterAgent
    Anybody has experienced it.
    Please let me know.
    Regards.
    SS

    Hello,
    Would you kindly share the solution?
    Think I run into a similar issue.
    Many Thanks,
    Jan

  • SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)

    I am getting the following message when I start the agent.  I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects.  Just eventually times out after 30 mins.
    FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    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=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 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=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    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=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    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=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 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=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    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=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.

    cat dev_SMDAgent
    trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
    node name   : smdagent
    pid         : 17393
    system name : SMD
    system nr.  : 98
    started at  : Wed Oct  7 08:56:32 2009
    arguments         :
              arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
              arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
              arg[02] : -DSAPINFO=SMD_98_server
              arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
    -> ms host    :
    -> ms port    : 36
    -> OS libs    : /usr/sap/SMD/exe
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SMD/J98/profile/smd.properties
    Instance properties
    -> ms host    :
    -> ms port    : 36
    -> os libs    : /usr/sap/SMD/exe
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    Worker nodes
    -> [00] smdagent             : /usr/sap/SMD/J98/profile/smd.properties
    [Thr 182894174624] Wed Oct  7 08:56:32 2009
    [Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
    [Thr 182894174624] SigISetDefaultAction : default handling for signal 17
    [Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182894174624] CPIC (version=701.2009.01.26)
    [Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
            Java Home: /opt/IBMJava2-amd64-142
    [Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
    JStartupIReadSection: read node properties [smdagent]
    -> node name          : SMDAgent
    -> node type          : server
    -> node id            : 1
    -> node execute       : yes
    -> java path          : /opt/IBMJava2-amd64-142
    -> java parameters    : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 256M
    -> init heap size     : 256M
    -> root path          : ../SMDAgent
    -> class path         : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> OS libs path       : /usr/sap/SMD/exe
    -> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
    -> parameters         : run jcontrol
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 58981
    -> shutdown timeout   : 20000
    [Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -DP4ClassLoad=P4Connection
    -> arg[  4]: -Xj9
    -> arg[  5]: -Xmn50m
    -> arg[  6]: -Xgcpolicy:gencon
    -> arg[  7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
    -> arg[  8]: -Dapplication.home=/usr/sap/SMD/exe
    -> arg[  9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    -> arg[ 11]: -Dmemory.manager=256M
    -> arg[ 12]: -Xmx256M
    -> arg[ 13]: -Xms256M
    -> arg[ 14]: -DLoadBalanceRestricted=no
    -> arg[ 15]: -Djstartup.mode=JCONTROL
    -> arg[ 16]: -Djstartup.ownProcessId=17393
    -> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
    -> arg[ 18]: -Djstartup.whoami=server
    -> arg[ 19]: -Djstartup.debuggable=yes
    -> arg[ 20]: -DSAPINFO=SMD_98_server
    -> arg[ 21]: -DSAPSTARTUP=1
    -> arg[ 22]: -DSAPSYSTEM=98
    -> arg[ 23]: -DSAPSYSTEMNAME=SMD
    -> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
    -> arg[ 25]: -DSAPDBHOST=
    -> arg[ 26]: -Dj2ee.dbhost=
    [Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
    -> arg[  0]: run
    -> arg[  1]: jcontrol
    [Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1086335328] Wed Oct  7 08:56:35 2009
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1086335328] Wed Oct  7 08:56:38 2009
    [Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
    [Thr 1101334880] Wed Oct  7 08:56:43 2009
    [Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
    [Thr 1101334880] Wed Oct  7 08:56:48 2009
    [Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]

  • SMD agent not connecting to the SMD server!!!!

    Hi
    We are tring to set up the Solution manager diagnostics. We are on SP13 NW04s.
    We finished installing the Wily 7.2, Diagnostics System Wizard,
    and then finished installing the SMD agent on the remote server without any error.
    Our Diagnostic system server(solution manager) in on i5/OS and the our SMD agents are spread across windows servers & i5/OS servers.
    The SMD agents from the i5/OS server got connected to the Diagnostic server(solution manager) within minutes.
    But the ones from windows(X64) do not get connected to the Diagnostic server(solution manager) . We waited and waited, tried rebooting the agent, but to no help. The status it shows is "in process"
    When we checked the logs in the SMD agent system on windows, we found out that it is complaining about some  application which failed to unzip as shown:
    Mar 18, 2008 8:04:47 PM [Thread[SMDAgent connection thread,5,main]] Info       [SMDConnector.reset] in progress ...
    Mar 18, 2008 8:04:47 PM [Thread[SMDAgent connection thread,5,main]] Info       Stopping Applications ...
    Mar 18, 2008 8:04:47 PM [Thread[SMDAgent connection thread,5,main]] Info       [SMDConnector.reset] Done.
    Mar 18, 2008 8:04:52 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Waiting for connection ...
    Mar 18, 2008 8:04:52 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Checking server availability...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Authentication in progress ...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Connection established .
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Registering agent on server ...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       Reading JStartup environment...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       'SAPLOCALHOST' found, The value 'srvlctemp01' will be used to determine the Agent name.
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       InetAddress Resolving for 'srvlctemp01' - FQN: srvlctemp01 SQN: srvlctemp01 IP: 10.10.16.89
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       InetAddress Resolving for localhost - FQN: srvlctemp01 SQN: srvlctemp01 IP: 10.10.16.89
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       Agent handle : srvlctemp01_SMD_J66/srvlctemp01 created.
    Mar 18, 2008 8:04:53 PM [Thread[Thread-620,5,main]] Info       Overriding runtime property from server configuration, name= 'runtime.states.initial', value='core.startup,core.patch.enabled'.
    Mar 18, 2008 8:04:56 PM [Thread[Thread-616,5,main]] Info       [AgentContext.offlineDeployApplicationConfiguration] ENTERING
    Mar 18, 2008 8:04:56 PM [Thread[Thread-616,5,main]] Error      Deploy application configuration failed.
    [EXCEPTION]
    com.sap.smd.agent.deploy.DeploymentException: Cannot expand zip entry.
         at com.sap.smd.agent.deploy.DeploymentManager.extractCompressedStream(DeploymentManager.java:258)
         at com.sap.smd.agent.deploy.DeploymentManager.installAppConfiguration(DeploymentManager.java:780)
         at com.sap.smd.agent.AgentContext.offlineDeployApplicationConfiguration(AgentContext.java:597)
         at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:189)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
         at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:710)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.util.zip.ZipException: invalid entry CRC (expected 0x0 but got 0x1b3304ba)
         at java.util.zip.ZipInputStream.read(ZipInputStream.java:164)
         at com.sap.smd.agent.deploy.DeploymentManager.extractZipEntry(DeploymentManager.java:321)
         at com.sap.smd.agent.deploy.DeploymentManager.extractCompressedStream(DeploymentManager.java:251)
    Has anyone experieced any kind of errors related to this?
    Thanks

    Hi Folks,
    Can u give me the steps and best practices to be follow to configure & Install the WILY Interoscope with solution manager.
    Please share your experience also with WILY Interoscope.
    Documents would be highly appreciated with reward points.
    Regards,
    Akshay

  • SMD agents goes offline in agent administration

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

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

  • 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

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

  • 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

  • Smd agent problem

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

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

  • 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

Maybe you are looking for

  • Itunes 10.5.3

    help with itunes 10.5.3 can't install it on windows 7 it aborts right about at the end of the process with some error

  • Spectre 13" 3004TU Ultrabook F4A28PA Display rubber seal leaking fluid at bottom of screen

    I have a Spectre Ultrabook 13" for which I paid a pretty penny - top of the line specs (i7, 8gb ram, 256 GB SSD etc). Naturally, having spent so much I have treated it with kid gloves - however, I have noticed small amounts of a clear, oily residue a

  • Full Package

    Hey am new to this and im a bit confused with all the different licensing  options, do i understand it to be rite if i perchase a full package do i get full use out of it for life but pay full price, and if you have a different licence it last for a

  • Removing extra spaces from email attachment of text file

    Hi All, I am having a question in opening email attachment file in text mode. Whenever I am trying to open a CSV file in text mode after each row it adds blank spaces. These blank spaces are to complete the 255 characters on each row I guess. My clie

  • Advice on Xserve Raid

    I need advice please. I want to buy the following second hand. is this a worthwhile buy or is it an old model of Xserve RAID? Can 400GB HDs be put in in place of the 250 GB? Xserve RAID Chassis 14x250GB Hard Drives 2 SFP Controllers w/ 512MB Cache ea