Analysis Problem in RAR

[Former Member]

hi,

We have some troubles in Risk analysis and Remediation.

In the configuration tab, background job:

-User/Role and Profile Sync are OK

-But when we launch a user, role or profile analysis we always have the statuts error and the error message(in job history):

Failed: error while executing the job:Index , Size:0

So at the moment in the informer tab, we don't have any report.

Thank you in advance for your help,

Julien

[former_member184114 · Accepted solution]

can you paste the complete log here?

Regards,

Faisal

[Former Member · Accepted solution]

here is the end of the log (status error):

Tue Aug 26 21:48:45 CEST 2008 :  Job ID:68 : Analysis done: SAP_EMPLOYEE_ERP05_FR elapsed time: 0 ms 
Tue Aug 26 21:48:45 CEST 2008 : Job ID: 68 Status: Running
Tue Aug 26 21:48:45 CEST 2008 : Job ID: 68 Status: Running
Tue Aug 26 21:48:45 CEST 2008 :  Job ID:68 : Exec Risk Analysis
Tue Aug 26 21:48:45 CEST 2008 :  Job ID:68 : Analysis starts: SAP_WP_CEO_HOSP
Tue Aug 26 21:48:45 CEST 2008 :  Job ID:68 : Analysis done: SAP_WP_CEO_HOSP elapsed time: 0 ms 
Tue Aug 26 21:48:45 CEST 2008 : Job ID: 68 Status: Running
Tue Aug 26 21:48:45 CEST 2008 : Job ID: 68 Status: Running
Tue Aug 26 21:48:45 CEST 2008 : --- BKG Role Permission Analysis (System: E30) completed ---  elapsed time: 73609 ms 
Tue Aug 26 21:48:46 CEST 2008 : Index: 0, Size: 0java.util.ArrayList.RangeCheck(ArrayList.java:507)
java.util.ArrayList.get(ArrayList.java:324)
com.virsa.cc.xsys.bg.bo.BgSchedulerBO.getLastRunDate(BgSchedulerBO.java:627)
com.virsa.cc.xsys.bg.bo.BgSchedulerBO.updateLastRun(BgSchedulerBO.java:688)
com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1093)
com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1272)
com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:401)
com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:263)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:201)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:78)
com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Tue Aug 26 21:48:46 CEST 2008 : Job ID: 68 Status: Error
Tue Aug 26 21:48:46 CEST 2008 : ----------- Background Job History: job id=68, status=2, message=Error while executing the Job:Index: 0, Size: 0
Tue Aug 26 21:48:46 CEST 2008 : -----------------------Complted Job =>68---------------------------------------------------------------

[Former Member]

with "permission level report type":always statut error:

with "action level report type":status completed

but date and reports have not been updated in informer tab

[Former Member]

If you are using RAR and not CC then you are using AC 5.3, which is in Ramp Up, therefore these questions hosuld be addressed to your Ramp Up coach.

[Former Member]

I think the adminstrator did it. How can I check that the bg daemon is running?

[Former Member]

Hi Julien,

Check to see if the Background Workers and Web Service Workers are in IDLE status or RUNNING. All should show IDLE if the daemon is running properly.]

check note no. 999785 and 1121978

Best Regards,

Amol Bharti

[Former Member]

all the statuts are IDLE. I will paste the log tonight bu If I remember well, the log had some problems(error :xxx19 does not exit)

[Former Member]

Have you already configured the background daemon?