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

Similar Messages

  • 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

    Hi,
    I am trying to install SMD agents(711) on EP 7.0 system ,Got below error when trying to lauch the intsaller (sapinst)
    guiengine: No GUI server connected; waiting for a connection on host xxxxxx, port 21200 to continue with the installation
    Jan 11, 2011 5:18:58 PM [Info]: *************************
    Jan 11, 2011 5:18:58 PM [Info]: Starting Server
    Jan 11, 2011 5:18:58 PM [Info]: Reading server configuration.
    Jan 11, 2011 5:18:58 PM [Info]: Reading service configuration SAPinstService.
    Jan 11, 2011 5:18:58 PM [Info]: Configuring LogManager ...
    Jan 11, 2011 5:18:58 PM [Info]: *************************************************
    Jan 11, 2011 5:18:58 PM [Info]: Starting SL Controller ...
    Jan 11, 2011 5:18:58 PM [Info]: StorageService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: Initializing SecurityManager ...
    Jan 11, 2011 5:18:58 PM [Info]: Key Store management switched off.
    Jan 11, 2011 5:18:58 PM [Info]: Configuring HTTPManager ...
    Jan 11, 2011 5:18:58 PM [Info]: WebstartService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: RoleService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: AlertService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: Starting NotesService ...
    Jan 11, 2011 5:18:58 PM [Info]: ProcessService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: Starting MIDService ...
    Jan 11, 2011 5:18:58 PM [Info]: Starting FileService ...
    Jan 11, 2011 5:18:58 PM [Info]: LogService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: MailService switched off.
    Jan 11, 2011 5:18:58 PM [Info]: Starting services ...
    Jan 11, 2011 5:18:58 PM [Info]: Starting service "SAPinstService" ...
    Jan 11, 2011 5:18:59 PM [Info]: Service "SAPinstService" started
    Jan 11, 2011 5:18:59 PM [Info]: Services started.
    Jan 11, 2011 5:18:59 PM [Info]: Starting HTTP server listening on port 4239 ...
    Jan 11, 2011 5:18:59 PM [Info]: HTTP server started.
    Jan 11, 2011 5:18:59 PM [Info]: SL Controller started.
    Jan 11, 2011 5:18:59 PM [Info]: Starting GUI ...
    Jan 11, 2011 5:18:59 PM [Error]: java.lang.reflect.InvocationTargetException: null
    Jan 11, 2011 5:18:59 PM [Error]: java.lang.reflect.InvocationTargetException: null
    Jan 11, 2011 5:18:59 PM [Error]: GUI start failed.
    Please help me to solve the issue.
    Thanks,
    Srini K

    Hi,
    I have to cope with the same issue on exactly one of our 60 systems. I have no difficulties to start the SAPInst on any of the other systems, but I can't find any differences in their configurations.
    I already tried to apply a newer version of SAPInst (as suggested), but this did not help either (package SAPINST7102_2-20003627.SAR, Rel. 7.10 PL 80 for SunOS).
    Do you have any other suggestions how to get the SAPInst up and running on this final system?
    Thanks in advance for your help!
    Ulf

  • SMD Agent for ABAP Only Systems

    Everything I have read states that the SMD Agent is only for JAVA Stack.  Then I read a post here stating to install the SMD on the ABAP systems.  Can anyone clear this up?  I have a mix of Java only, Abap only and dual stack systems.  Can anyone help clear this issue up for me?

    Hello Donna,
    SMD Agent can be installed on Java Stack, Java-ABAP Stack and ABAP Stack.  It is not there only for Java as it can be used with ABAP and Dual stack also.  Hope this answers the question that you have brought up.
    Thanks,
    Mark

  • SMD Agent SR3 on NW2004s SR2

    Hi all,
    We are running NW2004s SR2 on our Solution Manager system.  We upgraded component ST-SER to 700_2008_1.  The older SMD agent appears to not work correctly with this level according to SAP.
    My question is, is it possible to install the standalone engine for SMD Agent SR3 without upgrading our entire system to SR3?  (kernel, installation, Java)
    We tried doing the SMD SR3 standalone install but are seeing some strange issues. 
    If anyone has an answer for me on whether I have to upgrade the entire system or not that would be much appreciated.
    Thank you.

    Solution Manager is a combined ABAP + Java installation, components of both must be in sync. It's not advised to install separate support packages or updates for certain components only, there are dependencies between them.
    Why don't you upgrade t the latest service pack - for both ABAP + Java? This will avoid lots of compatibility problems...
    Markus

  • 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

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

  • 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 starts, but stderr0 has errors

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

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

  • The SMD Agent 'Hades' hasn't been found!

    Hello,
    I started to install and configure Wily Introscope on one of my satellite
    system.
    I have one problem on some systems with the name of the server. The name of the satellite system is "hades" with lower letter. I installed the SMDagent on this hades system, this was installed successful (please see the [Agent Administration picture|http://img28.imageshack.us/img28/4707/agentadministration.jpg]). My problem is when I start to configure the agent for hades system on Managed Systems running Managed Systems, here I get "The SMD Agent 'Hades' hasn't
    been found!".(please see the [picture|http://img831.imageshack.us/img831/1260/setupwizard.jpg]) I think the problem is because the difference of capital
    letter for server name "hades". The server name is "hades" (with lower"h"), and this is the name in Agent Administration (please see the difference between ["Hades and hades|http://img15.imageshack.us/img15/4707/agentadministration.jpg]"), but in Setup Wizard the name of the server is "Hades"(upper "H"). Can you help me with this issue, because I am not able to
    continue because Agent is not available.
    I want to inform you that I ran SMSY_SETUP in to transfer all the SLD information to SMSY and this was successful transferred.
    Can you please tell me from where can come this server name with upper "H(ades)" . Only some systems have this problem, I configured another systems and those worked fine (the name of server was correctly (with lower characters).
    Best regards,
    Florin Radulea

    There are two possibities.
    1) You specified the SLD option when you installed the agent (I think this requires NW 7 SMD agent > ~14).
    - On SM system go to RCA work center, select Agent Administration, then Agent Candidates.  As long as you registered the agent in the same SLD as SM uses, it should be visible in the SLD view.  You need to associate the agent with this SM and supply connection information - there is a button for this, but you need to fill in a userid and password...
    The agent retrieves connection information (eventually) from SLD.
    2) You didn't register the agent in SLD or the agent needs special information to connect to managing SM.
    On OS level User smdadm (or DAAadm) there is a scripts directory
    /usr/sap/SMD/J##/script - SMD 7.0
    /usr/sap/DAA/SMDA##/script -- Diagnostic agent 7.1 or 7.2
    Run smdsetup.sh (.bat for windows) - no options gives all the possible sub commands.
    You need to specify info for "managingconf" sub command.
    If you provided wrong SLD connection information you can correct with this script too. (sldconf subcommand)
    You can also specify saprouter info...
    With supplied (correct) managing connection information, the agent should show up on the Agent Administration page.
    Note hostname is managing hostname, servername should be managed hostname.
    smdsetup managingconf      hostname:"sapms://<fqn>" port:"<MS httpPort>"
                                  [optional user:"<...>" pwd:"<...>" servername:"<...>"]
    smdsetup managingconf      hostname:"<fqn>" port:"<p4 port>"
                                  [optional user:"<value>" pwd:"<value>" servername:"<value>"]
    The first form uses load balancing the second doesn't.  The port in the second should be 5##04.
    Ckeck logs in work directory for error information (in case of typos, etc).  I think there may be a log in SMDAgent directory too.
    Ken

  • The SMD Agent 'server' hasn't been found

    I've seen this question posted, but no answer provided. I'm trying to install Wily Introscope on a Java-only (Netweaver 7) system. The SMD software is installed and the agent is running. I can see in the log files that the Wily agent  has connected to the management console.
    I'm running EHP1 on the Solution Manager server.
    When I go to Introscope Agent - Detailed Selection   and select this server this message is displayed "Failed to connect to server: "server" - Please make sure SMD Agent is up and running"
    When I attempt to run the Diagnostic Setup Wizard. I get the following message "the SMD Agent "server" hasn't been found" 
    1.) I've stopped and started the SMD agent on the client serveral times - Does not fix the problem
    2.) I've restarted Solution Manager - does not fix problem
    Any idea how to trouble shoot this issue?

    Thanks for pointing me in the right direction - here are the steps to resolve this issue.
    In my case the problem was caused by dual entries  in smsy for the server. I had the hostname and a DNS u2013 cname u2013 for the server in smsy. This was confusing Solution Manager.
    1. Use SOLMAN_WORKCENTER
    2. GoTo      ROOT CAUSE ANALYSIS  COMMON TASKS  ADMINISTRATION  AGENT ADMINISTRATION
        a. Right-click on the server with the problem and select  u201CRESET SERVER NAMEu201D
            i. The SMD agent will be disassociated with the server.  Restart the SMD agent on the server.
    3. Steps to reassign the server name
        a. Use SOLMAN_WORKCENTER
        b. GoTo     ROOT CAUSE ANALYSIS  COMMON TASKS SETUP and CHECK  DIAGNOSTIC SETUP  DIAGNOSTIC SYSTEMS  UPGRADER
            i. Select the UPGRADE NOW button
        c. Once the UPGRADER tasks completes
        d. GoTo     ROOT CAUSE ANALYSIS  COMMON TASKS SETUP and CHECK  DIAGNOSTIC SETUP MANAGED SYSTEMS  SETUP WIZARD
            i. Select the server
            ii. Reassign the SMD agent to this server
               1. The SMD agent will restart with the correct server name

  • Connection between SMD Agent and SMD server via SAProuter

    In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it?
    Hope someone can give us your precious advices on this issue.
    Karl

    Perfect; and thanks for your response. I found this help page for developers to implement P4 support over SAP router: http://help.sap.com/saphelp_nw73/helpdata/en/48/2992d7ad8758d7e10000000a421937/content.htm
    But in the SM Diagnostics Setup options I can set up only a direct HTTP adresses and have no options to set up connections over a sap router to P4 ports directly. I can at the moment only solve my problems with NAT or firewall rules.
    And also the diagnostic agent setup has no options to config a proxy or sap router. I found yesterday a blog on sdn side with screenshots of the setup with all available connection opetions to SLD... sry I can not post this link today.
    This is an official statment of SAP from the current version of SMD guide; it is also possible but why not from the beginning???:
    In some network conficurations, the Diagnostics agent has to connect to the Managing system though a SAP router.
    This feature will be fully supported in Solution Manager 7 Ehp2 (7.02).
    In order to enable this feature in Ehp1, please contact the Diagnostics Agent support team to get information on how to
    setup the agent and on which patch level you can perform the installation.
    This thread were a long time not answared; proxy and routing connections are mostly stepmotherly handled by SAP; this is also a problem by set up of automatic RFC generations in SMSY; why there are in the setup assitents no options to set up the router string.
    I have absolutly no comprehension for this in year 2011. All this technics are good known and long time tested.
    In this case the f**k has provoked an answare to this thread and this is what I expected; but sorry for my style You are right I could also writh why the heck
    FAQ:
    SMD root side on SDN: http://service.sap.com/diagnostics
    SM FAQ: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4e49dbea-0c01-0010-91bd-f0b61388c9ae
    SM Setup Home: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
    SM Diagnostic Troubleshooting Guide: https://websmp201.sap-ag.de/~sapdownload/002007974700000409092009E/DiagAgent_TroubleShooting.pdf
    SMD Candidate Setup: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

  • Deinstall SMD Agent

    Hello
    I upgrade SolMAn 7.01 to 7.10.
    The SMD Agent is still version 7.01. I would to upgrade it to 7.30.
    My first step is to deinstall the old agent using the DVD "DIAGNOSTICS AGENT 7.3", Software Life-Cycle Options, Uninstall
    But I get the error:
    An error occurred while processing option Solution Manager Diagnostics Agent > Software Life-Cycle Options >
    Uninstall > Uninstall( Last error reported by the step: Assertion failed: in component: NW_getDBInfo step:fillContext at this
    point the dbtype has to be != ind).
    Which is the right way to upgrade the Diagnostics Agent?
    How could I avoid the error?
    Thank you and regards,
    Tommaso

    Hi,
    I also had a similar issue sometime back. Please use the SMD Agent 7.01 Installation DVD to uninstall the existing 7.01 SMD Agent.
    Regards,
    Srikishan

  • Diagnostics - How to patch SMD Agent

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

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

Maybe you are looking for

  • Simple Button Hit Zone not working

    I am somewhat new to Flash CS4 andt am having a problem making simple buttons in Flash CS4 on a Macintosh: I have made a few buttons with a graphic and can go into them and successfully create the Up, Over and Down stages of the graphic. Then when I

  • Make a field obligatory by clicking on a check box

    SELECT-OPTIONS:             so FOR ztable-so OBLIGATORY. SELECTION-SCREEN END OF BLOCK b1. SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-b02. PARAMETERS: check1 TYPE char1 AS CHECKBOX. SELECTION-SCREEN END OF BLOCK b2. here my requirement

  • Material cost Valuation Exit: COPCP005(EXIT_SAPLCK21_002)

    Hi Experts, I am using this Enhancement COPCP005(EXIT_SAPLCK21_002) for material costing using valuation strategy U . When i try to cost a material which is a header BOM in CK11n the costing is done by info records for the header material. Configurat

  • Is it safe to delete Old QRFc logs ?

    Hi team , In SMQ 1 of ECC system we are able to see more entries for few Data sources like 0BP_STATUS_ATTR 0BP_TAXNUMB_ATTR 0FI_AP_3 0BP_ROLES_ATTR For these data source the Entries are more( around 10000) and they not loaded to BW end and these entr

  • ITunes on more than one computer - how??

    iTunes tells me I'm registered on more than one computer, but I'm not aware of it! 1) How do I find out which computers I'm on? I can't find where to go. 2) How do I delete them if I don't want them?