Introscope Agent 8.2.2.0 error

Hello All,
We are running on Solution Manager SP23. When I am doing automated setup of Introscope Agent from solution manager I am getting the error. Please find more details below
Intorscope Agent  8.2.2.0 successfully deployed on managing system  Solution Manger
SMD Agent 7.11 installed successfully and running fine on managed system
During Automated setup of Introscope Agent getting the below error
java.lang.NoSuchMethodError: com.sap.smd.agent.util.RunExec.setCharSet(Ljava/lang/String;)V
        at com.sap.smd.vm.J9Detector.isJ9(J9Detector.java:179)
        at com.sap.smd.wily.WilyHandlerService.performCommonSteps(WilyHandlerService.java:749)
        at com.sap.smd.wily.WilyHandlerService._configureISAgent(WilyHandlerService.java:659)
        at com.sap.smd.wily.WilyHandlerService.configureISAgent(WilyHandlerService.java:550)
        at com.sap.smd.wily.WilyHandlerServicep4_Skel.dispatch(WilyHandlerServicep4_Skel.java:144)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:664)
Thanks in advance
Akram

Hi,
Is the wily agent already deployed on the satellite system ?
then your SMD agent is not registered properly/ smsy details for the system are not maintained properly.
sometimes SMD Agent is shown green in the agent viewer, even the pls check if the logs are visible for that agent in the logviewer.
More checks better to try and start the uninstallation of the smd agent via sapinst,, in the second step it will either show the managing host name or not..
pls re-check and deactivate the wily agent and re-setup from the wily tab.
pls check if after the setup the OS contains the said Introscope agent.profile in the specified path.
Regards,
Kaustubh.
Edited by: Kaustubh Krishna on Aug 23, 2010 2:29 PM

Similar Messages

  • Introscope Agent Setup Error

    Hi,
    I am trying to setup Introscope Agent. I have installed it with Software Deployment Manager with no issues and setting up the agent using Diagnostic Agent Setup -> Managed System -> Introscope Agent.
    I am getting this error. Please suggest on this.
      ISAgent Setup on node:
    Operation Faile
       Introscope Agent Configuration
    Remote Operation Failed
       Introscope Agent Extraction
    Remote Operation Succeeded
       Detailed Information
    Operation skipped - Introscope Agent is already deployed at : filesystem
    \SMDAgent\applications.config\com.sap.smd.agent.application.wily\BytecodeAgent\ISAGENT.8.2.2.0-2010-04-22
       Updating Introscope Agent Profiles
    Remote Operation Succeeded
       ISAgent Profile Generation: IntroscopeAgent.profile ,
    Remote Operation Succeeded
       Detailed Information
    Operation Failed - <SID> - 254006950 - java.lang.NullPointerException
    Regards,
    Sandeep

    Hello Sandeep-
    Please do as follows
    Install IS Agent (Wiley Introscope agent) in Solution Manger systems
    Make sure wily is not running by looking for unix/windows  processes with strings like u201Cintrou201D, u201Cemu201D, u201Cwilu201D.  Uninstall wilyintroscope 7.1 by renaming the wily directory.
    and deploy it with SDM it should work
    Start SDM - 9> RemoteGui.sh
    (IS Agent file is /sapcds/SMD2/ISAGENTSMD72_02-10005468.SCA)
    then hit next and deploy after that you should be good to go.
    George
    Edited by: george rayi on Jul 20, 2010 10:14 PM

  • Introscope agent Error

    Hi,
    I have setup the rootcause analysis. Everything working fine..
    .But when Go to Introscope agent
    Diagnostics Setup -> Managed Systems -> INtroscope agent
    receive an error message below
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.progmodel.context.ContextException: Node(WilyAdmin.EMS): must not bind an empty collection to a Node of cardinality 1..1 or 1..n
        at com.sap.tc.webdynpro.progmodel.context.Node.checkCollection(Node.java:515)
        at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:415)
        at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:345)
        at com.sap.tc.webdynpro.progmodel.context.Node.createMappedElementList(Node.java:498)
        at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:393)
        ... 172 more
    reagars
    Thirumal

    Hi I got the same error,
    could you tell me how you solved it.
    Thx very much in advance.
    Genrich

  • Managed System Configuration - Introscope Agent Configuration Failed

    I get the following error message when carrying out step Byte Code Adapter Installation.
    Introscope Agent Configuration - Remote Operation Failed.
    The Wily agelet is running in 711 mode.
    VM Parameters update for node 268734950 Remote Operation Failed.
    Failed to update VM parameters:- com.sap.smdagent.vmmanager.VMManagerException: Failed to use JMX service
    Any help will be appreciated.

    Hi Tariq,
    Please check the following KBA:
    1918621 - Wily Bycode Agent install error - Failed to use JMX service
    Thanks
    Vikram

  • Introscope agent registration

    Dear All,
    after SMD agent installation (SolMan 7, EHP1 SP3) the SMD service start without problems. Unfortunately the agent cannot be registered properly, in SMD Agent Candidates I can see it but it stays in status 'Waiting for agent registration'and sometimes there is a 'handshake denied' error.
    In Diagnostics Setup -> Managed Systems -> Introscope Agent I can see the agent but withthe status: "Failed to connect to server: <name> - Please make sure SMD Agent is up and running".
    Any idea what can be the reason? LM* has the latest version and SP.
    Best regards,
    Jakub

    Did you ever get this resolved?  I've looked for Notes but only found your message.

  • Introscope agent setup

    I have setup the SMD agent on the satellite system and installed Wily EM. Now I want to setup the introscope agent on the satellite system. I go to Diagnostics setup-> Managed Systems-> Introscope Agent-> I select the Systems -  I dont see any J2ee node and when I click on setup introscope agent I get the error "The landscape definition of the selected system is empty. operation has been aborted"
    please suggest

    Hi ,
    I think, you have not provided the correct login details in Step 5.
    After executing step 4, in step 5 it will ask for SLD login details from there it will retrieve the list of all the systems.
    OR
    One of the reasons may be, provided login details are correct & all the system (managed system)  are already registered on the SMD of SolMan. So that is why you are not able to find any entries there.
    In that case, click on the SMD View tab in the newly opened window. You will find all the registered system there.
    I hope this will help you.
    Thanks & Best Regards,
    Pradeep Bishnoi
    Edited by: Pradeep Bishnoi on Dec 3, 2008 5:30 AM

  • Wily Introscope agent not deploying on PI

    Hi all!
    We have a solution manager 7.0 system, recently upgraded to stack 26. We have several PI landscapes, all connected to solman. Recently, i was able to update the Introscope agent on one PI 7.1 SP3 enh. pack 1 system without any problems, using introscope agent deployment in solman_workcenter -> Root Cause analysis -> Diagnostics Setup -> managed systems -> Introscope agent.
    With a 711 sp4 enh 1 system, i'm struggeling to get the agent deployed/upgraded on the same manner. The errors i'm getting are:
       ISAgent Setup on node: servername - 2352050 - server0
    Operation Failed
       Introscope Agent Configuration
    Remote Operation Failed
       Introscope Agent Extraction
    Remote Operation Succeeded
       Updating Introscope Agent Profiles
    Remote Operation Failed
       ISAgent Profile Generation: IntroscopeAgent.profile
    Remote Operation Succeeded
       Detailed Information
    Failed to get vm parameters from database - com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 23520
       Introscope Agent Connector Generation
    Remote Operation Failed
       Detailed Information
    Introscope Agent Connector generation is done using JDK at: null
       Detailed Information
    Failed to create Introscope Agent Connector at: J:\usr\sap\DAA\SMDA97\SMDAgent\applications.config\com.sap.smd.agent.application.wily\BytecodeAgent\ISAGENT.8.2.3.5-2011-01-14\wily\connectors - java.lang.NullPointerException 
    I'm using the same (SAP default) instrumentation profile as on the other PI servers. Also using the same autoprobe directives:
    sap_typical.jar
    sap_ep.jar
    sap_ep_iview.jar
    sap_xi_typical.jar
    I've read several forum posts regarding this issue, none aswered and none giving a clue in what direction i am to look for an answer. The only difference between the systems is patch levels and that the server experiencing the problems has an additional java node. Is it a problem with the autoprobing directives, should something in the instrumentation profile be changed? (if so, is there any available documentation regarding this?)
    If someone is able to point me in the right direction i'd appreciate it.
    Regards!

    Hi Diego,
    The saphostagent version on all the PI sattelite systems is the same, 711, patch 137, since all systems are 711 systems.
    If I check run SMDsetup on solman it shows me diagn. agent version 7.01.2.0.20081119084015. Based on the last long string, this looks kind of old..
    If i check agent administration in SOLMAN i see: 7.01.9.0.20110214073110 for the PI sattelite systems, i'm guessing this is the DAA agent version?
    The wily agent we're trying to deploy is ISAGENT.8.2.3.5-2011-01-14.. So.. Looks like something is to be upgraded on the solution manager side? All these agents and different ways of getting version numers make me dizzy.

  • Introscope agent -problem in ISAgent settings retrieval

    Hi ,
    I have installed a SMD agent for a pure and simple Java stack system.
    The SMD agent installation and setup wizard ran fine with no problems.
    How ever while trying to setup the introscope agent i have errors.
    Diagnostics setup -Managed system -Introscope agent
    The error is as following
    "Operation failed - X01 - 123456789 - com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied: Please make sure the <user> and <password> parameters are correct.; nested exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]"
    The SMD agent is up and running and im not clear which user id the above message is telling about.
    The user ID and password of  administrator which we give during running the setup wizard is correct.
    Also i have installed the SMD agent  with connection type "Lookup HTTP connection via message server"
    So i understand that the above user id could be the user which the agent is using to connect to the JVM...but im not sure which is that user id or if im right or wrong .
    Kindly advise if anyone has an idea how to resolve thsi problem.
    Regards,
    Sunanda

    Hi Sunanda,
    I had a similar problem with the ISAgent.
    I did a manual installation as described in the Installation guide Wily Introscope, chapter 4.
    After that, it worked.
    Best Regards,
    Jan
    PS: Check if note 1149214 applies before restarting the system /if restarting the system fails.

  • I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

    I can not make a "Byte Code Adapter Installation"
    When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
    Please help to resolve a number of questions that might help me complete the setup :
    1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
    I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
    2 . Why Server Node is empty detail settings ?
    JDK Location: 
    Enterprise Manager Host: 
    Enterprise Manager Port: 
    Introscope Agent Name: 
    Introscope Agent Profile: 
    Autoprobe Directives: 
    Wily Version: 
    Introscope Agent Version: 
    Introscope Agent Log Location:
    3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
    And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
    Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
    there is such an item:
    2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
    However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

    The problem was resolved a small manipulation - on stage Basic Configuration,
    point 3 "Configure CA Introscope"
    I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
    Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
    Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

  • Introscope Agent Settings does not show J2EE Nodes

    Hi all,
    we are using Solultion Manager Diagnostics for 4 systems and everything is all right. We no installed a PI 7.10 system (for migration from PI 7.00) on the same server as the PI 7.00 system is. Agents are running and configuration is almost done, just the last step is missing or not working.
    Now I want to configure SMD as well for the PI 7.10 system but I can see the J2EE Nodes on the SMD: Diagnostics Setup -> Managed Systems -> Introscope Agent
    I am not sure how we did it the last times, because everything run smooth. One thing I remember, we could not see the second Java Server node of the PI 7.00 system in here as well.
    Any Ideas how to do this?
    BR Markus

    Hi Jan,
    Could you please tell me how you reloaded the solution in SMD,i mean could you tell me the steps to reload the  solution in SMD.
    Regards,
    Krithi

  • Wily Introscope agent settings

    Hi,
    After the recent EHP1 upgrade on Solution manager,when we go to introscope agent configuration(Diagnostics Setup->Managed Systems->Introscope Agent)and select the system,it can't able to retrieve the current settings(i.e.,J2ee node).
    {through we have select right Enterprise Manager}
    We have also completed the post installation activities and successfully completed both the Initial and Basic configuration in solman_setup.
    Any inputs??????
    Thanks and Regards,
    Edited by: Venkata Nooney on Jan 28, 2010 5:10 PM

    Hi,
    You will need Enterprise Manager 8.x for Solution manager EHP1 SP3 and up.
    check this Note: 1273028- Introscope 8 release Notes for more details.
    Check if the wily agents on the managed systems are connected to Enterprise manager using the webview
    http://hostname.publix.com:8081/webview
    Thanks,
    Harini

  • Introscope Agent Settings

    Hi folks,
    Quick question this one probably.
    Can anyone tell me where this screenshot was taken from in Solution Manager please?  I've looked and looked and just cannot find it.
    Hopefully someone may recognise it??
    Thanks

    Hi Paul,
    Use this URL
    http://<fqdn>:<port>/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=ADMIN_INTROSCOPE_AGENT
    goto -SOLMAN_SETUP ----- Managed System Configuration, select your managed system and in step 5 select action 'Configure Wily Introscope Agent'
    Divyanshu

  • Installation of Introscope Agent

    Hi!
    I would like to install Introscope Agent.
    Neither the manual installation nor the installation via Setup Introscope Agent was succesfull.
    case a) automatic installation via SMD Wizard
    The erros of installation with SMD Wizard (Setup Introscope Agent):
    The landscape definition of selected system is empty.
    Operation has been aborted
    case b) manual installation (uncar the file ISAGENT71...SAR)
    With the manual installation of Setup Introscope Agent ISAGENT71*.SAR I have the following problem:
    No folder /usr/sap/ccms/wily/logs exist
    If I add Java settings in Config Tool, restart the system and open the file d:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.properties
    I can not find any entries added before.
    Thank you for any helpful information
    regards
    Thom

    Again case a)
    Please verify your definition, and also you need to have the previous Managed Setup Wizard run successfully.
    case b) I would not recommend it.
    Best Regards,
    Frederic

  • Wily Introscope Agent does not start

    Hi,
    i am installing Solution Manager Diagnostics on a Solution Manger 7.0 System. At the moment i am on the point to install the Wily Introscop Agent and i have following problem:
    At first i tried the automatic setup and deployed the agent with JSPM and it seemed to work. I see "ISAGENT" on the System Information -> All Compontents over http://0/smd/admin and there is no log directory in the wily directory?
    Does anybody has an idea whats wrong?
    Best Regards,
    Stefan
    Edited by: Stefan on Feb 17, 2009 8:57 AM
    Edited by: Stefan on Feb 17, 2009 9:31 AM

    Hello Stephan,
    1. Wily IS Agent (2 agents) is installed ONLY in SOLMAN system.
    2. Then, with SOLMAN_SETUP Guided procedure, in third phase (Managed System Configuration),
        you deploy the Wily IS Agent to your managed system.
    To summarize :
    1. Install the ISAGENTxxx.SCA in SOLMAN only !
    2. Start the SOLMAN_SETUP guided procedure
    3. Phase I - Initial Configuration
        Phase II - Basis Configuration
        Phase III - Managed System Configuration.
    In Phase III, there are 6 steps :
    1.     Connect Managed system
    2.     Check Prerequisites
    3.     Manual Configuration
    4.     Diagnostics Configuration
    5.     Wily Introscope Configuration
    6.     Create Logical Components
    The Wily IS Agent (2 agents : IS Agent wich monitored JAVA instance and Wily Host-level Agent which a sub-process of the SMD Agent) is configured and STARTED here.
    So, you cannot start / stop by any OS command the Wily IS Agent.
    You start it from SMD.
    Hope it help you.
    Best regards
    Pascal Cuennet

  • Problems in Introscope Agent Setting

    Hi all,
    we are configuring ROOT CAUSE ANALYSIS on Solution Manager 7 EHP1 to manage SAP BPC 5.1 system.
    On managed system, we installed Introscope_Agent_dot_net_8.1.0.0
    During the Introscope Agent Configuration in SolMan (transaction solman_setup --> Managed System Configuration --> Configure System --> Step 4 (Wily Introscope Configuration) --> in section "Introscope Agent Settings" field "System" there is no entry to select.
    Can you help us?
    Best regards,
    Alessandro

    Hi Alessandro,
    do you mean that everything is working and setup OK? If you look in Agent Administration, do you see the agent(s) online there?
    Did the managed system setup also complete successfully?
    Normally when performing the managed system setup, you assosciate the registered agent, to the system you are configuring for diagnostics. Therefore it's important that all agents are up and running and connected.
    On the managed system, check the logfile /usr/sap/ccms/wily/logs/IntroscopeAgent*****.log to see if it is running correctly. Also make sure the SMD agent on this host is OK: /usr/sap/SMD/J98/SMDAgent/log
    /usr/sap/SMD/J98/script/smdadmin.sh
    Check if the instance is up and running.
    Edited by: J. Hellemons on Oct 27, 2009 4:31 PM

Maybe you are looking for

  • Save my applications

    Hello, do you know how to save all my applications with Desktop Manager 6 if I want to change my phone or the OS one day ? thanks for yours anwsers. Solved! Go to Solution.

  • Function Modules for creating production version.

    Hi, Is there any function module available in SAP to create Production version? I'm aware of CM_FV_PROD_VERS_MAINTAIN function module but this one works on dialog mode. Please let me know if there are any other function module/class available to crea

  • Macbook Pro Harddrive Broken?

    Hi all, I appreciate you're all busy people - but if you had a second, some advice would be brilliant. (Also - apologies in advance for being a hardly a tech genius). I have a MacBook Pro (2010), not sure of which version of OS X, and during normal i

  • FAQ - Ancile RWD SPP compatibility with IE 9

    There may be problem starting RWD client when IE 9 is installed on the client machine. This can happen for version below SPP 4.31. For version SPP 4.31, there are some successful stories but this is not officially supported by Ancile as Ancile RWD is

  • How to use output of one query as an input for another

    Hi Gurus, can you give me any links on how to use an output of one query as an input for another (preferably if this can be done in a dynamic/on the fly way)? thanks