Skip to Content
avatar image
Former Member

Error when editing a JCO

hello everyone!

delivery to acknowledge the help I can get.

I tell them my problem, I have a BI Server (ABAP + JAVA), which is trying to configure the JCO, but there is a problem when trying to create a new or an existing deal.

starting to enter the "Web Dynpro Content Administrator" presents the message "java.lang.NullPointerException"

to try to Edit or Create a JCO, gives the following error:

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

java.lang.NullPointerException

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)

at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:286)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)

... 45 more

See full exception chain for details.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; MEGAUPLOAD 1.0)

Version null

DOM version null

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime Vendor: SAP, build ID: 7.0020.20090723111631.0000 (release=NW04S_20_REL, buildtime=2009-08-14:13:18:26[UTC], changelist=65312, host=pwdfm114), build date: Wed Nov 11 21:35:52 AST 2009

J2EE Engine 7.00 PatchLevel 65302.450

Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation

Operating system AIX, version: 5.3, architecture: ppc64

Session & Other

Session Locale es_CL

Time of Failure Sat Apr 03 16:06:33 AST 2010 (Java Time: 1270325193642)

Web Dynpro Code Generation Infos

sap.com/tcwdtools

No information available null

sap.com/tcwddispwda

No information available null

sap.com/tcwdcorecomp

No information available null

Detailed Error Information

Detailed Exception Chain

java.lang.NullPointerException

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)

at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:286)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)

at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)

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

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:332)

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

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

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

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:219)

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

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

-


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Apr 05, 2010 at 04:41 PM

    Probably you might need to stop and start the service/application in VM(under deploy) or from NWA.

    The webdynpro application name should cover in sap.com/tcwd* (* means all followers).

    Let us know the outcome.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 02, 2010 at 09:46 PM

    The error produced by blocking some users

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      if there is edit and create options are showing disabled, you need to check SLDDSUSER and other user which are communicating with SLD of your landscape.