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

Similar Messages

  • Error creating request when using CUP in GRC 5.3

    Hello guru's
    when user is trying to create request in CUP , he is facing an error message at top indicating Error Creating Request ,
    The error message is " * Exception in getting the results from the web service : Service call exception; nested exception is:  java.lang.Exception: Incorrect content-type found 'text/html' * "
    can anyone help me how to trace the problem.
    thanks and regards,
    keerthi

    HI all
    I am also gettting same error like this..We created CUP Requests one hour before ..But we are not able to create CUP Requests now.. I got below error message in system log.
    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: (401) Unauthorized. The requested URL was:"http://c700u121.com:50000/SAPGRC_CCRiskAnalysis_V01/Config1?wsdl&style=document"
    2012-03-08 13:05:25,558 [SAPEngine_Application_Threadimpl:3]_23 ERROR com.virsa.ae.core.BOException: 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: (401) Unauthorized. The requested URL was:"http://c700u121.com:50000/SAPGRC_CCRiskAnalysis_V01/Config1?wsdl&style=document"
    com.virsa.ae.core.BOException: 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: (401) Unauthorized. The requested URL was:"http://c700u121.com:50000/SAPGRC_CCRiskAnalysis_V01/Config1?wsdl&style=document"
    at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
    at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:4087)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:408)
    at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:381)

  • CUP 5.3 - X Error creating request

    Good day.
    I have a issue, that I need assistance in resolving. I have successfully installed CUP 5.3 and I am testing the end to end functionality. I have create a request (request type - change account), populated all the mandatory fields, Selected a Role and successfully run the Risk Analysis.
    When I click on the Approve button, I recieve the error Error creating request. I am not sure where the issue resides.
    Any suggestions?
    Regards,
    Michael Hannie

    Good day William and Frank.
    What a day! I have double checked and the Number Range is activated. Please review the system log below.
    Thank you for all you assistance thus far -
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:05,293 [SAPEngine_Application_Thread[impl:3]_30] INFO  com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll :   :
    going to return no of records= 24
    2009-01-14 21:39:38,418 [SAPEngine_Application_Thread[impl:3]_27] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:39:48,840 [SAPEngine_Application_Thread[impl:3]_36] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:40:01,981 [SAPEngine_Application_Thread[impl:3]_10] WARN 
    com.virsa.ae.accessrequests.actions.RequestDetailsHelper : copyUserPropertiesToRequest() :  : Company Code not available in
    the system:
    2009-01-14 21:40:01,981 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:40:05,653 [SAPEngine_Application_Thread[impl:3]_15] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:40:16,716 [SAPEngine_Application_Thread[impl:3]_35] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:40:19,997 [SAPEngine_Application_Thread[impl:3]_31] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:40:36,935 [SAPEngine_Application_Thread[impl:3]_27] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:00,169 [SAPEngine_Application_Thread[impl:3]_39] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:41:00,185 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.dao.sqlj.ApplicationDAO :
    findAllForContext :   :  going to return ImmutableList(empty)
    2009-01-14 21:41:00,185 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.dao.sqlj.ApplicationDAO :
    findAllForContext :   :  going to return ImmutableList(empty)
    2009-01-14 21:41:14,591 [SAPEngine_Application_Thread[impl:3]_14] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:17,920 [SAPEngine_Application_Thread[impl:3]_27] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:41:17,935 [SAPEngine_Application_Thread[impl:3]_27] INFO  com.virsa.ae.dao.sqlj.ApplicationAreaDAO : findAll :
      : findAll() going to return # of records= 1
    2009-01-14 21:41:46,686 [SAPEngine_Application_Thread[impl:3]_28] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:50,139 [SAPEngine_Application_Thread[impl:3]_2] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:41:50,154 [SAPEngine_Application_Thread[impl:3]_2] INFO  com.virsa.ae.accessrequests.actions.RequestViewAction
    : pageLoad() :   : INTO the method
    2009-01-14 21:41:50,154 [SAPEngine_Application_Thread[impl:3]_2] INFO  com.virsa.ae.accessrequests.actions.RequestViewAction
    : pageLoad() :   : request number :
    2009-01-14 21:41:55,014 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:55,029 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestAuditHelper :
    logMajorAction() :   : intHstId : 183
    2009-01-14 21:41:55,029 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling saveRequestHeader()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] ERROR Ignoring exception
    com.virsa.ae.core.NoRecordsFoundException: no service level values are found for request attributes : {Request Type=CHANGE,
    Application=[400], Priority=LOW, Role=ZD_MM_BUYER_BCX}
    at com.virsa.ae.accessrequests.bo.SelectServiceLevelHelper.getServiceLevel(SelectServiceLevelHelper.java:92)
    at com.virsa.ae.accessrequests.bo.RequestBO.getDueDate(RequestBO.java:7873)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveRequestHeader(RequestBO.java:7719)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:345)
    at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
    at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
    at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
    at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
    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:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    adjustUserId() :   : INTO the method for strUserId : MICHAELH, user email : michael.hannieATa.bcx.co.za
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    adjustApproverDetails() :   : INTO the method for strApproverId : JOHANSW, approver email : johan.swanepoelATbcx.co.za
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling saveUsers()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling updateWithDefaultRoles()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    updateWithDefaultRoles() :   : Considering default roles is not enabled
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling updateWithRoleMappingRoles()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    updateWithRoleMappingRoles() :   : Role mapping is not enabled
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling saveApplications()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.service.sap.SystemDAOFactory :
    getRiskAnalysisDAO() :   : cc version : 5.3_WS
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.service.sap.SystemDAOFactory :
    getRiskAnalysisDAO() :   : risk analysis dao is set to RiskAnalysisWS52DAO
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.service.sap.SystemDAOFactory :
    getRiskAnalysisDAO() :   : cc uri : http://xgpmid01:50000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    2009-01-14 21:41:55,061 [SAPEngine_Application_Thread[impl:3]_10] ERROR java.lang.LinkageError: loader constraints violated
    when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
    java.lang.LinkageError: loader constraints violated when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-01-14 21:41:55,061 [SAPEngine_Application_Thread[impl:3]_10] ERROR Exception during EJB call, Ignoring and trying
    Webservice Call
    com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : loader constraints violated
    when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.LinkageError: loader constraints violated when linking
    com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         ... 26 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] ERROR java.rmi.RemoteException: Service call exception;
    nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
    java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         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:312)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:452)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:559)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode
    (ClientMimeMessage.java:120)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    (MimeHttpBinding.java:956)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1437)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
         ... 28 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] ERROR com.virsa.ae.core.BOException: Exception in getting
    the results from the web service : Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
    com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested
    exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         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: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.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:344)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:452)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:559)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 22 more
    Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         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:312)
         ... 26 more
    Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode
    (ClientMimeMessage.java:120)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    (MimeHttpBinding.java:956)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1437)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
         ... 28 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] ERROR BO Exception in Save request
    com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested
    exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         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: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.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:344)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:452)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:559)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 22 more
    Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         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:312)
         ... 26 more
    Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode
    (ClientMimeMessage.java:120)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    (MimeHttpBinding.java:956)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1437)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
         ... 28 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:42:27,577 [SAPEngine_Application_Thread[impl:3]_21] INFO  com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll :   :
    going to return no of records= 24

  • Error creating request on CUP

    Dear All,
    I am trying to create a new account request on CUP and I am getting the message "Error creating request", without any other help or info.
    I checked the log and that's what I got:
    Unknown Errorcom.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForUserInputElement.wdGetObject(IPublicBackendAccessInterface.java)
    com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
    com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInter... [see details]
    And the details are:
    Unknown Errorcom.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForUserInputElement.wdGetObject(IPublicBackendAccessInterface.java)
    com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
    com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
    com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
    com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
    com.virsa.cc.comp.BackendAccessInterface.getObjPermAuth(BackendAccessInterface.java:623)
    com.virsa.cc.comp.wdp.InternalBackendAccessInterface.getObjPermAuth(InternalBackendAccessInterface.java:4271)
    com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.getObjPermAuth(InternalBackendAccessInterface.java:4740)
    com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjPermissions(DataExtractorSAP.java:307)
    com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjPermissions(DataExtractorSAP.java:263)
    com.virsa.cc.xsys.meng.MatchingEngine.getObjPermissions(MatchingEngine.java:987)
    com.virsa.cc.xsys.meng.MatchingEngine.matchPrmRisks(MatchingEngine.java:466)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1536)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:315)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:244)
    com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:566)
    com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:362)
    com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:334)
    com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:86)
    com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
    com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
    com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
    com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
    com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    java.security.AccessController.doPrivileged(Native Method)
    com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Could you guys help me out on identifying the problem?
    Thks!

    Hello Rodrigo,
       While you are getting error in CUP, the logs it seems like states problem with risk analysis. Did you check if you have Configuration parameter "Perform Risk Analysis on Request Submission" Set to YES in CUP? Kindly check this. If this is set to YES, change it to NO and then try to submit request in CUP. This should clear up situation a little.
    This parameter is at CUP configuration -> Risk Analysis.
    Regards, Varun

  • GRC CUP Error creating request. Approver not found

    Hi,
    We just upgrade from GRC CUP 14 to GRC CUP 15.6 support pack.I already performed post upgrade steps and when i try to create a request i am getting approver not found.i didnot change workflow.In stage for role approver we have approver determinator "role".
    system log report
    com.virsa.ae.workflow.NoApproverFoundException: No approvers found for req no : 493, for reqPathId, 662, for path, PROD_APPRV_PATH and approver determinator : Role
         at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1469)
         at com.virsa.ae.workflow.bo.WorkFlowRequestCreateHelper.handleWFForNewPath(WorkFlowRequestCreateHelper.java:278)
         at com.virsa.ae.workflow.bo.WorkFlowRequestCreateHelper.createNewWorkflow(WorkFlowRequestCreateHelper.java:167)
         at com.virsa.ae.workflow.bo.WorkFlowBO.saveNewWorkflow(WorkFlowBO.java:120)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:579)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:381)
         at com.virsa.ae.accessrequests.actions.EUCreateRequestAction.createRequestHandler(EUCreateRequestAction.java:135)
         at com.virsa.ae.accessrequests.actions.EUCreateRequestAction.execute(EUCreateRequestAction.java:68)
         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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Please let me know solution ASAP.This is high priority.
    Thanks
    Yakoob.

    It looked like some old request stuck in DB.But, not sure about it.I tried by changing the number ranges in configuration by giving the current request number in "from number",but it didn't work.
    This is strange some time it gives "error creating request: path not found." and once this error gone then "error creating request : approver not found".
    To avoid this i created one more stage by custom approver determinator with application attribute and approver assiged.This stage, i assigned before role approver stage then it worked,Request get created and request get provisioned.
    i don't understand why it's not working,if i assigned role approver stage first in a path of workflow.role approver (approver determinator:"role" standard one, "approver" gets from configuration:roles:create role:role approver OR upload from role import).
    Please help
    Thanks
    Yakoob.

  • CUP 5.3 - Error creating request

    Dear expert,
    We have installed GRC Access control 5.3 (support package 8.0) and are facing a problem when trying to create a request in CUP:
    When creating a new request, we always get the error message "Error creating request" after trying to submit.  There seems to be no apparent problem with the workflow and we have filled out all mandatory fields.
    Thanks for your help in advance!
    Regards,
    Felix Poeschl

    Hello Alpesh, hello Shweta,
    We're pretty sure that the initiator is set correctly.  (The only condition for it to be actived is that a certain employee type is selected, which we select accordingly during request creation.)
    Below are the sections of the log durch creation of the request, where an error message appears.
    Thanks for your help!
    Regards,
    Felix
    1)
    2009-07-13 09:32:31,015 [SAPEngine_Application_Thread[impl:3]_8] ERROR com.virsa.ae.dao.sqlj.RequestDataHeaderDAO : insertUsers(IAETransaction txn,String reqNo,List listRequestDataUserDTOs) :   : SqlException occured, reqNo= 44 exception=[SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
    com.sap.sql.DuplicateKeyException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
         at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:259)
         at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.executeUpdate(RTStatementJDBCPrepared.java:267)
         at sqlj.runtime.ExecutionContext$StatementFrame.executeUpdate(ExecutionContext.java:1124)
         at sqlj.runtime.ExecutionContext.executeUpdate(ExecutionContext.java:718)
         at com.virsa.ae.dao.sqlj.RequestDataHeaderDAO.insertUsers(RequestDataHeaderDAO.sqlj:578)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveUsers(RequestBO.java:1505)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:359)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:268)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:89)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    2)
    2009-07-13 09:32:31,015 [SAPEngine_Application_Thread[impl:3]_8] ERROR Exception in saving the request
    com.virsa.ae.dao.DAOException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
         at com.virsa.ae.dao.sqlj.RequestDataHeaderDAO.insertUsers(RequestDataHeaderDAO.sqlj:605)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveUsers(RequestBO.java:1505)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:359)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:268)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:89)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.sql.DuplicateKeyException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
         at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:259)
         at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.executeUpdate(RTStatementJDBCPrepared.java:267)
         at sqlj.runtime.ExecutionContext$StatementFrame.executeUpdate(ExecutionContext.java:1124)
         at sqlj.runtime.ExecutionContext.executeUpdate(ExecutionContext.java:718)
         at com.virsa.ae.dao.sqlj.RequestDataHeaderDAO.insertUsers(RequestDataHeaderDAO.sqlj:578)
         ... 21 more
    3)
    2009-07-13 09:32:31,015 [SAPEngine_Application_Thread[impl:3]_8] ERROR BO Exception in Save request
    com.virsa.ae.core.BOException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:443)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:268)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:89)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.virsa.ae.dao.DAOException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
         at com.virsa.ae.dao.sqlj.RequestDataHeaderDAO.insertUsers(RequestDataHeaderDAO.sqlj:605)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveUsers(RequestBO.java:1505)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:359)
         ... 19 more
    Caused by: com.sap.sql.DuplicateKeyException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "VF_AE_RQD_USERS_1". The conflict occurred in database "ERP", table "SAPERPDB.VIRSA_AE_REQD_HDR", column 'REQNO'.
         at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:259)
         at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.executeUpdate(RTStatementJDBCPrepared.java:267)
         at sqlj.runtime.ExecutionContext$StatementFrame.executeUpdate(ExecutionContext.java:1124)
         at sqlj.runtime.ExecutionContext.executeUpdate(ExecutionContext.java:718)
         at com.virsa.ae.dao.sqlj.RequestDataHeaderDAO.insertUsers(RequestDataHeaderDAO.sqlj:578)
         ... 21 more

  • Error creating request. Path not found

    Hi,
    We are trying to create a request in CUP. We have given input in all the mandatory fields like Requester Name, Manager Name, Application and we have selected Roles. Those roles were already assigned to approvers.
    When we press the APPROVE button, it is asking to Approve. After clicking APPROVER button, it is giving error like u201CError creating request. Path not foundu201D.
    Please check and advice me where we are missing while creating request in CUP.
    Thanks & Regards,
    KKRao.

    Hi Sabita/Alpesh,
    Thanks for your reply. We have created two conditions under Initiator with AND and AND. We have cleared and we are not getting error like Path not found.
    Now we are getting error like "Error creating request. Approver not found".
    We have selected the Manger name in the request which we have defined in the Custom Approver Determinater. Still we are getting the error like Approver not found.
    Please check and correct me.
    Regards,
    KKRao.

  • Risk Analysis in CUP not working

    Hello Experts, we are using GRC 5.3. In CUP, I am trying to approve Role Provisioning. One of the requirements is to run Risk Analsys (as it says 'Risk Analysis is Mandatory'). When I hit the 'Risk Analysis' button, the circle keep circling but, nothing seems to happen forever (no error message either). Can you guide me in the right direction? What could be the possible situation? And, where am I better off to start troubleshooting.
    Thank you.

    Well, the problem seems to be that I am connecting from VPN. From my analysis, after I reboot the laptop, I am able to analyze risk for the first 3 or 4 requests and after that I can't do risk analysis for any more requests until I reboot my laptop. If I login to a remote server (say Virsa server), I seem to have no problem at all. i am able to continuoiusly run risk analysis for multiple requests. The problem seems to be VPN or my laptop.

  • Error while doing risk analysis for a user

    Hi ,
    When i did risk analysis at user level for a particular user we are getting this error under level  ."Exception!!. No relavent language message available in database for :0292".I had reuploaded the the messages text file but still the error persists i have restarted the j2ee application but still the error is not going .any pointers please thanx in advance.When checked the file CC5.3_MESSAGES.txt it does not contain any entry corresponding to message code 0292.So how shud i proceed.
    Edited by: Ambarish annapureddy on Jan 21, 2009 12:54 PM

    Hi Ambarish,
        What is the patch level of GRC AC 5.3? Did you apply any service pack recently? Did the service pack contain any message file? There has to be some message file which contains message '0292'. If you can not find the message file then open a message with SAP support and they should be able to provide it to you.
    Regards,
    Alpesh

  • Error while running risk analysis.

    Hi,
    I am facing problem, while running risk analysis from Access Enforcer for a particular application. Infact problem is for all the connectors. I have done required configuration.
    Error i am getting is "Risk analysis failed: Exception from the service : Risk Analysis failed".
    Please suggest.
    Thanks in Advance.
    Regards,
    Pravin.

    Problem was with JCO connection.

  • Error while performing Risk Analysis at user level for a cross system user

    Dear All,
    I am getting the below error, while performing the risk analysis at user level for a cross system (Oracle) user.
    The error is as follows:
    "ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPJ2EDB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.RC:1
    Can anyone please help.
    Regards,
    Gurugobinda

    Hi..
    Check the note # SAP Note 1121978
    SAP Note 1121978 - Recommended settings to improve peformance risk analysis.
    Check for the following...
    CONFIGTOOL>SERVER>MANAGERS>THREADMANAGER
    ChangeThreadCountStep =50
    InitialThreadCount= 100
    MaxThreadCount =200
    MinThreadCount =50
    Regards
    Gangadhar

  • Error while running risk analysis in CC 5.2

    Hi guys,
    the present client i am working with had installed GRC CC 5.2 long back, they have given me the access to CC and when i am trying to run some basic reports in the informer tab the following error pops in
    type com.virsa.cc.modelvirsaxsr3_01.types.So_Text001 could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.RC:1
    Error while executing the Job:Interface Controller does not exist for Component Instance VirsaXSR3_01 in Component Usage VirsaXSR3_01
    is it something related to the connectors.
    appriciate any suggestions.
    thanks.
    Edited by: sap sec on Nov 25, 2008 12:55 AM

    Hi,
    Check below:
    Is your ABAP system configured in the System Landscape Directory (SLD)
    Your ABAP system has a default logon group defined
    Your ABAP system can be accessed by the J2EE system services file
    Regards,
    Naveen

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

  • CUP Risk Analysis results are not shown, continues processing request

    We have several users that complain the risk analysis in CUP never finishes. Requests do not contain risks or huge amount of risks which could explain a long runtime.
    With one user we checked, the user is never getting the risk analysis result on his screen. Sitting together with the user shows that the progress bar at bottom of IE is completing analysis, however the screen is not updated to show the risk analysis result and continues to show the processing circle.
    On other pc's CUP risk analysis result is shown as expected, so it must be some issue in local PC Internet Explorer settings.
    Environment used is Windows XP with IE 8. GRC version is 5.3.
    Have any of you experienced the same? And is there a solution available that will resolve this issue, by e.g. correcting settings in IE 8?

    Hello!
    If you want to successfully use GRC 5.3 with IE8, you have two options:
    1) Change a parameter in the server
    2) use the compatibility mode.
    3) Update NW
    refer to [Note 1347768 - Web Dynpro and Microsoft Internet Explorer Version 8.0|https://service.sap.com/sap/support/notes/1347768]
    I dismiss option 2, because it requires to change in every end user computer, so I've been working with option 1 without problems. Bear in mind that NW 7.01 is supported:  [Note 1433940 - Access Control compatibility on Netweaver Java server 7.01|https://service.sap.com/sap/support/notes/1433940]
    Cheers!
    Diego.

  • Risk Analysis in a CUP request

    Is there any way to run a Risk Analysis in a CUP request on different Rule Sets?
    Letu2019s say you have 3 different Rule Sets like US - EU u2013 Global defined in RAR. Each one includes its own risks. In a CUP
    request, it shows risks based on the u201CVirsaCCRiskAnalysisServiceu201D defined in your CUP config.
    In our case we use the global Rule Set but the problem is for an EU request you can have US risks appearing that must be mitigated even if those risks are not relevant for EU.
    It would be great if we could link the attributes Company or Functional Area directly to a specific rule set.
    Please help/comment on this issue.
    Regards

    Hi,
    When we perform risk analysis on the request, ruleset for the risk analysis for CUP request is picked from RAR default values.
    RAR-> Configuration-> Default Values-> Default rule set for risk analysis.
    This rule set is picked by CUP to perform the risk analysis.
    With the current design it is not possible to link  the attributes Company or Functional Area directly to a specific rule set.
    Kind Regards,
    Srinivasan

Maybe you are looking for

  • Streams between 9i Enterprise and 10g Standard

    Hi, I'm currently trying to configure streaming between an oracle 9i Enterprise database and a 10g Standard Database. First of all, I would like to know if this is a configuration that can be done. Actually I'm facing some problems on the 9i side...

  • ClassCastException with ClassLoader issues

    I'm using JBoss 3.2.3, with Kodo 3.1.0 After doing a hot deploy in JBoss, ClassCastExceptions start occuring. String filter = "reference==param1"; Extent extent = pm.getExtent(Customer.class, false); KodoQuery query = (KodoQuery) pm.newQuery(extent,

  • OBIEE 11.1.1.7, Win 8, Admin tool not opening.

    Dear Experts, I have recently installed OBIEE 11.1.1.7, on windows 8, 64bit, I3 processor and 6 GB ram configuration. Installation is successfull, i can login all console,em, answers etc. Only issue is Administration tool to manage to RPD is not open

  • Error when running OPatch 11.2.0.1.3

    I just finished running the OUI for 11.2.0.2. I am Installing the Current Patch Set for 11.2.0.2 - OPatch_11201_Generic_v3.zip  I have unzipped the OPatch_11201_Generic_v3.zip file to oracle/<DBSID>/112_64/ and when I try to apply it, I get the below

  • [SOLVED] GVFS errors

    Hello, I tried everything, including upgrading my system, re-installing the packages and all the troubleshooting I was able to find on the wiki and Internet. Whenever I try to run applications like Thunar or pcmanfm I get this kinds of errors: (pcman