IDM 7.2 SP4: Internal Server Error

[Former Member]

Hello all,

im running a SAP IdM 7.2 SP 4 environment with the latest patch 1 installed and now facing the following problem:

After the patch has been installed, I have created an Entrytype,(not for identities) and two UI-tasks to create and update objects of that entrytype. Once I have created an object, I try to call the modify task. However, on clicking the "Choose Task" button on the UI I get an internal server error as shown below.

Does anybody of you have an idea what the problem is about? Any hint about how to fix it would be very appreciated.

Best regards,

manfred

***************

Error - Code:

500   Internal Server Error

Failed to process request. Please contact your system administrator.

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 at com.sap.idm.wd.jmx.SAP_ITSAM_IDM_TaskGroupResult$Impl.getChildTaskGroups(SAP_ITSAM_IDM_TaskGroupResult.java:257)

    at at com.sap.idm.wd.wf.taskhierarchies.TaskHierarchiesComp.retrieveTaskHierarchy(TaskHierarchiesComp.java:220)

    at at com.sap.idm.wd.wf.taskhierarchies.TaskHierarchiesComp.updateTaskHierarchy(TaskHierarchiesComp.java:285)

    at at com.sap.idm.wd.wf.taskhierarchies.wdp.InternalTaskHierarchiesComp.updateTaskHierarchy(InternalTaskHierarchiesComp.java:186)

    at at com.sap.idm.wd.wf.taskhierarchies.TaskHierarchiesCompInterface.showTaskHierarchy(TaskHierarchiesCompInterface.java:115)

    ... 38 more

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)

Version null

DOM version null

Client Type msie8

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.0110.20110629101433.0000 (release=NW701_10_REL, buildtime=2011-07-14:08:30:12[UTC], changelist=116130, host=pwdfm319.wdf.sap.corp), build date: Tue May 08 13:53:52 CEST 2012

J2EE Engine 7.01 PatchLevel 113005.

Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation

Operating system Linux, version: 2.6.5-7.244-smp, architecture: amd64

Session & Other

Session Locale de

Time of Failure Tue Jun 26 14:28:51 CEST 2012 (Java Time: 1340713731740)

Detailed Exception Chain

java.lang.NullPointerException

    at com.sap.idm.wd.jmx.SAP_ITSAM_IDM_TaskGroupResult$Impl.getChildTaskGroups(SAP_ITSAM_IDM_TaskGroupResult.java:257)

    at com.sap.idm.wd.wf.taskhierarchies.TaskHierarchiesComp.retrieveTaskHierarchy(TaskHierarchiesComp.java:220)

    at com.sap.idm.wd.wf.taskhierarchies.TaskHierarchiesComp.updateTaskHierarchy(TaskHierarchiesComp.java:285)

    at com.sap.idm.wd.wf.taskhierarchies.wdp.InternalTaskHierarchiesComp.updateTaskHierarchy(InternalTaskHierarchiesComp.java:186)

    at com.sap.idm.wd.wf.taskhierarchies.TaskHierarchiesCompInterface.showTaskHierarchy(TaskHierarchiesCompInterface.java:115)

    at com.sap.idm.wd.wf.taskhierarchies.wdp.InternalTaskHierarchiesCompInterface.showTaskHierarchy(InternalTaskHierarchiesCompInterface.java:124)

    at com.sap.idm.wd.wf.taskhierarchies.wdp.InternalTaskHierarchiesCompInterface$External.showTaskHierarchy(InternalTaskHierarchiesCompInterface.java:191)

    at com.sap.idm.wd.wf.entrysearch.TaskHierarchyView.wdDoInit(TaskHierarchyView.java:103)

    at com.sap.idm.wd.wf.entrysearch.wdp.InternalTaskHierarchyView.wdDoInit(InternalTaskHierarchyView.java:157)

    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.bindRoot(ViewManager.java:579)

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

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

    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.handle(ApplicationWindow.java:258)

    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.handleWindowEvents(ApplicationWindow.java:238)

    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:149)

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

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

    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]

Hi Manfred,

What was in the entrytype you were creating?

I'm assuming that you patched both the application and the database? 

Does all of the other functionality work correctly?

Could be a mismatched SCA file./

Matt

[Former Member]

Hello Matt,

yes, application and database have been patched. The entrytype "PROJECT" has relations to subordinate entry types for MX_PERSON and MX_PRIVILEGE. As aleady mentioned, creating objects of this entrytype works as designed, everythings else is working correctly as well.

Deleting the Entrytype and creating a new one didn´t help.

About the SCA files seems to be ok.

Manfred

[Former Member]

More than likely, one of your attributes is causing you this problem.  You may want to isolate which attribute is causing the problem.  Unselect all but the DISPLAYNAME and MSKEYVALUE attribute on your UI task.  See if it gives the same problem.  If it does not, then select 1 at a time and repeat until you see the error.  This will tell you which attribute is the culprit.

[Former Member]

I did some tests and could isolate the problem. The problem occurs when I allow subordinate entrytypes. I allowed subordinate entrytypes for MX_Priviliege and MX_Person, exactly as I did it with other entrytypes serveral times without any issue. Deselecting both entrytypes does not fix the problem. Seems there is something corrupt in the database, however, I have no idea, what could have caused this, right now. Any ideas?