Introscope Agent fails for CE 7.2 systems

[Former Member]

Hi Experts,

Need help in resolving issue during Introscope Agent deployment on CE 7.2 system. We are getting following issue

Sep 3, 2011 8:20:00 PM [Thread[Thread-6,5,main]] Error VM Parameters update for node: 2140350 - Failed to update VM parameters

[EXCEPTION]

com.sap.smdagent.vmmanager.VMManagerException: Could not change the vm parameters, error:ERROR_CHANGE_PARAMETERS

at com.sap.smdagent.vmmanager.impl710.VMManager711.applyChanges(VMManager711.java:592)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)

at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)

at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)

at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)

at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)

at java.lang.Thread.run(Thread.java:678)

Also there is another issue being reported in the logs

Sep 3, 2011 8:16:47 PM [Thread[Thread-5,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - commandExists: file /usr/sap/SMD/SMDA97/exe/saposcol does

not exist, destination Process_Saposcol not available

Sep 3, 2011 8:16:47 PM [Thread[Thread-5,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - open(): file saposcol does not exist, destination not avai

lable

Can you pelase advise how can i resolve these issues.

BR

Davinder

[guilherme_balbinot · Accepted solution]

Hello Davinder,

I have replied to the OSS message, but I will post it here so we can share with the community.

-

---

The new error is due to a problem in JMX bean of the NWA application in the managed system. The issue is being investigated internally by SAP, as some other customers reported this error too.

Currently, please do the setup manually as a workaround.

Here are some considerations to follow to apply the workarond.

1) REPLACE XXX in the example below with your managed system SID, make sure to replace the J00 with yours as well).

2) CHECK if your managed system path is /usr/sap/DAA/SMDA97, adjust if necessary

3)CHECK your ISAGENT directory as well. In the example below version 8.2.2.2.0-2011-04-22 is used. Replace if necessary. You can go the the Managed system and browse all the way through the directory.

4) Apply the parameters

5) Insert the JVM parameters following on the server nodes of Managed system

-Dcom.wily.introscope.agent.agentName=XXX_J00_$[elem/Name]

-Dcom.wily.introscope.agentProfile=/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/IntroscopeAgent.profile

-javaagent:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.2.0-2010-04-22/wily/Agent.jar

6) Restart the java stack to take account the changes.

-

---

Don't forget to visit regularly our Wikis. We are putting a great effort to keep it up to date for 7.0 EHP1 and also for 7.1

[http://wiki.sdn.sap.com/wiki/display/SM] (Solution Manager Main Wiki)

[http://wiki.sdn.sap.com/wiki/display/SMSETUP] (Solution Manager - Setup and Configuration)

Best regards,

Guilherme Balbinot

Edited by: Guilherme Balbinot on Sep 4, 2011 12:46 PM

Edited by: Guilherme Balbinot on Sep 4, 2011 12:46 PM