CUP 5.3 (SP5): Error after creating mitigations and approving

[Former Member]

After creating a request, and mitigating the risks in the request, I receive the error:

Mitigation control <MC ID> could not be saved for user <USER ID> - Exception from the service : Mitigation record doesn't exist

However, the roles get autoprovisioned without the mitigating control being updated.

The error log shows this information:

2009-01-13 15:49:13,156 [SAPEngine_Application_Thread[impl:3]_29] INFO com.virsa.ae.service.sap.SystemDAOFactory : getMitigationControlDAO() : : cc version : 5.3_WS

2009-01-13 15:49:13,156 [SAPEngine_Application_Thread[impl:3]_29] INFO com.virsa.ae.service.sap.SystemDAOFactory : getMitigationControlDAO() : : mitigationDAO is set to MitigationControlWSDAO

2009-01-13 15:49:13,234 [SAPEngine_Application_Thread[impl:3]_29] ERROR javax.xml.rpc.soap.SOAPFaultException: 0

javax.xml.rpc.soap.SOAPFaultException: 0

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:860)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1439)

at com.virsa.ae.service.sap.wsMtg52.Config1BindingStub.execUpdateMitiControl(Config1BindingStub.java:90)

at com.virsa.ae.service.sap.wsMtg52.Config1BindingStub.execUpdateMitiControl(Config1BindingStub.java:115)

at com.virsa.ae.service.sap.MitigationControlWS52DAO.createMitigationControl(MitigationControlWS52DAO.java:198)

at com.virsa.ae.accessrequests.bo.MitigationControlBO.createMitigationControl(MitigationControlBO.java:134)

at com.virsa.ae.accessrequests.actions.CreateMitigationControlAction.createHandler(CreateMitigationControlAction.java:190)

at com.virsa.ae.accessrequests.actions.CreateMitigationControlAction.execute(CreateMitigationControlAction.java:83)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)

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

[Former Member]

I was getting an error in RAR that it couldn't send out the notification e-mail. The Java Mail Client had not been configured. Once I had done this, and restarted the server0, it worked.