on 12-10-2009 7:57 AM
Hello everyone,
Will someone please urgently help us with this issue? Any suggestions are greatly appreciated! : )
We are on AC v5.3 SP 8. In RAR, we are able to run a Risk Analysis both in the foreground and background across all users and roles. However, when we try to run a Risk Analysis in ERM or CUP, we get an error saying that the "Risk Analysis Failed". The other strange thing is that the error does occur for every role in ERM--just most of them. Also, the ERM management dashboard reflects the correct number of roles in the SAP back-end system, but it says that there are 0 risk violations, which is incorrect.
I have checked that the connectors into RAR successfully connect. I have confirmed the servers. I have re-run all of the background jobs in RAR, ERM and CUP, but nothing seems to be working.
Is there anybody that can please help us?
Thank you!
Johonna
Johonna,
Please check if connector /system names in CUP, ERM match with RAR connector names, then check if Risk analysis web service URL / User ID login details are correctly configured in CUP and ERM. If they are setup correctly, next thing to check is the Logs for error messages.
Please paste the CUP/ERM error logs if above checks don't resolve the issue.
Regards,
Amol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Amol,
Thank you for your suggestions. I have confirmed that the connectors, etc. are correct. Here are some of the error logs u2026 any ideas?
Thank you!
Johonna
95 12/15/09 12:20:51 PM Running Risk anaysis for role ZAU:FF_VFAT_ADMINISTRATOR failed
95 12/15/09 12:21:21 PM Running Risk anaysis for role ZAU:FF_VFAT_ROLE_ADMINISTRATOR failed
95 12/15/09 12:21:43 PM Running Risk anaysis for role ZAU:FF_VFAT_ROLE_CONTROLLER failed
95 12/15/09 12:23:13 PM Running Risk anaysis for role ZAU:FI_AA_CLERK_AGN failed
95 12/15/09 12:26:07 PM Running Risk anaysis for role ZAU:FI_AA_CLERK_GFA successful
2009-12-15 14:36:17,889 [Thread-7999] ERROR Risk Analysis failed
java.lang.Throwable: Risk Analysis failed at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:733)
at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysis(RiskAnalysisBO.java:234)
at com.virsa.re.backgroundjobs.RiskAnalysis.execute(RiskAnalysis.java:73)
at com.virsa.service.backgroundjobs.BackgroundTask.run(BackgroundTask.java:53)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
2009-12-15 14:36:24,811 [Thread-7999] ERROR Risk Analysis failed for sytem: 'PRD'; Return Message: 'Risk Analysis failed'
2009-12-15 14:36:24,811 [Thread-7999] ERROR com.virsa.core.service.ServiceException: Risk Analysis failed
java.lang.Throwable: Risk Analysis failed
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getTranViolations(RiskAnalysisEJBDAO.java:331)
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingTransactions(RiskAnalysisEJBDAO.java:171)
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingTransactions(RiskAnalysisEJBDAO.java:205)
at com.virsa.re.bo.impl.RiskAnalysisBO.performTranLvlRiskAnalysis(RiskAnalysisBO.java:483)
at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysis(RiskAnalysisBO.java:229)
at com.virsa.re.backgroundjobs.RiskAnalysis.execute(RiskAnalysis.java:73)
at com.virsa.service.backgroundjobs.BackgroundTask.run(BackgroundTask.java:53)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
2009-12-15 14:36:34,561 [Thread-7999] ERROR Risk Analysis failed for sytem: 'PRD'; Return Message: 'Risk Analysis failed'
2009-12-15 14:36:34,561 [Thread-7999] ERROR com.virsa.core.service.ServiceException: Risk Analysis failed
java.lang.Throwable: Risk Analysis failed
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getObjViolations(RiskAnalysisEJBDAO.java:812)
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingObjects(RiskAnalysisEJBDAO.java:596)
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingObjects(RiskAnalysisEJBDAO.java:633)
at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:693)
at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysis(RiskAnalysisBO.java:234)
at com.virsa.re.backgroundjobs.RiskAnalysis.execute(RiskAnalysis.java:73)
at com.virsa.service.backgroundjobs.BackgroundTask.run(BackgroundTask.java:53)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
2009-12-15 14:36:34,561 [Thread-7999] ERROR Risk Analysis failed
java.lang.Throwable: Risk Analysis failed
at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:733)
at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysis(RiskAnalysisBO.java:234)
at com.virsa.re.backgroundjobs.RiskAnalysis.execute(RiskAnalysis.java:73)
at com.virsa.service.backgroundjobs.BackgroundTask.run(BackgroundTask.java:53)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
2009-12-15 14:36:42,218 [Thread-7999] ERROR Risk Analysis failed for sytem: 'PRD'; Return Message: 'Risk Analysis failed'
2009-12-15 14:36:42,218 [Thread-7999] ERROR com.virsa.core.service.ServiceException: Risk Analysis failed
java.lang.Throwable: Risk Analysis failed
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getTranViolations(RiskAnalysisEJBDAO.java:331)
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingTransactions(RiskAnalysisEJBDAO.java:171)
at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingTransactions(RiskAnalysisEJBDAO.java:205)
at com.virsa.re.bo.impl.RiskAnalysisBO.performTranLvlRiskAnalysis(RiskAnalysisBO.java:483)
at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysis(RiskAnalysisBO.java:229)
at com.virsa.re.backgroundjobs.RiskAnalysis.execute(RiskAnalysis.java:73)
at com.virsa.service.backgroundjobs.BackgroundTask.run(BackgroundTask.java:53)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
ERM log doesn't have much details apart from error while doing object level analysis, can you please check RAR logs when error occurs. It is likely to give further details about exact error risk analysis webservice had.
Also as Alpesh suggested, can you please test Riskanalysis web service via WSNavigator to verify it runs successfully even for the falied cases.
Amol
Edited by: Amol Patil on Dec 15, 2009 7:22 PM
Hello Amol,
I am waiting for access from the client for the WSNavigator. I will test that as soon as I can.
I just ran the risk analysis for one role in ERM and it failed. Below are the logs from ERM and RAR. Any ideas?
Thank you!
Johonna
Job ID Last Modified On Status Message
99 12/16/09 11:04:53 AM Ready Job created
99 12/16/09 11:05:18 AM Running Job running
99 12/16/09 11:05:31 AM Running Risk anaysis for role ZAU:MM_PROC_INV_REPORTS_GFA failed
99 12/16/09 11:05:31 AM Completed Job completed
INFO: performActPermAnalysis completed ...
Dec 16, 2009 11:05:18 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS getNewJob
FINEST: New job ID:9412, file:.tmp_IWS9412
Dec 16, 2009 11:05:18 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start
INFO: Analysis Daemon [28609550]G:\usr\sap\AEG\DVEBMGS02\j2ee\cluster\server0\. processing Web Service Call ID:9412
Dec 16, 2009 11:05:18 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Before Rules loading, elapsed time: 0 ms
Dec 16, 2009 11:05:18 AM com.virsa.cc.xsys.util.RuleLoader getActRuleMatrix
INFO: No of Systems=1
Dec 16, 2009 11:05:22 AM com.virsa.cc.xsys.util.RuleLoader getActRuleMatrix
INFO: Action rules cache loaded: memory used in cache=97M, free=912M, total=2021M
Dec 16, 2009 11:05:22 AM com.virsa.cc.xsys.util.RuleLoader getActionRules
FINEST: Rule Loader Rules Size=>67418
Dec 16, 2009 11:05:22 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Rules loaded, elapsed time: 4000 ms
Dec 16, 2009 11:05:22 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : # objects to analyse: 1
Dec 16, 2009 11:05:22 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Analysis starts: ZAU:MM_PROC_INV_REPORTS_GFA
Dec 16, 2009 11:05:22 AM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
FINEST: ObjAuthMatcher constructed: 0ms, #singles=5, #ranges=0, #super=0
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Analysis done: ZAU:MM_PROC_INV_REPORTS_GFA elapsed time: 1938 ms
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : 1 out of 1 (100%) done
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : All Analysis done, elapsed time: 5985 ms , memory usage: free=761M, total=2021M
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysisRE
INFO: performActPermAnalysis completed ...
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS getNewJob
FINEST: New job ID:9413, file:.tmp_IWS9413
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start
INFO: Analysis Daemon [28609550]G:\usr\sap\AEG\DVEBMGS02\j2ee\cluster\server0\. processing Web Service Call ID:9413
Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Before Rules loading, elapsed time: 15 ms
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Rules loaded, elapsed time: 32 ms
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : # objects to analyse: 1
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Analysis starts: ZAU:MM_PROC_INV_REPORTS_GFA
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
FINEST: ObjAuthMatcher constructed: 0ms, #singles=5, #ranges=0, #super=0
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : Analysis done: ZAU:MM_PROC_INV_REPORTS_GFA elapsed time: 78 ms
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : 1 out of 1 (100%) done
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Foreground : All Analysis done, elapsed time: 157 ms , memory usage: free=1016M, total=2021M
Dec 16, 2009 11:05:25 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysisRE
INFO: performActPermAnalysis completed ...
Hi Johonna,
RAR log doesn't have any error/exception. I would suggest to open SAP message.
>Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
>INFO: Foreground : Analysis done: ZAU:MM_PROC_INV_REPORTS_GFA elapsed time: 1938 ms
>Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
>INFO: Foreground : 1 out of 1 (100%) done
>Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
>INFO: Foreground : All Analysis done, elapsed time: 5985 ms , memory usage: free=761M, total=2021M
>Dec 16, 2009 11:05:24 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysisRE
>INFO: performActPermAnalysis completed ...
>
Were you able to test the web service via WSNavigator for the failed cases?
Regards,
Amol
Hello,
No, I was able to test in the WSNavigator, as I do not have access. We opened a message with SAP and they have suggested that we move our GRC DEV/QA environment to a separate server than GRC PRD. The support team is working on that this week. I am not sure if this will resolve the issue. The client currently have the 2 GRC environments on the same server on separate instances. Have you ever seen this cause an issue before?
Thank you!
Johonna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.