cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to Configure EP Agent

Former Member
0 Kudos

Hi Gurus,

We have configured Solution Manager diagnostic and trying to add Enterprise portal system to E2E. We are getting following error when we are adding system.

Table Size Filter disabled steps

Details Success

Time

Type

Message

Wed Apr 22 15:32:38 2009 DataCollect Initial Data Collect ERROR for host SAPEPPCI

Step DataCollect Details

Initial Data Collect ERROR for host SAPEPPCI

!! Exception : Wed Apr 22 15:32:40 MDT 2009 | storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1240435926020447, name=SAP J2EE ENGINE 7.00, internalVersion=7.00 PatchLevel 111772.44, ppmsId=01200314690200004229, date=Wed Apr 22 15:32:39 MDT 2009, status=[N], mod=[M], messageServer=SAPEPPVCI:3902, masterComponent=true]'! Please see log for next warning(s).

Exceptions

com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: Wed Apr 22 15:32:40 MDT 2009 | storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1240435926020447, name=SAP J2EE ENGINE 7.00, internalVersion=7.00 PatchLevel 111772.44, ppmsId=01200314690200004229, date=Wed Apr 22 15:32:39 MDT 2009, status=[N], mod=[M], messageServer=SAPEPPVCI:3902, masterComponent=true]'! Please see log for next warning(s).

at com.sap.sup.admin.scheduler.task.remote.AbstractGatherRemoteTask.checkTaskResult(AbstractGatherRemoteTask.java:42)

at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.parseXml(InitialConfigGatherTask.java:107)

at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:68)

at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)

at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)

at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:348)

at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)

at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:736)

at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)

at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1000)

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

Wed Apr 22 15:32:40 2009 Wilyhost Agent Failed to configure EP Agent for SAPEPPCI

Step Wilyhost Agent Details

Failed to configure EP Agent for SAPEPPCI

!! Exception : java.lang.NullPointerException

Exceptions

java.lang.NullPointerException

at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.getByteCodeAgentName(AgentConfigWriter.java:611)

at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.createFileDestinationVO(AgentConfigWriter.java:398)

at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.processComponentSAP_J2EE_ENGINE(AgentConfigWriter.java:293)

at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.prepareSapAgentConfiguration(AgentConfigWriter.java:201)

at com.sap.sup.admin.wily.hostagent.Setup.setupAgentConfiguration(Setup.java:309)

at com.sap.sup.admin.wily.hostagent.Setup.executeSetup(Setup.java:74)

at com.sap.sup.admin.setup.AppCfgTasks.configureEPAgent(AppCfgTasks.java:109)

at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:352)

at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)

at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:736)

at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)

at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1000)

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

Any one came across with the same issue?

Thanks,

Miral.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

We figured out the issue in our server nodes..

Former Member
0 Kudos

Hi, I run into the same error. Can you tell me what you have done to fix this error?

Thanks

Klaas

Former Member
0 Kudos

I am running into this same issue when running diag setup for MDM managed systems. Could you share your resolution? Thank-you in advance