SAP Knowledge Base Article - Preview

2925409 - Byte Code Adapter Installation failed due to "Failed to connect via p4 channel - com.sap.smdagent.vmmanager.VMManagerException: Failed to use JMX service"

Symptom

"Byte Code Adapter Installation" activity fails with error: "Failed to update JVM parameters".

While checking error details by launching "Byte Code Adapter Installer", the following error message will be detected as shown below:

"Failed to connect via p4 channel - com.sap.smdagent.vmmanager.VMManagerException: Failed to use JMX service"

error in installer.png

In the SMDAgentApplication.*.log of the corresponding Diagnostics Agent, you may find a similar permission missing error like below:

"
[Thread[ExRun:default_2,5,default:ExecTG] ] Error [J2eeNodeIntrospector.getJavaPath]Failed to find javaPath for node 113376850
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException:Failed to use JMX service
at com.sap.smdagent.vmmanager.impl710.VMManager711._getSettings(VMManager711.java:218)
......
Caused by: com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException: [JmxProxy_1416051700_<SID>] Error in dynamic mbean operation invocation [mbeanName:com.sap.default:version=1.0,name=<SID>,type=SAP_ITSAMJ2eeCluster,j2eeType=J2EEServer,cimclass=SAP_ITSAMJ2eeCluster,SAP_ITSAMJ2eeCluster.Name=<SID>.SystemHome.<host name>,SAP_ITSAMJ2eeCluster.CreationClassName=SAP_ITSAMJ2eeCluster] [getAttribute:SAP_ITSAMJ2eeClusterJ2eeInstanceTemplatePartComponent]; nested exception is:

com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException: Runtime exception in connector occurred; nested exception is:
com.sap.smdagent.plugins.connectors.jmx.exc.RemoteJmxException: Caller <admin user> not authorized, required permission missing (javax.management.MBeanPermission -
"


Read more...

Environment

    • SAP Solution Manager 7.1
    • SAP Solution Manager 7.2 

    Product

    SAP Solution Manager 7.2

    Keywords

    JAVA Administrator, IS Agent. , KBA , SV-SMG-DIA-WLY-BCA , Byte Code Agent Setup , Problem

    About this page

    This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

    Search for additional results

    Visit SAP Support Portal's SAP Notes and KBA Search.