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.

Similar Messages

  • SAP GRC AC 5.3 - RAR Risk analysis Error Log

    Hi
    i have scheduled the background job for full sync risk analysis for the first time . the job ended with status error . critical analysis, user,role and profile action analysis is shown 100% . but the user permission analysis shows 49% , role and profile permission analysis show 97% each . where can i check the log for the errors . do i need to run the whole risk analysis job again ? when i check the management reports , risk violations are shown as zero . Please let me know how i can proceed at this stage . thanks
    Regards
    Prasad

    Thanks.
    First time please do for all users. I assume this was first time and it failed, so i will suggest you scheudle for all.
    once these are done, then periodic jobs should be increamental.
    few tips :
    - schedule user sync separate job and once it finish only then scheudle role sync and when role sync finishes, only then schedule profile sync
    - always select system ids from search help (which is F4 in ABAP)
    - best scheudle one job per system id, so that when failure occurs, so that error analysis is easy
    regards,
    Surpreet

  • CUP Risk Analysis Error

    Hi Experts,
    OUR GRC AC system configuration is: GRC AC 5.3 CUP Patch 7.0. One of our enduser has requested for a new role through CUP. While the manager performs the risk analysis, it is showing the following error: "Risk Analysis failed: Exception in getting the result from the webservice: service call exception, nested exception is: java.net.socket Timeout Exception: Read timout".
    Below is the system log of CUP for futher reference:
    2009-12-02 11:08:41,428 [SAPEngine_Application_Thread[impl:3]_12] ERROR com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested exception is:
                    java.net.SocketTimeoutException: Read timed out
    com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested exception is:
                    java.net.SocketTimeoutException: Read timed out
                    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(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)
    Caused by:
    com.virsa.ae.service.ServiceException: Exception in getting the results from the web service : Service call exception; nested exception is:
                    java.net.SocketTimeoutException: Read timed out
                    at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:343)
                    at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:451)
                    at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:569)
                    at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
                    at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
                    ... 24 more
    Caused by:
    java.rmi.RemoteException: Service call exception; nested exception is:
                    java.net.SocketTimeoutException: Read timed out
                    at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:90)
                    at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:99)
                    at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:311)
                    ... 28 more
    Caused by:
    java.net.SocketTimeoutException: Read timed out
                    at java.net.SocketInputStream.socketRead0(Native Method)
                    at java.net.SocketInputStream.read(SocketInputStream.java:153)
                    at java.io.BufferedInputStream.fill(BufferedInputStream.java:200)
                    at java.io.BufferedInputStream.read(BufferedInputStream.java:218)
                    at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
                    at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
                    at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
                    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
                    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:553)
                    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
                    at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
                    ... 30 more
    Could anyone please analyze, where it went wrong.
    Thanks a lot in advance.
    Regards,
    Gurugobinda

    We are facing this issue as well. This is seen in requests where there are a lot of conflicting roles requested, or if the user on the backend already has many SoD conflicts.
    How many risk violations did show up in the RAR simulation? Seems that above 1000 you will get performance issues in CUP risk analysis.
    We are also on SP7 and we did receive a reply from SAP that the risk violation threshold can be changed in RAR as of SP9:
    =======================================================
    From CUP 5.3 SP9 onwards, we have one parameter in RAR in
    'Configuration>Risk Analysis>Performance Tuning' which will
    enable you to set threshold violation limit for the Risk Analysis web
    service. The name of the attribute is 'Threshold Violation Limit for webservice' and default value of this attribute is 1000.
    When you perform risk analysis from CUP and the violation data count
    exceeds this limit then error message will appear.
    Setting this attribute will help tuning your performance.
    ==========================================================
    Regards,
    Stefan.

  • Risk Analysis error in AE

    Hi all,
    I am getting the following error message when trying to run a risk analysis in AE, which seems to be different from the error messages that others have posted in this forum.
    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'
    Any help on this is appreciated.
    Thanks!
    Erin

    Thank you - although my error message was different from others, the problem was the same - my naming convention for connectors in CC and AE were different, and the systems could not communicate.
    I found this post very helpful in solving the problem:
    Governance, Risk and Compliance (SAP GRC)
    Thanks!
    Erin

  • GRC 10 - Risk Analysis in legacy system

    Hi everybody,
    I have a problem with legacy connectors in GRC 10. I implemented the note 1594963. So, I created the legacy files and storage it in GRC server.
    When I run the user synch, the legacy connector only synch the first record.
    Someone can help me? Someone did implement a risk analysis for legacy systems?
    Regards,

    Hi  Claudio Ekel
    Can you share some inputs on the Legacy Risk Analysis.
    We have configured the Legacy Connector as per the note 1594963 ; Placed the files on the server & tried running Synchronization Jobs. But the data is not getting uploaded to GRC10 .
    We made sure that text files are in UTF-8 format
    Is it mandatory to load all the 11 files that are provided in the note 1594963? We have excluded the Profile related files
    Can you share a sample of Legacy file formats that you have used for the sync.
    Can you throw some light on what could be the possible issues for data not getting uplaoded to GRC10?
    Regards,
    Pavan Muthyala

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

  • GRC CUP risk analysis

    Hi,
    Risk analysis give risk status result in balls like red in critical, light red in high,orange in medium.we want,it should say critical,high,medium and low intead of balls and simulate also give same result as risk analysis.we also don't want if critical conflict then it should not allow that role/roles/request to be approved by approver.In stages it already set as "no" for approve roles despite any conflict and also in mitigation too in configuration.
    Thanks
    Mushu.

    Hi Mushu,
      None of these is possible in 5.x. You can not customize any of the screens or the process. Go for GRC 10.0 which will be going on ramp-up by end of december as that would allow you to customize most of the screens.
    Alpesh

  • GRC CC Risk Analysis download to Excel SE characters

    Hi All,
    I have performed a Risk Analysis in our GRC CC5.2 and the output was good. I was able to read Swedish characters in the Internet Explorer. However, when I download the report into Excel and open the file locally from my hardware, I see the Swedish Characters as:
    Anna Sjöberg                                        (via GRC CC in IE, it display Anna Sjöberg)
    Gerd Jönsson                                       (via GRC CC in IE, it display Gerd Jönsson)
    Anyone have the same display issue with Swedish characters?
    Thanks.
    Raymond

    Hi Raymond,
    Kindly let me know which version of Microsoft Excel are you using??
    If you are using excel 2000
    Check the note 1282267
    Regards
    Gangadhar
    Edited by: gangadhar hm on Sep 4, 2009 1:08 PM

  • GRC AC10 sync job error

    Hi Experts,
    I am getting error while running sync job. I searched but couldn't find a solution.
    We have two GRC AC10 clients setup, one is for fresh AC10 installation testing and another is for migration testing.
    Both clients talk to two different ECC clients. Issue is that we have setup all SPRO configurations, plug-in settings and stuff which is described in AC10 post -installation and migration documents,
    Sync job for one client is successful, but sync job for another client is giving error -
    Error message -
    Starting authorization sync for connector IE9_600 and language EN
    Error in IE9_600; Reason Error in RFC; 'Function module "/GRCPI/GRIA_AUTH_G
    PFCG authorization sync failed with errors
    I have checked plugin settings, RFC and other settings, it seems ok as it is in another client.
    What could be the cause and solution? Any suggestions are highly appreciated.
    Thanks in advance,
    Regards,
    Sabita

    The issue resolved, RFC was incorrectly pointed to wrong client.
    Regards,
    Sabita

  • Risk Analysis Error - Access Enforcer

    Hi Experts,
    I am getting error while running risk analysis in Access Enforcer and the error is
    <b>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'
    </b>
    We are using seperate RFC IDs for Access Enforcer connector and Comlaince Calibrator connector.
    Please help me.
    Thanks&Regards,
    Vijay

    Reddy,
    The user must indeed be created in the UME as a Compliance Calibrator user.
    I don't know exactly which role he should be assigned, usually I indicate there my CC admin user-id and password.
    When you see it is working with that user-id, you can try to re-fine the roles.
    Some more info regarding what needs to be set in the URI in case the one I inducated in my previous answer is not working:
    "There are two selectable versions of Compliance Calibrator. If you select 5.0 Web Service, three additional fields appear (URI, UserName, and Password). For the URI field, you need to navigate to the SAP NetWeaver Web Application Server Home page > Web Services Navigator > CCRiskAnalysisService > WSDLs > Standard link of Document, where you will see a list of all web services in the server. Select the desired URI address. If you select Compliance Calibrator 4.0, there is no need to connect to a URI address."
    Karim

  • Risk Analysis Error

    Hello All,
    Does anyone got this error while runing risk analysis on business owner stage ( where runing risk analysis is mandotory).
    "Risk Analysis filed: Exception voilation exceeds the treshhold limit : THERESOLD : 1000DETAIL:17275:SUMM 1354:MGMT:3
    THANKS MUCH IN ADVANCE

    Hi,
    Go to RAR->Configuration(tab)->Risk Analysis->Performance Tuning and change the value of "Web service violation limit " accordingly.
    As mentioned in the parameter desc- if set this value  to 0 (zero) then there is no upper or lower limit.
    I did the same to avoid any limitation on the error count.
    Regards,

  • 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.

  • AE5.2, CC5.2 Risk analysis error

    When performing a risk analysis in AE we get the following error:
    Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (400) Bad Request. The requested URL was:"http://HOST:PORT/VirsaCCRiskAnalysisService/Config1?wsdl"
    In AE config --> risk analysis we have setup
    Version: 5.2 Webservice
    URL: http://host:port/VirsaCCRiskAnalysisService/Config1?wsdl
    username: admin user for CC
    any ideas??
    thanks
    Naveed

    solved it.
    I was using the correct webservice, VirsaCCRiskAnalysisService
    but the link that is required is in RPC section under the folder for this service.
    Naveed

  • Full Batch Risk Analysis Error

    We just upgraded to SP13.  I got the following error when I scheduled the Full Batch Risk Analysis.  Please help:
    Oct 9, 2010 3:10:21 PM com.virsa.cc.common.util.ExceptionUtil logError
    SEVERE: null
    java.lang.NullPointerException
         at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForUserInputElement.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.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:792)
         at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:121)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1367)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:315)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1347)
         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:334)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:86)
         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:332)
         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(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)
    Oct 9, 2010 3:10:22 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
    FINEST: ObjAuthMatcher constructed: 2ms, #singles=818, #ranges=0, #super=0
    Oct 9, 2010 3:10:23 PM com.virsa.cc.common.util.ExceptionUtil logError
    SEVERE: null
    java.lang.NullPointerException
         at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthChgUserInputElement.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.getAuthChangedUsers(BackendAccessInterface.java:3674)
         at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedUsers(BackendAccessInterface.java:3664)
         at com.virsa.cc.comp.BackendAccessInterface.getObjDetails(BackendAccessInterface.java:1425)
         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:3969)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1709)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:315)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1347)
         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:334)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:86)
         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:332)
         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(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)
    Oct 9, 2010 3:10:23 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO:  Job ID:157 : Analysis done: 82547 elapsed time: 1760 ms

    rather than JCO, try running analysis with direct connection.
    in RAR you have option to give details of system.
    use that and if issue is resolved, then it means some problem with JCO connection.
    if issue is still not resolved, then please create OSS message.
    regards,
    Surpreet

  • 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.

Maybe you are looking for