on 06-03-2015 8:30 PM
Hi Aparecido,
Can you please attach a screenshot of the Log for Activity Byte Code Adapter Installation also.
Many thanks,
Ruth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Follow the logs.
Jun 7, 2015 8:01:48 PM [Thread[Thread-79,5,main] ] Error RemoteOSService: operation fai
led - cmd key=Parameters
[EXCEPTION]
com.sap.smd.plugin.remoteos.exception.InvalidCommandException: Command key=Parameters is not valid.
at com.sap.smd.plugin.remoteos.RemoteOSContext._executeOsSpecificCommand(RemoteOSContext.java:185)
at com.sap.smd.plugin.remoteos.RemoteOSContext.executeCommand(RemoteOSContext.java:103)
at com.sap.smd.plugin.remoteos.RemoteOSService.executeCommand(RemoteOSService.java:218)
at com.sap.smd.plugin.remoteos.RemoteOSService.executeCommand(RemoteOSService.java:205)
at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readRemoteOsCommand(OsCollect.java:496)
at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readStoreContent(OsCollect.java:223)
at com.sap.smd.agent.plugins.datacollector.os.OsCollect.collect(OsCollect.java:127)
at com.sap.smd.agent.plugins.datacollector.os.OsCollectp4_Skel.dispatch(OsCollectp4_Skel.java:60)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:337)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:728)
at java.lang.Thread.run(Thread.java:763)
Jun 7, 2015 8:01:48 PM [Thread[Thread-79,5,main] ] Error [ScriptExtractor] exception wh
ile getting configuration from os-command [Parameters]
[EXCEPTION]
com.sap.smd.plugin.remoteos.exception.InvalidCommandException: Command key=Parameters is not valid.
at com.sap.smd.plugin.remoteos.RemoteOSContext._executeOsSpecificCommand(RemoteOSContext.java:185)
at com.sap.smd.plugin.remoteos.RemoteOSContext.executeCommand(RemoteOSContext.java:103)
at com.sap.smd.plugin.remoteos.RemoteOSService.executeCommand(RemoteOSService.java:218)
at com.sap.smd.plugin.remoteos.RemoteOSService.executeCommand(RemoteOSService.java:205)
at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readRemoteOsCommand(OsCollect.java:496)
at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readStoreContent(OsCollect.java:223)
at com.sap.smd.agent.plugins.datacollector.os.OsCollect.collect(OsCollect.java:127)
at com.sap.smd.agent.plugins.datacollector.os.OsCollectp4_Skel.dispatch(OsCollectp4_Skel.java:60)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:337)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:728)
at java.lang.Thread.run(Thread.java:763)
Jun 8, 2015 12:32:36 AM [Thread[SID AbapSystem/60,5,WILYHOST_SCHEDU...] Warning JCOConnectorService.getAgentJ
coRepository: repository not found into pool SmdPool#hostname.domain.com.br#10#001#SMDAGENT_<SID>#-43095113#EN#5 al
ready created for system <SID>/10
hostname:sidadm 61>
I'm with my JAVA Solman working environment and I realized that in my PI-SOA environment does not have some items
In my Solman environment has two more items.
J2EE Node with the ID and Server 0 and IS Agent Name is the name of Instance_Server 0
And in the environment I'm in trouble PI-SOA does not have these options.
How do I be able to include this information and make the agent back up and running?
Willy Solution Manager Introscope is Version 8.2.4 and version of Wily Introscope PI-SOA is the 9.1.5.0 version.
Would if I update the version of Wily Introscope Solution Manager to version 9.1.5.0 I solve this problem.
Follow the screens attached.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.