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

Similar Messages

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

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

Upgrade introscope agent

Hi All,
I have currently below settings. EM is at version 8.2.3.5 and Introscope agents at version 8.1.0.0. Now i want to upgrade the version of the introscope agent via SDM in solution manager. For this do i need to undeploy the previous version first? or whether it will work without undeploying.
And for configuration i think i just need to run the setup for Introscope agent to deploy the new application version in satellite system from SMD. Let me know if i am wrong here.
Thanks,
Rohan

Hello
To update the ISAGENT on Solution Manager you can deploy the new version over your actual version using the force deployment method in SDM (Software Deployment Manager).
When you click on the deploy tab in the SDM, click on the + button browse to the ISAGENT SMD SCA file and confirm to add it. Next you have to expand the lower pane (push the arrow button to expand/subtract the pane) and choose "deploy any version".
Don't know if text is exact match but you have to choose the option that will enable you to deploy any version of the SCA file.
When choosing that option the current version is disregarded and the new SCA file is deployed anyway. You can even downgrade a Java component this way. In this case you deploy a newer version of course.
Don't forget to follow the post steps described in the SAP notes / Installation guide (Running upgrade in diagnostics setup for example).
To update individual Introscope Agents of your managed SAP systems you will have to redeploy those through the Introscope Agent setup.
Kind regards
Tom

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

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

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.

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

Wilyhost Agent setup finished successfully with limitations - SMD SPS15

Dear all,
we have connected different SAP J2EE systems to our Solution Manager Diagnostics without any problems. Now we are trying to connect the corresponding ABAP backend systems to the SMD. The Setup Wizard for these systems are completed with a warning. Everything seems to work fine, but the warning are spurious (we get only the yellow light, not a green one).
Did anyone has the same "problems" with ABAP managed systems and has anyone a solution for the yellow light ?
Thanks and best regards
Patrick
Error/Warning Message -
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager.
Created destination RT5|s3p5012_RT5_00
Created action RT5 - RT5 AbapSystem
Created action RT5|s3p5012_RT5_00 - RT5|s3p5012_RT5_00 AbapInstance
Created 2 action(s).
1 Wilyhost Agent(s) and 0 EP Agent(s) from host s3p2012 are connected to the EM.
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: RT5
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: RT5|s3p5012_RT5_00
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager.
Error/Warning Message -

Hi to all,
I have addition information about the Wily HostAgent problem. Here are some other alerts/warnigs from another SAP portal :
============================================================================
Jul 15, 2008 10:34:15 AM [Thread[SAP GC|FB7_J02_server3,5,main]] Error      com.sap.smd.wily.hostagent.action.GcScannerAction - scanInitial(): scan for file /usr/sap/FB7/J02/j2ee/../work/std_server3.outterminated: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
Jul 15, 2008 10:34:15 AM [Thread[SAP GC|FB7_J02_server3,5,main]] Error      com.sap.smd.wily.hostagent.action.GcScannerAction - doRun(): Action temporarily stopped: SAP GC|FB7_J02_server3
[EXCEPTION]
com.sap.smd.wily.hostagent.TransientException: java.io.FileNotFoundException: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
        at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:259)
        at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:391)
        at com.sap.smd.wily.hostagent.action.GcScannerAction.doRun(GcScannerAction.java:135)
        at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:52)
        at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
        at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.FileNotFoundException: /usr/sap/FB7/J02/j2ee/../work/std_server3.out (No such file or directory)
        at java.io.RandomAccessFile.open(Native Method)
        at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
        at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:372)
        ... 4 more
Jul 15, 2008 10:35:15 AM [Thread[Thread-364,5,main]] Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|FB7_J02_server2 not running because status is WAITING_FOR_DESTINATION
Jul 15, 2008 10:35:15 AM [Thread[Thread-366,5,main]] Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|FB7_J02_server1 not running because status is WAITING_FOR_DESTINATION
============================================================================

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

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

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

Wilyhost Agent setup finished successfully with limitations.

Solution Manager EHP1
While executing Managed system for Non-ABAP ( JAVA ) System , we are getting the problem
The Wily & SMD agent is already installed on the managed system
The error in Managed System Configuration :
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager
Logs of the SMDAgentApplication :
*Oct 12, 2009 2:33:23 PM [Thread[Thread-165,5,main]] Error      Error to retrieve the process from Message Server (detail: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine)*
[EXCEPTION] java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
at java.net.PlainSocketImpl.socketConnect(Native Method)
Oct 12, 2009 2:33:35 PM [Thread[Thread-177,5,main]] Error      RemoteOSService: operation failed - command is: mode=jstartup,mshost=epdev,msport=0,node=733441 [EXCEPTION]
com.sap.smd.plugin.remoteos.exception.ThreadDumpCommandException: Message Server Port must be specified!
at com.sap.smd.plugin.command.tda.ThreadDumpCommand.init(ThreadDumpCommand.java:89)
at com.sap.smd.plugin.remoteos.RemoteOSService.triggerDump(RemoteOSService.java:276)
Oct 12, 2009 3:03:27 PM [Thread[Thread-165,5,main]] Error      com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: Configuration Error: invalid property sysno for destination SapStartSrv_epdev_EPD_ at com.sap.smd.wily.hostagent.sapcontrol.SapControlDestination.open(SapControlDestination.java:52)
at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:82)
Oct 12, 2009 3:03:27 PM [Thread[Thread-165,5,main]] Error      com.sap.smd.wily.hostagent.SapAgent - startActions():
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: java.io.IOException: CreateProcess: saposcol error=2 at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:324)
at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:467)
at com.sap.smd.wily.hostagent.action.SapOsColAction.initSapOsCol(SapOsColAction.java:405)
at com.sap.smd.wily.hostagent.action.SapOsColAction.init(SapOsColAction.java:110)
at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:383)

Hi Rohan Pawar,
did you find some solutions. I've not the same problem but perhaps you now what the error means
i don't know which folder is expected.
Best regards
Thorsten Stracke
]] Error      com.sap.smd.wily.hostagent.SapAgent - startActions():
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: java.io.IOException: error=2, No such file or directory
        at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:324)
        at com.sap.smd.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:467)
        at com.sap.smd.wily.hostagent.action.SapOsColAction.initSapOsCol(SapOsColAction.java:405)
        at com.sap.smd.wily.hostagent.action.SapOsColAction.init(SapOsColAction.java:110)
        at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:383)
        at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:96)
        at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:112)
        at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:62)
        at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:119)
        at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:233)
        at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:307)
        at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:271)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:145)
        at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:504)
        at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:381)
        at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)
        at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:253)
        at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:164)
        at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:300)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
        at java.lang.Thread.run(Thread.java:664)
Caused by: java.io.IOException: error=2, No such file or directory
        at java.lang.UNIXProcess.forkAndExec(Native Method)
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        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.wily.hostagent.action.SapOsColAction.launchDaemon(SapOsColAction.java:465)
        ... 23 more

Introscope Agent Setup Error

Similar Messages

Maybe you are looking for