GRC 5.3 SP12 CUP: Error approving Risk-Request

[Former Member]

Hi together,

we have a problems approving risk-update-requests or other workflow-requests based on RAR.

We have opened a sap-message (08.09.2010) but their is no solution by sap yet.

We changed already often the URLs in RAR Configauration - Workflow.

Can somebody help?

Thanks.

Alexa

See attached the error-log:

2010-11-22 10:22:07,188 [SAPEngine_Application_Thread[impl:3]_0] ERROR Service call exception; nested exception is:

com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://saps080.sap.convista.local:50000/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document"

java.rmi.RemoteException: Service call exception; nested exception is:

com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://saps080.sap.convista.local:50000/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document"

at com.virsa.ae.request.ws.cc.Config1BindingStub.execWFExitService(Config1BindingStub.java:87)

at com.virsa.ae.request.ws.cc.Config1BindingStub.execWFExitService(Config1BindingStub.java:96)

at com.virsa.ae.accessrequests.bo.RequestExitServiceHelper.callCCExitService(RequestExitServiceHelper.java:263)

at com.virsa.ae.accessrequests.bo.RequestExitServiceHelper.callExitServiceForApprovedRequest(RequestExitServiceHelper.java:51)

at com.virsa.ae.accessrequests.bo.RequestBO.callExitService(RequestBO.java:6795)

at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:6634)

at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:6427)

at com.virsa.ae.accessrequests.actions.RequestViewAction.confirmRequestApproval(RequestViewAction.java:952)

at com.virsa.ae.accessrequests.actions.RequestViewAction.execute(RequestViewAction.java:104)

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

Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://saps080.sap.convista.local:50000/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document"

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:998)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1452)

at com.virsa.ae.request.ws.cc.Config1BindingStub.execWFExitService(Config1BindingStub.java:80)

... 33 more

[Former Member]

Hi,

Best option is to reset the password for the user in the backend system. Ensure that the user is in validity date and has all the required authorizations.

Maintain the new password in the Jco connectors used for CUP and RAR.

Hope this will resolve the issue.

Regards,

Raghu

[koehntopp]

Raghu,

this has nothing to do with the backend - it's when CUP tells RAR that a risk change has been approved.

I only just saw the URL - look in CUP - Configuration - Miscellaneous. Look up the risk change URI and enter the correct user/password there, then it should work.

Frank.

[Former Member]

Frank is correct. I believe the issue might be attributable though to creating a new user that is not listed as technical. The 401 unauthorized will appear since the password cannot be changed. Switch your web service user over to a technical user in the UME details, this also prevents the WS user's password from expiring.

[koehntopp]

" Invalid Response Code: (401) Unauthorized"

Wild guess: the password for your web service user has expired or is otherwise wrong.

Frank.