IDM Display Error for one person

[former_member2987]

Hello every one,

I have a weird situation going on with my current project which is running IDM 7.2 (SP7) on Oracle. We have a task for modifying users. When ONE person (out of 20,000+) is selected, A NetWeaver error gets thrown. I've looked at the user data and the user's link data database tools and don't see anything unusual. The user does have a large number of assignments via idmv_link_ext (about 150) but I can't seeing that being the big issue. The user does work just fine on the Manage Search screen and I can see the detail data for the user without a problem.

I have included the NetWeaver trace info if it helps. Anyone have any ideas?

Thanks,

Matt

500 Internal Server Error <image001.png><image001.png>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 occurred 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.idm.wd.wf.entrydetails.EditEntry.supplyDynamicEntryNode(EditEntry.java:1720) at com.sap.idm.wd.wf.entrydetails.wdp.InternalEditEntry.supplyDynamicEntryNode(InternalEditEntry.java:492) at com.sap.idm.wd.wf.entrydetails.wdp.InternalEditEntry$_DynamicEntryNodeNode.doSupplyElements(InternalEditEntry.java:283) at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:406) at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:345) ... 34 more See full exception chain for details. System Environment Client Web Dynpro Client TypeHTML Client User agentMozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko Versionnull DOM versionnull Client Typemsie11 Client Type Profileie6 ActiveXenabled Cookiesenabled Framesenabled Java Appletsenabled JavaScriptenabled Tablesenabled VB Scriptenabled Server Web Dynpro RuntimeVendor: SAP, build ID: 7.0032.20141202044609.0000 (release=NW04S_32_REL, buildtime=2015-02-17:09:17:40[UTC], changelist=617496, host=PWDFM803.wdf.sap.corp), build date: Sat Sep 26 20:21:48 EDT 2015 J2EE Engine7.00 PatchLevel 123024.450 Java VMSAP Java Server VM, version:4.1.056 25.51-b02, vendor: SAP AG Operating systemLinux, version: 2.6.18-419.0.0.0.2.el5, architecture: amd64 Session & Other Session Localeen_US Time of FailureTue Oct 31 08:52:05 EDT 2017 (Java Time: 1509454325421) Web Dynpro Code Generation Infos sap.com/tc~idm~wd~workflow SapDictionaryGenerationCore7.0019.20090311102454.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:37:25[UTC], changelist=56826, host=PWDFM114.wdf.sap.corp) SapDictionaryGenerationTemplates7.0019.20090311102454.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:37:31[UTC], changelist=56826, host=PWDFM114.wdf.sap.corp) SapGenerationFrameworkCore7.0019.20090311102504.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:25:38[UTC], changelist=56831, host=PWDFM114.wdf.sap.corp) SapIdeWebDynproCheckLayer7.0019.20090311102650.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:43:39[UTC], changelist=56883, host=PWDFM114.wdf.sap.corp) SapMetamodelCommon7.0019.20090311102543.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:26:34[UTC], changelist=56850, host=PWDFM114.wdf.sap.corp) SapMetamodelCore7.0019.20090311102543.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:26:29[UTC], changelist=56850, host=PWDFM114.wdf.sap.corp) SapMetamodelDictionary7.0019.20090311102457.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:34:45[UTC], changelist=56827, host=PWDFM114.wdf.sap.corp) SapMetamodelWebDynpro7.0019.20090311102653.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:40:23[UTC], changelist=56884, host=PWDFM114.wdf.sap.corp) SapWebDynproGenerationCTemplates7.0019.20090401124456.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:53:13[UTC], changelist=59037, host=pwdfm114) SapWebDynproGenerationCore7.0019.20090311102650.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:43:45[UTC], changelist=56883, host=PWDFM114.wdf.sap.corp) SapWebDynproGenerationTemplates7.0019.20090401124456.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:53:13[UTC], changelist=59037, host=pwdfm114) sap.com/tc~wd~dispwda No information availablenull sap.com/tc~wd~corecomp No information availablenull sap.com/tc~idm~wd~model SapDictionaryGenerationCore7.0019.20090311102454.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:37:25[UTC], changelist=56826, host=PWDFM114.wdf.sap.corp) SapDictionaryGenerationTemplates7.0019.20090311102454.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:37:31[UTC], changelist=56826, host=PWDFM114.wdf.sap.corp) SapGenerationFrameworkCore7.0019.20090311102504.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:25:38[UTC], changelist=56831, host=PWDFM114.wdf.sap.corp) SapIdeWebDynproCheckLayer7.0019.20090311102650.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:43:39[UTC], changelist=56883, host=PWDFM114.wdf.sap.corp) SapMetamodelCommon7.0019.20090311102543.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:26:34[UTC], changelist=56850, host=PWDFM114.wdf.sap.corp) SapMetamodelCore7.0019.20090311102543.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:26:29[UTC], changelist=56850, host=PWDFM114.wdf.sap.corp) SapMetamodelDictionary7.0019.20090311102457.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:34:45[UTC], changelist=56827, host=PWDFM114.wdf.sap.corp) SapMetamodelWebDynpro7.0019.20090311102653.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:40:23[UTC], changelist=56884, host=PWDFM114.wdf.sap.corp) SapWebDynproGenerationCTemplates7.0019.20090401124456.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:53:13[UTC], changelist=59037, host=pwdfm114) SapWebDynproGenerationCore7.0019.20090311102650.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:43:45[UTC], changelist=56883, host=PWDFM114.wdf.sap.corp) SapWebDynproGenerationTemplates7.0019.20090401124456.0000 (release=NW04S_19_REL, buildtime=2009-06-07:20:53:13[UTC], changelist=59037, host=pwdfm114) Detailed Error Information Detailed Exception Chain java.lang.NullPointerException at com.sap.idm.wd.wf.entrydetails.EditEntry.supplyDynamicEntryNode(EditEntry.java:1720) at com.sap.idm.wd.wf.entrydetails.wdp.InternalEditEntry.supplyDynamicEntryNode(InternalEditEntry.java:492) at com.sap.idm.wd.wf.entrydetails.wdp.InternalEditEntry$_DynamicEntryNodeNode.doSupplyElements(InternalEditEntry.java:283) at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:406) at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:345) at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:333) at com.sap.tc.webdynpro.progmodel.context.Node.size(Node.java:721) at com.sap.idm.wd.wf.entrydetails.EditEntry.wdDoBeforeNavigation(EditEntry.java:365) at com.sap.idm.wd.wf.entrydetails.wdp.InternalEditEntry.wdDoBeforeNavigation(InternalEditEntry.java:360) 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:333) 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:185) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46) 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: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:1064) 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(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

[former_member2987]

Chenyang,

That does seem like the likely possibility, but this configuration has been in place for about 5 years and it only happens for the one person. However, anything is possible. Thanks for pointing this out.

Matt

[Chenyang]

It looks like a compability issue between the IdM UI and Idm database. Please check UI and DB are on the same SP level as well as the lastest patch level. If you launch other UIs for the same person, for instance, any UI without assignment tab, will the issue happen?

Cheers

Chenyang