Error creating request on CUP

[Former Member]

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!

[Former Member · Accepted solution]

I changed to 5.3 Webservice and now I receive the following message:

Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out

[Former Member · Accepted solution]

It seems the user may have lots of violations. Can you paste the logs here? Also, run the simulation for the same user and roles in RAR and check the number of violations.

Alpesh

[Former Member]

I am selecting the Versin 5.3 Webservice - Version 1 and the URI is:

"http://brmgebd.br.mahle:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document"

Edited by: Rodrigo Oliveira Nagamine on Sep 14, 2010 7:23 PM

[Former Member]

Hi,

The URL looks good from 5.3 Web service perspective. Can you change the version to 5.3 web service (instead of version 1) and try again? Can you make sure that the connector name in RAR and CUP are exactly same? Also, try to run risk analysis via Web service navigator by using the web service below. This way you can isolate the problem to RAR or CUP.

Regards,

Alpesh

[Former Member]

I just tried and I am getting the same error message:

Risk analysis failed: Exception in getting the results from the web service : E41F1363E5E8006900000CAC0000137000049039EADB6F21 : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:SAPGRC_CCRiskAnalysis_V01Vi'; Key name:'SoapRequestWrapper' key value:'execRiskAnalysis';

Any ideas?

[Former Member]

Rodrigo,

What is the web service URI that you have given in CUP?

Regards, Varun

[Former Member]

I ran RAR on its own and I didn't find any problems.

I also checked the webservice URI and it's apparently ok.

Any other ideas?

[Former Member]

Ricardo,

Try conducting risk analysis from a CUP request already created in CUP. This should clear up if web service is running fine or not...

Regards, Varun

[Former Member]

Yes, I tried changing the parameter to NO and now I am able to move with my requests.

Thanks!

But how can I solve this issue? Are there any ways I can figure out what's going on with CUP and RAR communication?

[Former Member]

Hello Ricardo,

This means that the problem lies in either the Integration aspects of CUP & RAR or with RAR itself. Try to run risk analysis in RAR for a user and then check how it goes. This should help you in rule out possibilities of problem in RAR. You can also check the integration aspects between RAR & CUP, specially the web service URI's provided in CUP.

Regards, Varun

[Former Member]

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