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

Similar Messages

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

  • Problem Remote Deploy Wily Introscope Agent

    Hi,
    I installed Wily Introscope EM and the Diagnostic Agent on Solution Manager (EhP1).
    Now, if I understand it, I can do a remote deploy of Introscope Agent, for example on Enterprise Portal.
    How can I do?
    Best Regards.
    Diego.

    Hi Diego,
    Do you also install an SMD agent on the portal system which one you want to managed via RCA? Also you need to run the Setup Wizard for Managed Systems for your portal.
    Please check SAP Note 1365123 - Installation of Diagnostics Agents. In this note you will find an attachment Agent_Installation_Strategy.ppt - describe the installation strategy of SMD agents and all agent rules which you need to follow.
    So one part is to get RCA running:
    1. Install a SMD agent per managed host.
    2. Define the technical system in SMSY Normal you have an SLD in your landscape and connect the Solution Manager to it or use the SLD from Solution Manager. After you define the technical system in SMSY or via SOLMAN_SETUP ->Managed System Configuration you go to Diagnostics Setup.
    3. You access this via Diagnostics work center or direct link http://solman_fqdn:<port>/smd
    4. Next go to Managed System -> Setup Wizard -> Select your to managed system <SID> - > check that system is Diagnostics Relevant (if not click on the managed products and set the relevant product for diagnostic u2013 also verify the Landscape setting light are green u2013 this means the technical system is well defined in SMSY)
    5. Click Setup <SID> Button -> on next screen you need to fill out all Java / Abap connection parameters (for the setup of Java systems you need a userid with j2ee admin rights)
    6. Please set the SMD agent in the right table u2013> Click on details arrow and then select the managed systemu2019s SMD agent and click on the set button. The SMD agent will now reboot wait until the agent is back -> Click on the Refresh button to see the status.
    7. Click Next and on the next screen you get a Summary of all setup steps
    8. Click on Setup. After the setup finished (all steps are green)
    9. Click on quit.
    Before your can deploy the IS agent from the Solution Manager you need to deploy the IS agent files via SDM to the Solution Manager. You can download the deployable IS agent from SAP Service Market Place:
    Support Packages and Patches -> Entry by Application Group -> SAP Technology Components -> SAP SOLUTION MANAGER -> SAP SOLUTION MANAGER 7.0 EHP 1 -> Entry by Components -> Agents for managed systems -> select your version for your IS EM and download the deployable agent via SolMan Diagnostics (File name like ISAGENTSMD801_01-10007435.SCA)
    Now you can start with the setup of the Introscope Agent (on the left menu bar under application selection).
    On the selection screen select first your IS Enterprise Manager then the IS Agent settings the relevant system.
    In the table select the J2EE node for which want you setup the agent (this need to be done for each Server node u2013 the IS agent runs inside of the J2EE node per server)
    Then click on Setup Introscope Agent u2026 Button u2013> select the Autoprobe Directives and click the Apply button. If every steps doen you need to reboot your managed JAVA system.
    Now you are ready to use the RCA tools and also see data in the IS Enterprise Manager.

  • 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

  • [SOLVED] Braid AUR "ERROR: There is no agent set up to handle file..."

    SOLUTION AT BOTTOM OF THREAD!
    I have installed numerous AUR packages in the past.  However, this is the first that I am unable to figure out.
    I assume I am supposed to extract the tar, copy the Braid package files (from my owned copy of Braid) to the same directory, run makepkg, then install via pacman.  The problem I am having is when I go to use makepkg I get the following error:
    # makepkg -s
    ==> Making package: braid 1.0.2-1 (DATE TIME)
    ==> Checking runtime dependencies...
    ==> Checking buildtime dependencies...
    ==> Retrieving Sources...
    ==> ERROR: There is no agent set up to handle file URLs. Check /etc/makepkg.conf.
    Aborting...
    I am not finding any solutions on Google.  Please help!
    Edit - Edited to show thread solved.
    Last edited by qKUqm3wtY4 (2013-01-03 17:00:49)

    SOLUTION! Provided by tdy
    braid-linux-build2.run.bin from Humble Indie Bundle 2 is required!
    You must edit the PKGBUILD file.
    source=("$_gamepkg"::"file://$_gamepkg"
    Change the source line to this:
    source=($_gamepkg
    Don't extract the braid file.  Just place it in the same directory as the PKGBUILD file.
    Run makepkg
    # makepkg -s
    Then run pacman
    pacman -U [filename].pkg.tar
    YOU ARE DONE!
    UPDATE!!!
    AFTER THIS THREAD WAS SOLVED, THE AUR PACKAGE WAS UPDATED TO SOLVE THIS ERROR.  JUST MAKE SURE YOU HAVE THE braid-linux-build2.run.bin FILE IN THE SAME DIRECTORY, AND THE INSTALL WILL WORK.
    Last edited by qKUqm3wtY4 (2013-01-06 09:18:11)

  • 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

  • Problem Wily Introscope Installation!

    Hi,
    I can not install on the server of the Solution Manager Wily Introscope ENTPR MGR 8 -> AIX 64bit 5.3 - java version "1.4.2"
    Java (TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20061124 (SR7) (JIT enabled: jitc)
    Used files are:
    SAPISEM8SP01_00-10007374.SAR
    osgiPackages.v1.1.unix.tar
    eula.txt
    Can you help?
    Best Regards.

    Hi,
    I installed the EM as explained Inst.Guide_Introscope Ver.8 for SAP
    using the files:
    SAPISEM8SP01_00-10007374.SAR (introscope8.1.0.0aix64SAP.bin)
    SAPISMM8SP01_00-10007429.SAR (management modules)
    Then I deploy with SDM the ISAGENTSMD801_01-10007435.SCA.
    Then I launched SOLMAN_SETUP:
    Initial Configuration -> ok (green)
    Basic Configuration -> ok (green)
    Managed System Configuration select the stack of hava Solman and click on "Configure System", Diagnostics Prerequisites are ok.
    In step 2 "Manual Configuration":
    -Install Diagnostics Agent (it was previously done by SDM)
    -Assign Diagnostc Agent -> Open URL -> Agent Administrator
    The problem arises at this point if you click on "Show offline agents" list is empty!
    Then I also tried to install the Wily Introscope Agent at hand but might as well not start.
    Can you help?
    My Solution Manager has been upgraded to 'EHP1 on AIX 5L with JVM:
    Java VM version: J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20090307 (SR13) (JIT enabled: jitc)
    Java VM vendor: Classic VM (IBM Corporation)
    java vm type: <default>
    java vm cpu: ppc64
    Regards.
    Diego.

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

  • 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

  • Hierarchy in Reporting Agent setting

    Hi,
    I have partner profit center (PPC) as a reference object of Profit ctr(PC). I have 2 hierarchies on PC.
    I am using those 2 in a query. (One with PC and one with PPC.)
    The problem is here:
    I have a reporting agent setting on this query. I use PC and PPC in it along with their respective hierarchies.
    But the hierarchy on PPC always shows the leaf nodes as output in the spool no matter what level I maitain. I want to have a higher level but certainly not the lowest level (leaf nodes).
    The hierarchy which i use in PPC is recently created. Has it something to do with the masterdata where is brings from or with the reporting agent setting itself.
    Please help with this.

    Hello Aarthi,
    Have you checked the dataprovider contains the negative values.
    Do a list Cube on the multiprovider and confirm it.
    Have you defined single exception for both or seperate exception. If 2 then check whether exception is active?
    Thanks
    Chandran

  • My wifi is greyed out my bluetooth n hotspot is not working and its showing problem in resetting all setting plez help.. :(

    my wifi is greyed out ..my bluetooth n hotspot is not working and its showing problem in resetting all setting plez help..

    Hello Prakharfromindia,
    Thank you for using Apple Support Communities.
    For more information, take a look at:
    iOS: Wi-Fi settings grayed out or dim
    http://support.apple.com/kb/ts1559
    iOS: Troubleshooting Bluetooth connections
    http://support.apple.com/kb/TS4562
    Use iTunes to restore your iOS device to factory settings
    http://support.apple.com/kb/ht1414
    Have a nice day,
    Mario

  • HT202213 Home sharing problem: I have never set up home sharing but I feel I understand it.  I recently (last 2 months or so) deauthorized, first time ever, all computers with my iTunes account. I am trying to set up home sharing but get  iTunes says "You

    Home sharing problem: I have never set up home sharing but I feel I the concept and how it works.  I recently (last 2 months or so) deauthorized, first time ever, all computers with my iTunes account. I have 3 computers authorized.  I am trying to set up home sharing but get  iTunes says:
    "Home Sharing could not be activated because this computer is not authorized for the Apple Id "#########@###.com". Would you like to authorize now?"  I click "authorize" and get the next error " You cannont authorize more than 5 computers.  You have already authorized 5 computers with this Apple ID.  To authorize this computer you must first deauthorize one of the other computers."
    Can someone help or shed more light on my problem?
    Thanks,
    Richard

    Home Sharing is designed to work on your local network not across the internet/cloud.
    Stuff is accessed under the Computers column where your local iTunes library on a local computer would appear.
    Home Sharing would share your iTunes content (i.e. stuff stored in itunes on the computer, not in the cloud) with AppleTV or an iPad etc on the SAME network.
    AppleTV2 will not be able to see itunes content on the work computer over the internet.  It's not designed to.  if the work computer was on the home network it would.
    iCloud is in it's infancy and is not a mature product - iTunes TV Show purchases appear on AppleTV, but currently music does not unless you are subscribed to iTunes Match. I find this rather odd to be honest, along with the inability to buy music on AppleTV2.  Movies purchased in iTunes are not authorised for iCloud viewing currently either.
    Maybe it has something to do with iTunes Match 'getting in the way' - i think they assume you'll use that whereas you really want to be able to access Purchased music from the cloud without subscribing to itunes Match which is overkill for some.
    AC

Maybe you are looking for