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

Similar Messages

  • 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 7.00 or Diagnostics Agent 7.11

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

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

  • Diagnostics Agent 7.11 vs SMD Agent 7.00

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

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

  • Start of SMD agent fails!

    Hi!
    After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
    The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
    Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error      Exception ID: 1160572286256
    Registering agent on server myhost.de:50004failed:
    com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
            java.lang.reflect.InvocationTargetException
    java.lang.reflect.InvocationTargetException
    However, the manual setup of the agent succeeds:
    ./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
    SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
    SMD Agent Setup is in process ...
    - STEP 1: checking JDK location
    JDK location is consistent: /usr/java14_64/bin
    - STEP 2: checking JDK Version
    JDK Version is correct: 1.4.2
    - STEP 3: checking Connection to SMD Server
    SMD Server check completed successfully
    - STEP 4: generating Runtime Properties
    runtime.properties has been created.
    - STEP 5: generating Launcher
    smdagent.bat has been created.
    smdagent.sh has been created.
    - STEP 6: generating SecStore
    secstore.properties: has been created.
    secstore.properties: user has been set.
    secstore.properties generation completed successfully.
    - STEP 7: checking P4 Connection and SMD Agent Registration
    SMD Agent Registration succeeded
    SMD Agent Setup completed successfully
    During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
    What can we do?
    Thanks for all hints solving our problem!
    Greetz,
    André Richter

    Hi Rahul,
    please try SMD Agent 7.00 SP10! We had no problems with this version!
    Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
    Regards
    André

  • Install SMD agent on EP6 fails

    Hi,
    I get an error when installing SDM agent on EP6 (HP-UX):
    STEP 7: checking P4 Connection and SMD Agent Registration
    External Command Executed:
    /opt/java1.4/bin/java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp ":/usr/sap/SMD/J97/SMDAgent/lib/sapxmltoolkit.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdagent.jar:/usr/sap/SMD/J97/SMDAgent/lib/tc_sec_secstorefs.jar:/usr/sap/SMD/J97/SMDAgent/lib/iaik_jce_export.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/logging.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdserver.jar:/usr/sap/SMD/J97/SMDAgent/lib/exception.jar:/usr/sap/SMD/J97/SMDAgent/lib/sapj2eeclient.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/smdagentlauncher.jar:" com.sap.smd.setup.Setup /p4connection
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    P4 Connection succeeded but SMD Agent Registration failed
    Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of smdserver.
    I couldn't find anything on SAP Market Place but a similar thread here advised to check if SDM servers is not in maintenance mode.
    Well, it's not.
    Can someone please help?
    Thx
    Bert

    Hi,
    Did you connect to smd server http://host:port/smd and desactivate maintenance mode in Agent Administration page?
    This should solve your issue.
    Regards,
    Frederic

  • 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 doesn't work

    Hello,
    I have been trying to install SMD Agent in my BI system but Solution Manager can't check it, this is the message in Solman_setup
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. 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.
    Step Wilyhost Agent Details
    Created destination QBB|svs978_QBB_01
    Created action QBB - QBB AbapSystem
    Created action QBB|svs978_QBB_01 - QBB|svs978_QBB_01 AbapInstance
    Created 2 action(s).
    0 Wilyhost Agent(s) from host svs978 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. 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.
    do you know something??? i restarted the agent but nothing happens
    Thanks!!!!

    Hello...
    For JAVA
    Software Components 
    Vendor  Name  Version  Provider  Location  Applied 
    sap.com  ADSSAP  7.01 SP4 (1000.7.01.4.0.20090417021200)  SAP AG  SAP AG  20091103161136 
    sap.com  BASETABLES  7.01 SP4 (1000.7.01.4.0.20090417015900)  SAP AG  SAP AG  20091103153957 
    sap.com  BI_MMR  7.01 SP4 (1000.7.01.4.0.20090417021807)  SAP AG  SAP AG  20091103161215 
    sap.com  BI_UDI  7.01 SP4 (1000.7.01.4.0.20090416221700)  SAP AG  SAP AG  20091103162333 
    sap.com  CAF  7.01 SP4 (1000.7.01.4.0.20090417194106)  SAP AG  MAIN_NW701P04_C  20091103163937 
    sap.com  CAF-UM  7.01 SP4 (1000.7.01.4.0.20090417194111)  SAP AG  MAIN_NW701P04_C  20091103161325 
    sap.com  CORE-TOOLS  7.01 SP4 (1000.7.01.4.0.20090417021948)  SAP AG  SAP AG  20091103154019 
    sap.com  ISAGENT  8.1 SP0 (8.1.0.0.20090605095817)  SAP AG  SAP AG  20091210142716 
    sap.com  JLOGVIEW  7.01 SP4 (1000.7.01.4.0.20090417020000)  SAP AG  SAP AG  20091103154104 
    sap.com  JSPM  7.01 SP4 (1000.7.01.4.2.20090918151100)  SAP AG  SAP AG  20091201201543 
    sap.com  KM-KW_JIKS  7.01 SP4 (1000.7.01.4.0.20090514115300)  SAP AG  SAP AG  20091103161349 
    sap.com  LM-SERVICE  7.01 SP5 (1000.7.01.5.2.20091211060559)  SAP AG  SAP AG  20091224192630 
    sap.com  LM-TOOLS  7.01 SP5 (1000.7.01.5.3.20091208123420)  SAP AG  MAIN_NW701P05_C  20091228135344 
    sap.com  SAP-JEE  7.01 SP4 (1000.7.01.4.1.20090612152648)  SAP AG  SAP AG  20091103154150 
    sap.com  SAP-JEECOR  7.01 SP4 (1000.7.01.4.0.20090417015900)  SAP AG  SAP AG  20091103154414 
    sap.com  SAP_JTECHF  7.01 SP4 (1000.7.01.4.2.20090612144700)  SAP AG  SAP AG  20091103154520 
    sap.com  SAP_JTECHS  7.01 SP4 (1000.7.01.4.2.20090612152905)  SAP AG  SAP AG  20091103162132 
    sap.com  SWLIFECYCL  7.01 SP4 (1000.7.01.4.0.20090511115334)  SAP AG  MAIN_NW701P04_C  20091103151458 
    sap.com  UMEADMIN  7.01 SP4 (1000.7.01.4.0.20090417195012)  SAP AG  MAIN_NW701P04_C  20091103165828 
    For ABAP
    SAP_BASIS     701     0004     SAPKB70104
    SAP_ABA     701     0004     SAPKA70104
    ST-PI     2008_1_700     0001     SAPKITLRD1
    PI_BASIS     701     0004     SAPK-70104INPIBASIS
    CRMUIF     500     0003     SAPK-50003INCRMUIF
    SAP_BW     701     0004     SAPKW70104
    SAP_AP     700     0016     SAPKNA7016
    BBPCRM     500     0015     SAPKU50015
    CPRXRPM     400     0015     SAPK-40015INCPRXRPM
    ST     400     0021     SAPKITL431
    BI_CONT     704     0004     SAPK-70404INBICONT
    ST-A/PI     01L_CRM570     0000          -
    ST-ICO     150_700     0022     SAPK-1507MINSTPL
    ST-SER     701_2008_2     0005     SAPKITLOQ5
    LM Components were updated for EHP1 SPS21, I installed SMD Agents in DEV and some QA servers and they work, but this one specially works as a fail over for a PRD cluster enviroment, and for that reason I'm using logical name, in SMSY it is configure with the same name, do you have any ideas?
    Thanks!!!

  • SMD agent passowrd issue

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

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

  • SMD agent on Sol Man 4 instance?

    Quick question.  Would/should one install the SMD agent on the Solution Manager 4 J2EE instance (as well as on satelite J2EE instances)?

    Hi,
    of course you may want to diagnose the monitoring system itself. Especially for the Java part of SolMan 4 this is useful.
    Kind regards,
       Bernie

  • Does solution manager 4.0  require SMD Agent?

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

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

  • Setting Agent timeout

    Hi,
    in one of my other posts, I mention solving most of my problems except for the fact that all my alarms have disappeared (eventManager problem?!)
    and that some of my slower systems frequently timeout their SunMC agent even though it is all working fine. I think the default Agent timeout is too short for me.
    It appears to be only a few seconds at most. I would like to be able to extend the timeout to about 15 or 20 seconds for the unresponsive systems. This seems
    to be a magic number that never produces a false alarm for me.
    So if such a value is possible, could I please be informed as how to set it? I figured it is yet another value in domain-config.x ?
    If so, is there also a list of all the possible values that can be set in SunMC or at least this file?
    Thanks!
    rachel

    bump - because "someone" must have done this in the past. Please assist! My system is running great except my
    boss says "why is host x, y & z always failing? They're not - they just take longer than the default timeout to respond.
    All I need is the magic timeout value and my world is good.
    rachel

  • Error in SMD Agent

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

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

  • 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

  • Preparing Solution Manager for SMD Agents Installation

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

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

Maybe you are looking for

  • AD contact user not showing up in Lync

    Hello, I'm trying to add Active Directory contact users in my Lync adress book but it seems not working. AD contact have correct phone number (E164) and i run "update-csaddressbook" and "update-csuserdatabase" on my Lync server. I have also deleted G

  • Suggestion for new Cover Browser

    I'm not sure where to post this suggestion to Apple, but I thought I'd start here. I'm LOVING this new "Cover Browser" view, with the way you can "flip" through CD covers like we used to do with LPs and CDs on our shelves. It's great to be able to de

  • DW CS4 "System" Fonts

    My wife's been using CS4 on a 19" CRT at 1024x768 resolution for quite a while. When her monitor went out this weekend, I managed to chase down a 19" LCD monitor, but this really has to be run at its native resolution of 1280x1024. Well, she really d

  • Application Skype wants me to use broken desktop version.

    Why my skype app wants me to use desktop version because it's newer?when i want to run applicatio skype it says "We replaced this application with newer, modernized Skype. Look ,what you can do with new skype" (Translated from Polish)Here's the origi

  • Plotting a time series

    I have this problems: A user should be able to choose some data from an access db and ask for a plotting. I am trying this: a) Servlet A queries the data base and presents all choices for user. User chooses one and submit it to Servlet B; b) Servlet