cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to access to Agent null

Former Member
0 Kudos

Hi, gurus

I´ve configured SolMan 7.0 Stack 16 with Diagnostics. Diagnostics worked fine, with Wily Introscope and SMD Agent.

Today, I´ve this error:

2009.03.12 18:22:59, Failed to access to Agent null. (detail: java.lang.NullPointerException)

when I go to the link Diagnostics Administrator --> Managed Systems --> Agent Administation

The log viewer say that:

error 2009-03-12 18:28:06:136 Failed to access to Agent null.

java.lang.NullPointerException...

Full Message Text

Failed to access to Agent null.

java.lang.NullPointerException

at com.sap.ags.smd.agentadmin.SMDAgentAdminMain.createAgentsList(SMDAgentAdminMain.java:373)

at com.sap.ags.smd.agentadmin.SMDAgentAdminMain.wdDoBeforeNavigation(SMDAgentAdminMain.java:268)

at com.sap.ags.smd.agentadmin.wdp.InternalSMDAgentAdminMain.wdDoBeforeNavigation(InternalSMDAgentAdminMain.java:352)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doBeforeNavigation(DelegatingComponent.java:126)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doBeforeNavigation(ClientComponent.java:675)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doBeforeNavigation(ClientComponent.java:679)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doBeforeNavigation(WindowPhaseModel.java:470)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:140)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:215)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Any idea about that?

Regards,

Sergio.

Edited by: Sergio Mazzeo on Mar 12, 2009 8:33 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Since you mentioned it was working fine earlier, there can be few possibilites for your issue

Agent is running or not in Satellite system.

Verify the connecting user SMD_ADMIN in Solman.

Run the self check in Diagnostics which will few more details requried

Former Member
0 Kudos

Hello,

Any suggestion for this issue.

Regards,

Sergio.