cancel
Showing results for 
Search instead for 
Did you mean: 

Risk Analysis failure in CUP

Former Member
0 Kudos

Hi Experts,

We have upgraded our sandbox from GRC Access Controls v5.2 to version v5.3 SP7. I am now getting the following error when doing CUP Risk Analysis to RAR:

Risk analysis failed: Exception from the service : Risk Analysis failed

Any ideas?

The Connection Names are the same for CUP and RAR.

Here is the CUP log for the error:

2009-05-11 17:17:12,562 [SAPEngine_Application_Thread[impl:3]_36] ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed

com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed

at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)

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

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

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

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

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

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

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)

Caused by: com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed

at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:586)

at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)

at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)

... 24 more

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Gary,

This is really strange. If the risk analysis was working before upgrade, it should work after the upgrade as well. Can you make sure about the URL and look at these notes?

1085586, 1136379 and 1296632.

Regards,

Alpesh

Former Member
0 Kudos

I have checked the URl (or URI) and it is correct. I have reviewed those notes previously and they have not fixed it.

Former Member
0 Kudos

Hi Gary,

Is Risk analysis working fine in RAR and ERM?

Make sure the webservice user has not got password expired.

Give any other user id in URLs, save it and then change it to webservice user id and password.Password encryption method is changed in 5.3 patch 7 and without changing user once, it wont make the changes effective.

Check if RAR risk analysis is working fine.

Regards,

Sabita

Former Member
0 Kudos

Thanks for pointing out something I should have thought of...the CC Risk Analysis itself. I checked that and it was not functioning. We narrowed the issue down to the JCO connector userID and fixed that. Now everything is running just fine.

Thanks for your help!

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello All,

I am having the same issue in CUP

EXCEPTION_FROM_THE_SERVICERisk Analysis failed

com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed.

The Password for the web service has not expired or the URI is the same as the CCRiskanalysis service and as well the connectors have the same name in RAR & CUP.

It worked till yesterday and stopped working suddenly. Any help is appreciated.