cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Go To menu in SP20

Former Member
0 Kudos

Hi all,

We are having a server with EP/KMC 6.0 SP20. When I go to the Portal Content -> KM Content iview and select any of the options from the Go To menu, it throws an error. The stack trace is given below. Has anyone experienced similar issues? We have another server at SP15 level. In that server it is working fine.

Thanks in advance.

Regards

Ranjith

The stack trace of the error:

[code]com.sapportals.wcm.WcmException: Could not execute command 'com.sapportals.wcm.rendering.uicommand.cm.UINavigationCommand'

at com.sapportals.wcm.rendering.uicommand.UICommandFactory.decodeTarget(UICommandFactory.java:660)

at com.sapportals.wcm.rendering.control.cm.CommandDispatcher.onExecute(CommandDispatcher.java:72)

at com.sapportals.wcm.rendering.control.cm.WdfProxy.onExecute(WdfProxy.java:2282)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sapportals.wdf.stack.Control.dispatchHtmlbEvent(Control.java:386)

at com.sapportals.wdf.WdfEventDispatcher.dispatch(WdfEventDispatcher.java:176)

at com.sapportals.wdf.WdfCompositeController.onWdfEvent(WdfCompositeController.java:539)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sapportals.htmlb.page.DynPage.doProcessCompositeEvent(DynPage.java:204)

at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:142)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

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

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

at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:110)

at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:333)

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

at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)

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

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)

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

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

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

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

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

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

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

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

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

[/code]

Accepted Solutions (1)

Accepted Solutions (1)

detlev_beutner
Active Contributor
0 Kudos

Hi Ranjith,

Just checked this on our KMC SPS20 (no P1), and saw the same. I expect this to be a regression from some changes how RIDs are passed to commands (there have been changes to decode paths with umlauts (mutated vowels) correctly):

https://service.sap.com/sap/support/notes/987865 -

-


The encoding of special characters is not sufficiently solved by the engine for the path-segment of a URL. Therefore, the URL parameter moves from the path segment to the query part. In paralell J2EE will work on a more reliable encoding.

This issue led to the following problem on UI side:

For resources with special characters (German Umlaut; Hebrew characters) in its filename it was not possible to use copy or move command from the details dialog. Using e.g. "Move" or "Copy" command in details dialog brought up an 'Item not found' (DE: 'Objekt nicht gefunden').

-


I know this topic quite well as I have pointed out this problem last december...

Please open an OSS message about this problem and be so kind to report any success / announced PatchLevel when this will be corrected.

Hope it helps / thanks in advance

Detlev

Former Member
0 Kudos

Hi Detlev,

Thanks for the info.

We are having a strange issue. We had upgraded 3 of our servers (sandbox, dev and test) to SP20. Sandbox was upgraded first and no patch was applied to it. But dev and test have SP20 Patch 1 applied to them. The issue is that this error is there in sandbox and test. But it is not there in dev server. After applying patch to dev and test servers, I tested this issue on both servers and both were working fine. So I thought this issue was solved in Patch 1. Now suddenly, this error has started coming again one of the servers but not in the other, even though both are running the same version up to the patch level. Any idea why?

I am planning to raise an OSS if this issue is persisting.

Regards

Ranjith

detlev_beutner
Active Contributor
0 Kudos

Hi Ranjith,

As we just patched KMC on one of our servers to P2, I rechecke it just again, and now it worked for me, too.

On the other hand, of course it is possible that the erroneous behaviour is not dependent on the patch level but just appears "suddenly" in a running system.

I would suggest to patch to KMC SP20 P2 and then, if the error comes up again, immediately open an OSS message. But of course, as this error is not reported in the KMC SP20 P2 buglist, you also could open an OSS message against P1.

If you get any feedback from the SAP support, please be so kind to report this here.

Thanks in advance

Detlev

Former Member
0 Kudos

Hi Detlev,

Apologies for the late reply.

The issue was resolved after restarting the server. I guess the server had some problems as we had some other issues as well in KM, which also got resolved after the restart.

Thanks & Regards

Ranjith

Answers (0)