Solution manager 7.1 sp4 , error @Bytecode adpater installation

[v_veeramalla]

HI All,

    I am facing the below issue while executing the managed system wizard @ Bytecode adapter installation.

Error @ Managed system

Failed to create Introscope Agent Connector at: /usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors: - java.io.IOException: Cannot run program "null/bin/java" (in directory "/usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors"): java.io.IOException: error=2, No such file or directory.

Error @ Diagnostic agent level

Jun 6, 2014 10:52:31 AM [Thread[Thread-19,5,main]

] Error

Operation Failed :

[EXCEPTION]

com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 48161

	at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
	at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
	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:94)
	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:285)
	at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
	at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
	at java.lang.Thread.run(Thread.java:679)

Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.

	at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.checkAuthorization(ConfigurationRuntimeInterfaceImpl.java:62)
	at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.getConfigurationContext(ConfigurationRuntimeInterfaceImpl.java:48)
	at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:331)
	at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:159)
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
	at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)

1. As per standard note , patch levels are on sap recommended level only.

2. Created connector manually as per wily documentation , but still no use.

3. Given the permissions for temp,<SID>cluster etc.. as per sap notes and restarted all the services including sapstartsrv

4. Assigend SPML roles as suggested by note.

5. checked java environment and umask  for diagnostic users , everything looks ok.

   Checked couple of notes related to the above issue ,

   1616058 - XSRF possible in SPML Services in AS Java

   1820230 - Byte Code Adapter Installation error in Solution Manager 7.1 Managed System Configuration step Configure Automatically

    1752441 - Introscope Agent Connector generation is done using JDK at: null

[v_veeramalla]

I can see the metrics in EM

But when i check ISAGENT admin , no info available for these agents

[v_veeramalla]

I would like paste few more error lines,

Jun 9, 2014 6:43:33 AM [Thread[FileSystemService_4cdecd7c,5,main]

] Error

[WHS] Failed to find javaPath for node 5818350

[EXCEPTION]

com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 58183

	at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
	at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
	at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
	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:94)
	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:285)
	at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
	at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
	at java.lang.Thread.run(Thread.java:679)

Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.

[roland_hennessy]

Hi Venkat,

Can you confirm your LM-SERVICE patch level? If possible can you upgrade to the latest level?

Kind regards,

Roland

[v_veeramalla]

SP04 for LM-SERVICE 710 Patch 5 .

Observed in some notes (1864284) that , upgrading will resolve the problem . But in my case since we are already on recommended levels as per note 1483508 though we are on correct LM service level.

Tried in another system with sp6 and sp8 update , but getting different kind of errors with non supported LM service patch level.

//Venkat V

[Former Member]

Hi Venkat,

As per below note Support Package 05 for LM-SERVICE 710 Patch 4 recommend for your SP level.

1483508 - Solution Manager 7.1: Root Cause Analysis pre-requisites

Please check wily introscope is up and running in the system

Rg,

Karthik

[v_veeramalla]

Wily is up and running , LM-SERVICE is on SP04 for LM-SERVICE 710 Patch 5 .

//Venkat v

[Sriram2009]

Hi Venkat

Could you refer the SAP Notes

1834066 - Solution Manager Managed Systems Configuration - Failed to get Instance properties for NW ...

1660105 - Introscope Bytecode Agent setup / ERROR_CHANGE_PARAMETERS

BR

SS

[v_veeramalla]

Thanks for the quick response,

i checked the notes , first one seems to be not relavnat since we are on 7.1 SP4 and all patches as per note 1483508.

Completed agent installation(creating connector,config parameters) as per blog

But still we are getting same issue ,

//Venkat V