Skip to Content
avatar image
Former Member

problem when accessng useradmin link in portal

Hi All

I have installed NW04s with support pack4 after that i have upgraded patch level to SP7.

After upgrading to SP7 http://<portalname>:<port>/useradmin gives following error

An error has occurred:

"Failed to process the request."

Please contact your system administrator.

Erro Stack Trace

java.lang.NoSuchMethodError: com.sap.tc.webdynpro.clientserver.uielib.standard.api.IWDTable.setEmptyTableText(Ljava/lang/String;)V

at com.sap.security.core.wd.maintainuser.wdp.InternalUserSearchResultView.wdCreateUITreeForUserResultTableAndActions(InternalUserSearchResultView.java:526)

at com.sap.security.core.wd.maintainuser.wdp.InternalUserSearchResultView.wdCreateUITree(InternalUserSearchResultView.java:492)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.createUITree(DelegatingView.java:74)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:292)

at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:232)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:403)

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

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.prepareTasks(AbstractClient.java:216)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:647)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.parseRequest(ClientManager.java:144)

at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.parseRequest(ApplicationHandle.java:79)

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:43)

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

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

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

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

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

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

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

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

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

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

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(Native Method)

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

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

Kindly help

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 11, 2006 at 02:31 PM

    Rajesh,

    check note 765573 - J2EE Engine 6.40 fails to start during upgrade to SP6 or SP7;

    If you are running mobile sales check

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/mba/~form/handler

    I think first note should solve your problem. Always check release notes as a standart/best practices before applying SP(s). I know it's painful/tedious, but i go through q LOT of notes daily. This is why I left Basis, I started dreaming about notes 😊

    James

    James

    Add comment
    10|10000 characters needed characters exceeded