Error During Risk Analysis in ERM

Hi Friends,
When I am creating a role in ERM in the step 'risk analysis' I am getting stuck. When I am clicking in 'GO' it is sayning system doesn't exist in RAR. But when I  am clicking it in Simulate it is sayinng background job scheduled and gone through the step and i can proceed from the approval step.
Please suggest if somwhere I am going  wrong.
Thanks & Regards,
Satyabrat
Edited by: Satyabrat Mohanty on Nov 5, 2009 3:54 PM

Please find the error details
Please find the error details below
2009-11-08 14:30:00,749 [SAPEngine_Application_Thread[impl:3]_13] ERROR java.lang.NullPointerException
java.lang.Throwable: java.lang.NullPointerException
     at com.virsa.re.bo.impl.RiskAnalysisBO.getTransactionsFromSTCODE(RiskAnalysisBO.java:842)
     at com.virsa.re.bo.impl.RiskAnalysisBO.performTranLvlRiskAnalysis(RiskAnalysisBO.java:443)
     at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:173)
     at com.virsa.re.role.actions.RiskAnalysisAction.performAndShowRiskAnalysis(RiskAnalysisAction.java:1430)
     at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:103)
     at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:270)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     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(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks,
Satyabrat

Similar Messages

  • Time Out ERROR CC Risk Analysis RFC

    Hi Friends,
    I am getting time out error when I am testing the CC risk analysis RFC. One thiing I monitor here is that when I am changing the parameters to 'YES' in tcode '/virsa/zrtcnfg',this RFC time out is occuring,when I am changing it back to 'NO' it is working fine.
    I beleive there is some system perfomance issue or any bottleneck is happenning.
    Please check error details of the Rfc below
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: program GRCRTTOCC5X not registered
    Error Details     LOCATION: SAP-Gateway on host hostname / sapgw00
    Error Details     DETAIL: TP GRCRTTOCC5X not registered
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 65055
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1960
    Error Details     RETURN CODE: 679
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Mar 11 09:21:35 2010
    Error Details     VERSION: 2
    and also some time I am getting below error
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: timeout during allocate of registered program
    Error Details     LOCATION: SAP-Gateway on host hostname / sapgw00
    Error Details     DETAIL: TP GRCRTTOCC5X init/busy for more than 60 sec
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 65068
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1937
    Error Details     RETURN CODE: 677
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Mar 11 09:29:56 2010
    Error Details     VERSION: 2
    Any suggestion please..
    Thanks & Regards,
    Satyabrat
    Edited by: Satyabrat Mohanty on Mar 11, 2010 11:54 AM
    Edited by: Satyabrat Mohanty on Mar 11, 2010 12:00 PM

    Hi,
    for further information  the latest log is
    2010-04-28 07:01:47,706 [SAPEngine_Application_Thread[impl:3]_18] ERROR  User :   not found to get full name
    2010-04-28 07:02:21,066 [SAPEngine_Application_Thread[impl:3]_11] ERROR
    java.lang.Throwable: java.lang.NullPointerException
         at com.virsa.re.workflow.client.WorkflowRequestClient.getRoleProcessContextDtos(WorkflowRequestClient.java:284)
         at com.virsa.re.workflow.client.WorkflowRequestClient.execSubmitRoleApprovalWF(WorkflowRequestClient.java:83)
         at com.virsa.re.workflow.actions.WorkflowRequestAction.submitApprovalRequest(WorkflowRequestAction.java:95)
         at com.virsa.re.workflow.actions.WorkflowRequestAction.execute(WorkflowRequestAction.java:54)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    FYI
    I have already checked all the webservices urls and password everything is fine.am I missing something.
    Regards,
    Satyabrat

  • Job Error- Batch Risk Analysis (Role Full Sync)

    Hi Experts,
    I have schedule the background job for Role analysis(Full Sync), but it gives an error- status error.
    all connections are working fine and pasted the error log for your reference.
    Oct 25, 2010 11:56:36 AM com.virsa.cc.common.util.ExceptionUtil logError
    SEVERE: null
    java.lang.NullPointerException
         at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthChgRoleInputElement.wdGetObject(IPublicBackendAccessInterface.java)
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
         at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
         at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedRoles(BackendAccessInterface.java:3735)
         at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedRoles(BackendAccessInterface.java:3724)
         at com.virsa.cc.comp.BackendAccessInterface.getObjDetails(BackendAccessInterface.java:1428)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.getObjDetails(InternalBackendAccessInterface.java:4327)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.getObjDetails(InternalBackendAccessInterface.java:4796)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjDetails(DataExtractorSAP.java:630)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.getObjInfoFromSource(AnalysisEngine.java:4140)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1754)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:317)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1366)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:559)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:362)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         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.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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)
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO:  Job ID:23 : Analysis done: T_00035951_H_IXOSCFGS elapsed time: 666 ms
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 23 Status: Error
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 23 Status: Error
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO: Detailed Analysis Time:
    Risk Analysis Time: Started @:Mon Oct 25 11:56:36 EDT 2010
    Rule Load Time: Started @:Mon Oct 25 11:56:36 EDT 2010
    Rule Load Time:0millisec
    Org Rule Loop Time: Started @:Mon Oct 25 11:56:36 EDT 2010
    Rule Loop Time: Started @:Mon Oct 25 11:56:36 EDT 2010
    Rule Loop Time:648millisec
    Org Rule Loop Time:649millisec
    Risk Analysis Time:686millisec
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    INFO:  Job ID:23 : Exec Risk Analysis
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO:  Job ID:23 : Before Rules loading,  elapsed time: 2 ms
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO:  Job ID:23 : Analysis starts: T_00035952_H_PMREAD_I
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1005
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1005
    Oct 25, 2010 11:56:36 AM com.virsa.cc.common.util.ExceptionUtil logError
    SEVERE: null
    java.lang.NullPointerException
         at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForRoleInputElement.wdGetObject(IPublicBackendAccessInterface.java)
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
         at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.executeBAPI(InternalBackendAccessInterface.java:4696)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:213)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:105)
         at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:813)
         at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:121)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1407)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:317)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1366)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:559)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:362)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         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.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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)
    Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
    FINEST: ObjAuthMatcher constructed: 0ms, #singles=27, #ranges=0, #super=0
    Oct 25, 2010 11:56:37 AM com.virsa.cc.common.util.ExceptionUtil logError
    Kindly do the needful.
    Regards,
    Arjun.

    Hi,
    1.Please check what type of connection is configuired in RAR(Adaptive RFC or SAPJCO). Please switch the connection type to SAPJCO.
    2. Please check the daemon & daemon manager statues.
    3. Check the Job threds in daemon manager after sechudeling job.
    Regards,
    Arjun.

  • CUP 5.3 SP 11.1 Exception during Risk Analysis

    Hi All,
    Can you please help in resolving this?
    Our current client has RAR and CUP.  RAR and CUP are connected to ECC and BW. ECC has SOD rule sets in RAR but BW does not. Can you please go through the following scenarios and help me resolve this:
    1> ECC is selected as Application and ECC roles are selected in request. When I perform Risk analysis it works fine.
    2> BW is selected as Application and BW roles are selected in request. When I perform Risk analysis it works fine ( 0 risks found).
    3> ECC and BW are selected for Applications and ECC and BW roles are selected in request. The Risk analysis failed giving an error message saying "EXCEPTION_FROM_THE_SERVICE Risk Analysis Failed". <BR>
    Here is the error log <BR>
    2010-04-15 08:26:09,420 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  NavigationEngine.java@85:execute() : Current Module: |AE| Conversation: |cnvCopyRequest| Screen: |scrRoles|
    2010-04-15 08:26:09,420 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  NavigationEngine.java@105:execute() :  Module#AE#Conversation#cnvCopyRequest#Screen#scrRoles#Action#selectRoles#
    2010-04-15 08:26:09,420 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  NavigationEngine.java@285:execute() : Handler found:class com.virsa.ae.search.actions.SearchRolesAction
    2010-04-15 08:26:09,420 [SAPEngine_Application_Thread[impl:3]_15] DEBUG com.virsa.ae.configuration.bo.AssignRoleGABO :  findRoleDetailsByName(String roleProfName) :   :  Enter,  roleProfName=PR0000EXEC
    2010-04-15 08:26:09,421 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  RoleDAO.sqlj@2625:findCustomFieldsbyRoleName() : INTO the method :  ctx=com.virsa.ae.dao.sqlj.SqljContext@7b4c7b4c roelProfName=PR0000EXEC
    2010-04-15 08:26:09,423 [SAPEngine_Application_Thread[impl:3]_15] DEBUG com.virsa.ae.dao.sqlj.RoleDAO : findCustomFields(SqljContext ctx, String roleProfName) :   : ,list size=0
    2010-04-15 08:26:09,424 [SAPEngine_Application_Thread[impl:3]_15] DEBUG com.virsa.ae.configuration.bo.AssignRoleGABO :  findRoleDetailsByName(String roleProfName) :   :  Enter,  roleProfName=PR0000EXEC
    2010-04-15 08:26:09,425 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  RoleDAO.sqlj@2625:findCustomFieldsbyRoleName() : INTO the method :  ctx=com.virsa.ae.dao.sqlj.SqljContext@7c927c92 roelProfName=PR0000EXEC
    2010-04-15 08:26:09,425 [SAPEngine_Application_Thread[impl:3]_15] DEBUG com.virsa.ae.dao.sqlj.RoleDAO : findCustomFields(SqljContext ctx, String roleProfName) :   : ,list size=0
    2010-04-15 08:26:09,425 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  RoleValidityHelper.java@160:isExpiredAsOfToday() : INTO the method : str : 12/31/9999
    2010-04-15 08:26:09,426 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  RoleValidityHelper.java@166:isExpiredAsOfToday() : INTO the method : dt : Fri Dec 31 00:00:00 PST 9999
    2010-04-15 08:26:09,426 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  RoleValidityHelper.java@176:isExpiredAsOfToday() : OUT of the method : boolResult : false
    2010-04-15 08:26:09,426 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
    2010-04-15 08:26:09,426 [SAPEngine_Application_Thread[impl:3]_15] DEBUG  AECacheUtil.java@956:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2010-04-15 08:26:09,427 [SAPEngine_Application_Thread[impl:3]_15] ERROR Ignoring exception, setting to default value : -1
    java.lang.NumberFormatException: For input string: "PR0000EXEC"
         at java.lang.NumberFormatException.forInputString(NumberFormatException.java:63)
         at java.lang.Integer.parseInt(Integer.java:492)
         at java.lang.Integer.parseInt(Integer.java:542)
         at com.virsa.ae.commons.utils.Util.parseInt(Util.java:1063)
         at com.virsa.ae.search.actions.SearchRolesAction.execute(SearchRolesAction.java:795)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         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.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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    2010-04-15 08:26:09,428 [SAPEngine_Application_Thread[impl:3]_15] ERROR Ignoring exception, setting to default value : -1
    java.lang.NumberFormatException: For input string: "AR0000SRAN"
         at java.lang.NumberFormatException.forInputString(NumberFormatException.java:63)
         at java.lang.Integer.parseInt(Integer.java:492)
         at java.lang.Integer.parseInt(Integer.java:542)
         at com.virsa.ae.commons.utils.Util.parseInt(Util.java:1063)
         at com.virsa.ae.search.actions.SearchRolesAction.execute(SearchRolesAction.java:802)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         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.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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    2010-04-15 08:26:09,428 [SAPEngine_Application_Thread[impl:3]_15] ERROR Ignoring exception, setting to default value : -1
    Thanks for your help.
    Anand

    RTA SP update solved the issue.
    Thanks

  • UM4_SCANNER error during INDX Analysis scan

    Hi Expert,
    We are performing Combined Upgrade & Unicode conversion (sapnote_0000928729) for our existing 4.6C system.
    We have completed Upgrade-PREPARE phase (till "checks") and now we have started MDMP pre-conversions SPUM4 scans.
    While performing INDX ANAYLSIS scan for table BDSCONT6, we came across ABAP dump - IMPORT_DECOMPRESS_FAILED.
    We have also perfomed runtime object check and database object check
    for above mentioned table. And repeated scan for table BDSCONT6.
    Please note that -
    1. we have successfully completed CUUC process for development-t06
    system.
    2. System is at kernel patch level 2541 (46D_EX2)
    Please check and advise us at the earliest.
    Thanks and regards,
    Meghan

    Hi Gerard,
    Thanks for response. Please find below error analysis for the ABAP dump IMPORT_DECOMPRESS_FAILED  
    Error analysis
    When IMPORTing compressed data, an error occurred when                        
    decompressing.                                                                
    Unable to read an IMPORT dataset.                                             
    The dataset may have been processed using SQL and is                          
    thus no longer readable for the IMPORT.                                       
    Thanks and regards,
    Meghan

  • ERM & CUP: Risk Analysis Error

    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

    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: Unable to run risk analysis

    Hey, we have recently configured ERM and during role creation when risk analysis is executed, we get the error: page can't be displayed".
    I have checked Miscellenous settings and it is updated with RAR web services as per the guide. I have checked the system (in landscape) and it is same as the RAR connector id. Should the landscape name also be same as RAR connector?
    Please help.
    Thanks,
    -S

    Hi Smriti,
    Here are few things that you can check:
    1. The configuration settings are correct.
    2. The ERM workflows are configured correctly.
    3. The three initial background jobs were completed successfully (Full Sync, Batch Risk Analysis, and Management Report)
    4. The performance of the system is good.
    5. The configuration settings for the RAR URL is properly maintained.
    If there is an issue with one of the above, you will have issues with performing risk analysis from ERM.
    You may additionally refer SAP Note 1136690 - Failed to perform Risk Analysis in ERM that may help you.
    Hope this helps!!
    Regards,
    Raghu

  • Risk Analysis: CUP Error: Exception Service

    Hi Guys,
    I am implementing GRC -CUP, where I found following error while performing the risk analysis from CUP.
    X - Risk analysis failed: Exception from the service : Inconsistency Org Rule Analysis Flag Parameter
    1. In RAR - we have not enabled Org. Rule Analysis.
    2. In CUP-Configuration tab- Risk Analysis link - I have disabled " Perform Org. rule Analysis"
    Yet, problem is coming in the system.
    Gurus,
    let me know if there are some errors from myside in RAR.
    Moreover, I am not able to integrate RAR with the CUP.
    Are there any steps which need to follow before integration?
    Thanks a ton
    SK

    Soumya,
       Can you look at the OSS Note # 1136379? I think you are missing the additional option "Consider Org. Rules when updating the Management reports and during Risk Analysis Web Service Call" part. Once you have set up everything similar to the OSS note option 2, test it.
    If it still doesn't work, bounce the server and test again.
    Regards,
    Alpesh

  • GRC AC10 Risk analysis error

    Hi Experts,
    We are getting error in Risk analysis.
    We have checked configuration, RFC, Batch Jobs, Rule Generation.
    Rules are showing active in Rules library, User and Roles are appearing while searching. I searched SMP for notes and sdn for similar issue but couldn't find anyone.
    During risk analysis, explorer gives dump -
    The URL call http://itdgrctest.itconline.in:8002/sap/bc/webdynpro/SAP/grac_sod_search_appln was terminated because of an error.
    Note
    The following error occurred in system G10 : File Could not be opened
    The error occurred on application server ITDGRCTEST_G10_02 and in work process 4 .
    The termination type was: ERROR_MESSAGE_STATE
    The ABAP call stack was:
    Method: UPDATE_FILE_DATA_DETAIL of program CL_GRAC_SOD_REPORTING=========CP
    Method: SET_VIOLATIONS of program CL_GRAC_SOD_REPORTING=========CP
    Method: WRITE_OUTPUT_TO_DB of program CL_GRAC_SOD_RISK_ANALYSIS=====CP
    Method: RISK_ANALYSIS of program CL_GRAC_SOD_RISK_ANALYSIS=====CP
    Method: DO_RISK_ANALYSIS of program /1BCWDY/0O2TMNDMBELX0AO58TG7==CP
    Method: IWCI_GRAC_RISK_ANALYSIS~DO_RISK_ANALYSIS of program /1BCWDY/0O2TMNDMBELX0AO58TG7==CP
    Method: EXECUTE_ANALYSIS of program /1BCWDY/0O2TMNDMBFK6DDPI1C1Q==CP
    Method: IF_SEARCH_VIEW~EXECUTE_ANALYSIS of program /1BCWDY/0O2TMNDMBFK6DDPI1C1Q==CP
    Method: ONACTIONSEARCH of program /1BCWDY/0O2TMNDMBFK6DDPI1C1Q==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/0O2TMNDMBFK6DDPI1C1Q==CP
    What can I do?
    If the termination type is RABAX_STATE, you will find more information on the cause of termination in system G10 in transaction ST22.
    If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server ITDGRCTEST_G10_02 in transaction SM21.
    If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 4 in transaction ST11 on the application server. ITDGRCTEST_G10_02 . You may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system adminmistrator.
    Error Code: ICF-IE-http -c: 600 -u: SABITADA -l: E -s: G10 -i: ITDGRCTEST_G10_02 -w: 4 -d: 20111115 -t: 162851 -v: ERROR_MESSAGE_STATE -e: File Could not be opened -X: 005056A41E8C1ED183EF148A3F5AFCCF_005056A41E8C1ED183EF142157E41CCF_1 -x: A4780FE1FA51F1DD9CCF005056A41E8C
    The termination type was: ERROR_MESSAGE_STATE, we I checked in St11. There error log is -
    N  *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c   1061]
    N  {root-id=005056A41E8C1ED183EEA264CAA11CCF}_{conn-id=005056A41E8C1ED183EEA264C5BA5CCF}_1
    N  *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c   1067]
    N  {root-id=005056A41E8C1ED183EEA264CAA11CCF}_{conn-id=005056A41E8C1ED183EEA264C5BA5CCF}_1
    M
    M Tue Nov 15 16:02:49 2011
    M  *** ERROR => AdCvtRecToExt: unknown opcode 71 (AD_OPCODE_71), ser 0, ex 0, errno 0 [adxx.c       2472]
    M  {root-id=005056A41E8C1ED183EEA4E10D4C3CCF}_{conn-id=00000000000000000000000000000000}_0
    M  *** ERROR => AdCvtRecToInt: unknown opcode 71 (AD_OPCODE_71), ser 0, ex 1, errno 1 [adxx.c       2530]
    M  {root-id=005056A41E8C1ED183EEA4E10D4C3CCF}_{conn-id=00000000000000000000000000000000}_0
    M
    If anyone has encountered the similar issue and has found a solution, please reply.
    Thanks in advance, Regards,
    Sabita

    Hi Experts,
    Iam also facing the same issue as below..
    Please let me konow if nay one of you encountered same issue and how you  resolved..
    Error while processing your query
    What has happened?
    The URL call http://yashgrcsrv.sapyash.com:8010/sap/bc/webdynpro/SAP/GRAC_UI_SPM_OWNER_POWL was terminated because of an error.
    Note
    The following error text was processed in system G10 : The ASSERT condition was violated.
    The error occurred on the application server YASHGRCSRV_G10_10 and in the work process 1 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_POWL_FEEDER~HANDLE_ACTION of program CL_GRAC_POWL_SPM_FFOWNER======CP
    Method: FEEDER_HANDLE_ACTION of program CL_POWL_MODEL=================CP
    Method: DISPATCH_ACTION of program CL_POWL_MODEL=================CP
    Method: DISPATCH_PREPARED_ACTION of program CL_POWL_TABLE_HELPER==========CP
    Method: ON_OBJECT_ACTION of program /1BCWDY/07CT55XNN6UHRCSZMBJE==CP
    Method: IF_TABLE_DATA~ON_OBJECT_ACTION of program /1BCWDY/07CT55XNN6UHRCSZMBJE==CP
    Method: ON_TOOLBAR_OBJECT_ACTION of program /1BCWDY/07CT55XNN6UHRCSZMBJE==CP
    Method: ON_TOOLBAR_OBJECT_ACTION of program /1BCWDY/07CT55XNN6UHRCSZMBJE==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/07CT55XNN6UHRCSZMBJE==CP
    Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
    What can I do?
    If the termination type is RABAX_STATE, you will find more information on the cause of termination in system G10 in transaction ST22.
    If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server YASHGRCSRV_G10_10 in transaction SM21.
    If the termination type is ERROR_MESSAGE_STATE, you cansearch for further information in the trace file for the work process 1 in transaction ST11 on the application server. YASHGRCSRV_G10_10 . You may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system adminmistrator.
    Error Code: ICF-IE-http -c: 100 -u: GRCADMIN -l: E -s: G10 -i: YASHGRCSRV_G10_10 -w: 1 -d: 20111117 -t: 124258 -v: RABAX_STATE -e: ASSERTION_FAILED -X: 00188B01D3231EE1849D72367EF328EF_00188B01D3231EE1849D723252D408EF_1 -x: 91EB10E1F7B3F19FA8EF00188B01D323
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Regards,
    Ravi Alluri.

  • AE Risk Analysis Error

    Hi,
    I am trying to run risk analysis in AE 5.2 while approving a request and I am getting following error message:
    Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.lang.Exception: Incorrect content-type found 'text/html'
    I checked CC and it is running fine. In AE, risk analysis url is fine and a user ID and password for RA are entered there. What can be the possible cause of this error other than possibility of initial password for RA user ID.
    Thanks

    Hi Alpesh
    We are using ERM 5.3 and we are getting the same error  when we tried to  ERM 5.3-, Role Management >  Roles ->  create ->  Authorization data -> Functions->  search ->
    When we are searching we are getting error as follows.
    Service call exception; nested exception is: java.lang.Exception: Incorrect content-type found 'text/html'
    Do you have any idea why this is happening?
    We have uploaded  re_init_clean_insert_data.xml , re_init_append_data,re_init_methodology_data .
    Is there any missing xml file to be uploaded to ERM 5.3.
    Please help.
    Thank you.

  • Error Creating Request - Risk Analysis in CUP

    Initially, we had the issue of not being able to create requests in CUP. I read around and found out that I needed to go to Configuration > Risk analysis and change the "Perform Risk Analysis on Request" to No. I tested and I was able to create a request. This tells me that SOMETHING is wrong with the Risk Analysis in CUP. So since its a Risk Analysis error, I when into a requested and selected Run Risk Analysis and go the following error.
    "Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.lang.Exception: Incorrect content-type found 'text/html' "
    But before anything. I just want to verify if its an authorization error with our webserivces id. Any input?
    Thank you,

    1. In the CUP Configuration-> Risk Analysis.
    Under the section "Select Risk Analysis and Remediation Version"( or "Select Compliance Calibrator Version" for version below CUP 5.3) make sure that the following web service is given in the URI, if the "Version" selected is above 4.0.
    "http://<servername>:<portnumber>/VirsaCCRiskAnalysisService/Config1?wsdl&style=document"
                                                                In the server name and port number, enter the corresponding entries of the Compliance Calibrator (CC) or (Risk Analysis and Remediation (RAR)) server entries on which it is installed.
    The User given under this section should have the administrator access for the CUP and RAR.
    CUP is 5.3 and we have the correct URL. The user is given the following roles:
    AEADMIN
    CC_Administrator
    VIRSA_CC_ADMINISTRATOR
    Please review the attachment for the list of actions in these roles. Please let me know if there is an action that the webservice id should have. In the link below, be careful of all the download buttons. Choose the "Save file to your PC: click here" link and open the file. (not save)
    http://www.2shared.com/document/8dOC7v6E/actions.html
    2. Make sure that the user provided in the CUP connector has the access for connecting to RAR and it should also have the administrator rights of the RAR.
    Should the access be provided from the roles/actions from above?
    3. Make sure that the password of both the users given in the above points is not expired i.e. they have been reset in UME.
    You can check the same by once logging into the UME through that users. In case it asks for the password change, then the password is expired and you need to change the password and give the new password in the CUP.
    Should the password ever expire for this ID? I will double check on the password.
    4. The logon language of both the above users should be maintained in UME.
    I am not sure how to check this, please advise.
    5. Also check that the connector in the RAR is working and is able to connect to the backend SAP system.
    I tested the connection in CUP and connection was successful. How can I test the connection for RAR?
    Thank you in advance,
    Edited by: Eric Lau on May 17, 2010 6:41 PM

  • CUP 5.3 (SP12) Risk Analysis Errors in CUP

    Hello Experts,
    When I run risk analysis in CUP for user provisioning. I get an error message:
    Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.lang.Exception: Incorrect content-type found 'text/html'
    Connector names are the same across all the components. We have a CUP test environment with SP11, and we did not have this kind of errors. I virtually tried everything I could.
    If you can, please assist me.
    HM

    Hello HM, 
    I had this error when I first upgraded to SP12 but I don't know if it is a SP issue or not.
    My CUP --> RAR SOD Analysis works for me on SP12.
    You might try double checking the following:
    1. Check all CUP configuration Web Service parameters in CUP --> Configuration --> 1) Risk Analysis & 2) Mitigation.
    2. Check that you uploaded the latest UME roles that were delivered with SP12.
    3. Check the UME user that is configured in CUP for risk analysis to make sure the password is still correct and that it has enough assigned roles.
    4. Make sure you uploaded all the required XML configuration files to CUP --> Configuration --> Initial System Data.

  • Error during Full Synch Batch Risk Analysis - RAR

    Hi All,
    We are implementation SAP GRC AC 5.3 - SP 9 - RAR
    Currently we have uploaded the text objects and permission objects and performed full sych for User, Roles & Profile with the backend system and it was successful
    Then we have uploaded all the RAR Standard text files for SoD Rules and scheduled a Full Sych for Batch Risk Analysis as a post installation activity. But we got an error as below after 85% of completion and the background job failed.
    WARNING: Error: while executing BatchRiskAnalysis for JobId=12 and object(s):T-RD470878: Skipping error to continue with next object: Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-01653: unable to extend table SAPSR3DB.VIRSA_CC_PRMVL by 8192 in tablespace PSAPSR3DB
    Can somebody please help us in resolving the above error message. Is it something to do with the table space availablity ?
    What are the consequences if we have not scheduled the Full Synch Batch Risk Analysis and start using the tool.We have to add some custom t-codes to the Standard rule set thereby tailoring it to the business requirement.
    Thanks and Best Regards,
    Srihari.K

    Sri,
       As Gangadhar mentioned this is a tablespace issue. You need to make sure to have enough space while running full sync risk analysis job. Please extend your database space and run the risk analysis job again.
    Regards,
    Alpesh

  • Risk Analysis Failing in ERM 5.3

    Hi All -
    I would appreciate some assistance with pin-pointing an issue that I'm having with running Risk Analysis on roles in ERM. Currently I have RAR configured with the appropriate rule set and generating the expected risk/sod conflicts for users & roles. I have also added the appropriate Web Service Info. in th Misc section under the configuration tab (url, user, pwd) for all sections associate with RAR integration.
    Now when I run a risk analysis on a particular role in RAR i get the correct conflicts however when I get the Risk Analysis stage with ERM I receive the following Error:
    Risk analysis failed; Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID) VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
    I also get this error when trying to run Mass Maintenance --> Risk Analysis:
    Risk anaysis for role "XX:XXXXX" failed
    Before I was getting error: "Risk Analysis performed successfully; No Risk Found" so I referenced SAP Note 1265964 and applied all solution steps.
    Lastly here is the error log:
    2010-01-14 14:59:28,768 [SAPEngine_Application_Thread[impl:3]_31] ERROR com.virsa.re.role.actions.RiskAnalysisAction
    java.lang.Throwable: Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID)  VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
         at com.virsa.re.bo.impl.RiskAnalysisBO.saveObjViolations(RiskAnalysisBO.java:906)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:824)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:214)
         at com.virsa.re.role.actions.RiskAnalysisAction.performRiskAnalysisOnMultipleRoles(RiskAnalysisAction.java:609)
         at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         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.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         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)
    Any help would be greatly appreciate it - Thanks in Advance!

    GOing to repost

  • Risk analysis Failure in ERM

    Hello Team,
    we got GRC 5.3 SP11, we have now started modifying our roles from ERM, the issue we are facing now is Risk analysis failing for any role from ERM.. please find the log content below and help!!
    2010-12-30 07:30:29,703 [SAPEngine_Application_Thread[impl:3]_38] ERROR Risk Analysis failed for sytem: 'TRDCLNT200'; Return Message: 'Risk Analysis failed'
    2010-12-30 07:30:29,703 [SAPEngine_Application_Thread[impl:3]_38] ERROR Risk Analysis failed
    java.lang.Throwable: Risk Analysis failed
         at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getObjViolations(RiskAnalysisEJBDAO.java:871)
         at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingObjects(RiskAnalysisEJBDAO.java:637)
         at com.virsa.re.service.sap.dao.RiskAnalysisEJBDAO.getConflictingObjects(RiskAnalysisEJBDAO.java:674)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:918)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:212)
         at com.virsa.re.role.actions.RiskAnalysisAction.performRiskAnalysisOnMultipleRoles(RiskAnalysisAction.java:604)
         at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         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.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
         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:427)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    2010-12-30 07:30:29,704 [SAPEngine_Application_Thread[impl:3]_38] ERROR com.virsa.re.role.actions.RiskAnalysisAction
    java.lang.Throwable: Risk Analysis failed
         at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:975)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:212)
         at com.virsa.re.role.actions.RiskAnalysisAction.performRiskAnalysisOnMultipleRoles(RiskAnalysisAction.java:604)
         at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         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.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
         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:427)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Hi,
      Is the connector name ''TRDCLNT200'' same in ERM and RAR? Make sure to maintain webservice URL with right username and password. Also, check to see if the password is not expired or not an initial password.
    Regards,
    Alpesh

Maybe you are looking for