Error after reload the standard XML file in UWL Configuration Wizard

[Former Member]

Hi all,

We are working with UWL (EP7sp10) and encountered a problem. The UWL Configuration Wizard gave an error. We found on SDN/WIKI a posting with a workaround (<a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/BPX/UWL%2bConfiguration%2bWizard%2bshows%2bempty%2bdropdown">WIKI - UWL Configuration Wizard shows empty dropdown</a>)

We tried this working around, but it did not work. We uploaded the standard XML file again. Now we cannot access the link "Customize the look of the UWL main page" in UWL Administration.

We get a shortdump: 500 Internal Server Error

<b>LOGS & TRACES</b>

Exception occured during processing of Web Dynpro application sap.com/tc_kmcbc.uwl.ui~wd_admin/UWLControlCenterConfiguration. The causing exception is nested.

[EXCEPTION]

com.sap.tc.webdynpro.progmodel.context.ContextException: dropDownEntry<u>ComboMaincom</u>.sap.pct.erp.mss.Alert</u> is not a valid name for a node or attribute

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.validateName(NodeInfo.java:973)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:513)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:534)

at com.sap.netweaver.bc.uwl.ui.admin.wizard.NavigationNodeConfiguration.createTab(NavigationNodeConfiguration.java:830)

at com.sap.netweaver.bc.uwl.ui.admin.wizard.NavigationNodeConfiguration.populateTabs(NavigationNodeConfiguration.java:945)

at com.sap.netweaver.bc.uwl.ui.admin.wizard.NavigationNodeConfiguration.onActionFirstLevelNodeSelected(NavigationNodeConfiguration.java:252)

at com.sap.netweaver.bc.uwl.ui.admin.wizard.NavigationNodeConfiguration.onPlugfromListOfConfigurations(NavigationNodeConfiguration.java:223)

at com.sap.netweaver.bc.uwl.ui.admin.wizard.wdp.InternalNavigationNodeConfiguration.wdInvokeEventHandler(InternalNavigationNodeConfiguration.java:288)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

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

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

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

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

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

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

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

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

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)

It seems getting wrong at: dropDownEntryComboMaincom.sap.pct.erp.mss.Alert

What do I have to do now? Also a clean XML file upload from another SNP installation did not work.

Best regards,

G. Leurs

Message was edited by:

G. Leurs

Message was edited by:

G. Leurs

[Former Member · Accepted solution]

Hi Leurs,

Try doing the following:

1. Upload the new Standard XML file from the another portal server with same support version or replace the changes u made to original and upload

2. Remove the cache

3. Register for all systems

4. preview the UWL iView.

Regards,

Vinoth.M

[Former Member · Accepted solution]

Hi Vinoth,

Thanks for you reply, but these steps I have taken already; without result.

Hope that you know more of how to go back to the previous version.

At last we can put a back-up of the portal server.

Thanks a lot

Gijs

[Former Member · Accepted solution]

Hello,

I have solved the problem I was facing. There was a Configuration name ending with **.zip which was giving the error. I deleted this Configuration Name and cleared all caches again.

• Now, the dropdown box is empty again ***

Best regards,

G. Leurs

[Former Member]

I know the answer

[nazeer_syed2]

Hi Leurs,

I am facing the similar error, can you pls let me know the solution for the issue in UWL

Thanks,

Nazeer

[Former Member]

Hello,

This question is not answered yet. We still have a problem with changing the XML Configuration file com.sap.pct.erp.mss.001.

The steps mentioned above were done, the onlt result was that the page is visible again.

I urgently looking for an answer!

Best regards,

G. Leurs