SAP CUP - Error Submitting Request
Hi Experts
At my client , i am trying to implement GRC with CUP and RAR . Idea is to setup CUP where requests should be submitted to RAR for risk analysis automatically and if No risks then there is no need of any approval steps . If there are any violations then it should go through the approval process .
but at the moment , to start with, i have the simple work flow configured with single approval stage . The option for Risk analysis on submitting the request is turned on . with this config when i try to submit the request , i get the below Internal server error.
to go forward , i have switched of the risk analysis on request submission . i am able to create a request but at the approval stage ,when i login as the approver i can see the risk violations tab is green . i run the risk analysis , the flag turns red . when i try to approve i get the same error as below. I have pasted the log at the bottom . Can you please help me go forward at this stage . thanks .
500 Internal Server Error
SAP J2EE Engine/7.01
Application error occurred during request processing.
Details: java.lang.NoClassDefFoundError: com.virsa.cc.rulearchitect.dao.dto.RiskDTO (initialization failure)
Exception id: [002481E5092A006500060973000004CD00049385356E63ED]
CUP LOG:
2010-10-26 14:57:37,825 [SAPEngine_Application_Thread[impl:3]_18] ERROR Exception in retrieving the values from the database
com.virsa.ae.core.BOException: Exception while getting results
at com.virsa.ae.accessrequests.bo.RequestBO.getRequestDetails(RequestBO.java:5125)
at com.virsa.ae.accessrequests.bo.RequestBO.getRequestDetails(RequestBO.java:4503)
at com.virsa.ae.accessrequests.actions.RequestViewAction.loadRequestFromDB(RequestViewAction.java:530)
at com.virsa.ae.accessrequests.actions.RequestViewAction.pageLoad(RequestViewAction.java:424)
at com.virsa.ae.accessrequests.actions.RequestViewAction.execute(RequestViewAction.java:142)
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(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)
Caused by:
com.virsa.ae.core.BOException: Exception while getting results
at com.virsa.ae.accessrequests.bo.RequestBaseBO.getRequestBaseDetails(RequestBaseBO.java:633)
at com.virsa.ae.accessrequests.bo.RequestBO.getRequestDetails(RequestBO.java:4557)
... 25 more
Caused by:
com.virsa.ae.workflow.NoTransactionFoundException: Request is closed, no transactions available
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.getWorkFlowInfo(WorkFlowBOHelper.java:1759)
at com.virsa.ae.workflow.bo.WorkFlowBO.getWorkFlowInfo(WorkFlowBO.java:996)
at com.virsa.ae.accessrequests.bo.RequestBaseBO.getRequestBaseDetails(RequestBaseBO.java:204)
... 26 more
LOG continued :
2010-10-27 13:55:30,830 [SAPEngine_Application_Thread[impl:3]_14] ERROR java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
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:527)
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:3999)
at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:369)
at com.virsa.ae.ejbutil.submitrequest.RequestSubmissionBean.submitRequest(RequestSubmissionBean.java:692)
at com.virsa.ae.ejb.submitrequest.SubmitRequestEJBBean.getSubmitRequest(SubmitRequestEJBBean.java:45)
at com.virsa.ae.ejb.submitrequest.SubmitRequestEJBObjectImpl0_0.getSubmitRequest(SubmitRequestEJBObjectImpl0_0.java:119)
at com.virsa.ae.ejb.submitrequest.SubmitRequestEJB_Stub.getSubmitRequest(SubmitRequestEJB_Stub.java:57)
at sun.reflect.GeneratedMethodAccessor1278.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy165.getSubmitRequest(Unknown Source)
at sun.reflect.GeneratedMethodAccessor1277.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
2010-10-27 13:55:30,831 [SAPEngine_Application_Thread[impl:3]_14] ERROR Exception during EJB call, Ignoring and trying Webservice Call
com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
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:527)
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:3999)
at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:369)
at com.virsa.ae.ejbutil.submitrequest.RequestSubmissionBean.submitRequest(RequestSubmissionBean.java:692)
at com.virsa.ae.ejb.submitrequest.SubmitRequestEJBBean.getSubmitRequest(SubmitRequestEJBBean.java:45)
at com.virsa.ae.ejb.submitrequest.SubmitRequestEJBObjectImpl0_0.getSubmitRequest(SubmitRequestEJBObjectImpl0_0.java:119)
at com.virsa.ae.ejb.submitrequest.SubmitRequestEJB_Stub.getSubmitRequest(SubmitRequestEJB_Stub.java:57)
at sun.reflect.GeneratedMethodAccessor1278.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy165.getSubmitRequest(Unknown Source)
at sun.reflect.GeneratedMethodAccessor1277.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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)
Caused by:
java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
... 40 more
Similar Messages
-
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. -
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,
keerthiHI 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) -
Xmlspy Error submitting HTTP Request 400
Hi All,
Whe I try to open any XML file with XMLspy, for example BizPackageMETA.xml, I get the an error :
Sorry, but the file "http://localhost:8080/B1iXcellerator/exec/dummy//sim.com.sap.b1i.datasync.001/bp.Z.PRIELL/BizPackageMETA.xml" could not be opend!
Error Submitting HTTP request for "http://localhost:8080/B1iXcellerator/exec/dummy//sim.com.sap.b1i.datasync.001/bp.Z.PRIELL/BizPackageMETA.xml":400
I had enabled WebDav in xcellerator.cfg. Anything else I am missing ?Hi Hany,
I already had opened service calls at Altova and SAP regarding this issue. It is related to a small bug in B1i when responding to a PROPFIND request with an url path with trailing slash.
This bug should be fixed in the next B1i Patch.
Meanwhile you can use the following workarounds:
In older versions of XMLSpy you could just enter the path without trailing slash:
http://localhost:8080/B1iXcellerator/exec/dummy
Since the newer Version of XMLSpy automatically adds the trailing slash (which is the proper behaviour of a WebDAV client), you have to eleminate the additional slash in the resulting url path:
http://localhost:8080/B1iXcellerator/exec/dummy//sim.com.sap.b1i.datasync.001/bp.Z.PRIELL/BizPackageMETA.xml
=>
http://localhost:8080/B1iXcellerator/exec/dummy/sim.com.sap.b1i.datasync.001/bp.Z.PRIELL/BizPackageMETA.xml
The other way is to create a project with the external webfolder. Unfortunately XMLSpy adds the trailing slash also here. So you have to edit the created project file (.spp) afterwards to delete the trainling slash. Then it should look like this:
<?xml version="1.0" encoding="UTF-8"?>
<Project>
<ExtMountFolder FolderName="http://localhost:8080/B1iXcellerator/exec/dummy"/>
</Project>
Kind regards,
Marcus -
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 HannieGood 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 -
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 PoeschlHello 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 -
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 -
Error encountered during provisioning of user to SAP CUP in OIM 11g R1 BP07
We recently updated our environment from 11.1.1.5 BP05 to 11.1.1.5 BP07.
We are facing an issue with provisioning users to SAP CUP system. We receive an error specifying :
Response: oracle.iam.connectors.sap.cup.ws.submitreq.ObjectFactory
Response Description: Unknown response received
However, we are unable to find any errors related in the log file. The SAP UM connector version is 9.1.2.5. Please let us know the cause of this issue.1. Login to Design Console and open your GTC provisioning process definition , then Add a new task called "Notify Email".
2. Check Required for Completion, Allow Cancel and optionally Disable Manual Insert.
3. In the Integration tab, add tcCompleteTask
4. In the assignment tab, add an entry with the Default rule, target type of User, and for the User field pick an existing user with a valid email address in their User Profile.
5. In the Notification tab add an entry and check Assignee, (You can select User, Manager etc ) have the Status field set to C and for the Email field pick a Provisioning type of Notification Template that you have already created.
N.B: 7. Make sure the IT Resource and email configuration properly otherwise you will not get the mail.
Thanks
Tamim Khan -
Error submitting a support message to Solution Manager
I get an error when try to submitting a message to solution manager via portal. Can anyone explain why this error occur.
An exception occurred while processing a request for :
iView : pcd:portal_content/com.bc.SuperRoles/com.bc.role.solutionmanager/com.bc.rolefolder/com.bc.iview.solman
Component Name : com.sap.portal.epsolman.EPSolman
The exception was logged. Inform your system administrator..
Exception id: 12:56_22/03/05_0012
See the details for the exception ID in the log fileHi Ramesh. We are facing the same problems at a customer. Did you ever get an answer to your problem:
Error submitting a support message to Solution Manager
Posted: Mar 22, 2005 1:59 PM Reply E-mail this post
I get an error when try to submitting a message to solution manager via portal. Can anyone explain why this error occur.
An exception occurred while processing a request for :
iView : pcd:portal_content/com.bc.SuperRoles/com.bc.role.solutionmanager/com.bc.rolefolder/com.bc.iview.solman
Component Name : com.sap.portal.epsolman.EPSolman
The exception was logged. Inform your system administrator..
Exception id: 12:56_22/03/05_0012
See the details for the exception ID in the log file
Kind regards Thomas -
SP12: CUP: Error for requesttype "change" at auto-provisioning
Hello,
We have an error while auto-provisioning a change-request in CUP.
The request stages can be approved correctly but after the last stage, the request is rerouted to administrator because of escape-route settings. (auto provisioning failures)
So the audit trail reports an error at auto-provisioning, BUT in the backend-system the user was changed correctly.
If we now want to approve the request on admin-stage, the error appears again. So we have a closed loop reaction.
Any ideas?
Does anybody have the same issue?
Our client have the same problem with SP12 on the prod.system but in the dev.system (also SP12) we can create the request well.
Thanks,
Alexa2010-10-15 13:45:54,456 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@1794:getProvisioningStatusDTO() : OUT of the method
2010-10-15 13:45:54,458 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@1827:getProvisioningStatusDTO() : OUT of the method
2010-10-15 13:45:54,458 [SAPEngine_Application_Thread[impl:3]_32] DEBUG com.virsa.ae.accessrequests.bo.ProvisioningBO : autoProvision() : : listMessagesForSysType,list size=1
2010-10-15 13:45:54,459 [SAPEngine_Application_Thread[impl:3]_32] DEBUG com.virsa.ae.accessrequests.bo.ProvisioningBO : autoProvision() : : listMessagesForSysType #0# element:com.virsa.ae.configuration.po.ApplicationLogPO@31cf3f2[userId=GRC_20,emailId=<null>,reqNo=716,system=LS_DI6_300,recDate=10/15/2010,changedBy=AKOLB,logAction=USER CREATE,newValue=GRC_20,description=<null>,error=true,singleMessage=false]
2010-10-15 13:45:54,461 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@248:autoProvision() : Preparing Provision to SAP ... DONE
2010-10-15 13:45:54,463 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@277:autoProvision() : OUT of the method
2010-10-15 13:45:54,465 [SAPEngine_Application_Thread[impl:3]_32] WARN RequestBO.java@5924:autoProvisioningForApprove() : Exception occured during auto provisioning , error messages : [com.virsa.ae.configuration.po.ApplicationLogPO@31cf3f2[userId=GRC_20,emailId=<null>,reqNo=716,system=LS_DI6_300,recDate=10/15/2010,changedBy=AKOLB,logAction=USER CREATE,newValue=GRC_20,description=<null>,error=true,singleMessage=false]]
2010-10-15 13:45:54,469 [SAPEngine_Application_Thread[impl:3]_32] ERROR RequestBO.java@6665:approveRequest() : AutoProvisioning Exception, checking if the escape route is enabled
2010-10-15 13:45:54,478 [SAPEngine_Application_Thread[impl:3]_32] ERROR RequestBO.java@6681:approveRequest() : AutoProvisioning Exception, escape route is enabled, going for the escape route
2010-10-15 13:45:54,490 [SAPEngine_Application_Thread[impl:3]_32] DEBUG com.virsa.ae.accessrequests.bo.RequestBO : rerouteRequest() : AKOLB : INTO the method with toPathName : , poRequestDetails : com.virsa.ae.accessrequests.po.RequestDetailsPO@70e31b05[requestForOthers=false,userLookupEnabled=false,userIDFieldEnabled=false,userFirstNameFieldEnabled=false,userLastNameFieldEnabled=false,approverLookupEnabled=false,locationFieldEnabled=false,departmentFieldEnabled=false,emailFieldEnabled=false,telephoneFieldEnabled=false,companyFieldEnabled=false,employeeTypeFieldEnabled=false,managerTelephoneFieldEnabled=false,managerEmailFieldEnabled=false,managerNameFieldEnabled=false,requestorTelephoneFieldEnabled=false,requestorEmailFieldEnabled=false,requestorNameFieldEnabled=false,addRole=false,approveReject=,approveRejects=approveRejects,accessChanged=false,fileAttached=false,reqDataApplProvDTOs={com.virsa.ae.dao.dto.RequestDataApplicationProvisionDTO@46b5291a[reqNo=716,application=LS_DI6_300,provisionAction=ASSIGN_ROLES,userId=GRC_20,roleId=2,isProvisioned=true,isNew=false,LMD=<null>],com.virsa.ae.dao.dto.RequestDataApplicationProvisionDTO@1f9d8e3a[reqNo=716,application=LS_DI6_300,provisionAction=ASSIGN_ROLES,userId=GRC_20,roleId=3,isProvisioned=true,isNew=false,LMD=<null>],com.virsa.ae.dao.dto.RequestDataApplicationProvisionDTO@20e4920d[reqNo=716,application=LS_DI6_300,provisionAction=ASSIGN_ROLES,userId=GRC_20,roleId=4,isProvisioned=true,isNew=false,LMD=<null>]},accntValidationmsgs=[],connectionFailedSystems=,userExistSystems=,userNotExistSystems=,comm_method_type=,cstmFldName=,usersPOList=[com.virsa.ae.accessrequests.po.RequestUserPO -
KDE Printer Manager fails with "client-error-bad-request"
I'm having some trouble with printing on my system. The KDE printer manager shows "client-error-bad-request" and no other information. When I run the KCM from the command line, I also get "kcmshell(17286) KCupsRequest::serverError: status unrecognised: 1024" on the console. I wasn't able to find any useful information on this issue on google or these forums; not even what the 1024 status code means. It seems to me that this may be a bug in the kcm_printer_manager module, but I'd like to rule out other possibilities first. Unfortunately, I don't know what to try from here. I'll provide as much potentially relevant information as I can think of below.
Changes since last successful print job:
Multiple updates to KDE packages
Update to cups that changed systemd unit file names.
Stopped and disbled old units
daemon-reload
Enable and start new units
Other updates to cups since then, if I recall correctly.
Packages and versions:
kdeutils-print-manager 4.14.3-1 (owns kcm_printer_manager module for kcmshell4)
kdebase-runtime 4.14.3-1 (owns kcmshell4 binary)
cups 2.0.1-1
libcups 2.0.1-1
systemd 218-1
linux 3.17.6-1
Let me know if any other information might be helpful.Anyone please help.
Thanks,
Orton -
Error while printing (SAP spool error)
Hi,
I have configured a printer of type 'C : Direct Operating System Call'. On printing a page, an error occurs with the following log entries
SAP spool error log
=====================
Print request processing log
The host spool is reporting errors
Windows/NT error 1775: "A null context handle was passed from the client to the host during a remote procedure call."
Errors occurred processing this print request
Error during print request output. l_rc = 1
There may be no printout
Please. can someone help me out here.
Thanks!
Regards,
AngadOk I am upgrading from R/3 46C to ECC 6.0, on the 46c system the printers are configured as follow:
Device type HPLJ4 : HP Laserjet 4 series
Spool server sapprod1_PRD_00 sapprod1
Device class Standard printer
Host spool access method C: Direct operating system call
Host printer
srtroot03.startek.com\srt-dc-c4-sharp
Host name sapprod1
On the ECC 6.0 system the printers are configured as follows:
Device Type HPLJ4 : HP Laserjet 4 series
Spool Server srtsapeccdev1_DEV_00
Server Description
Host srtsapeccdev1
Device Class Standard printer
Host Spool Access Method C: Direct operating system call
Host printer
srtroot03.startek.co\srt-dc-c4-sharp
HostName srtsapeccdev1
The 46c system prints just fine, on the ECC 6.0 systems; I can not get the printers to work. I have made sure that the hosts file on the ECC server has the printer host address, and I get the following error back:
SAP spool error log
=====================
Print request processing log
The host spool is reporting errors
Windows/NT error 5 [
srtroot03.startek.com\srt-dc-c4-sharp]: "Access is denied."
Errors occurred processing this print request
Error during print request output. l_rc = 1
There may be no printout
The access to the Printer Host is wide open, what do I need to do to resolve this issue. -
Sap-plugin error when deploying a par file
Hi,
We are getting sap-plugin error when ever we are trying to deploy the application to the portal.Even after restarting the server the problem is not getting solved.
The application we are trying to deploy is perfectly alright as we tested the same earlier.
Can any one provide some inputs to solve this issue.
To add some more points
In brief ,we are not able to deploy our Portal applications . It is giving us error like this
NFO: Detected Portal Archive File: com.abc.par
INFO: Deployment failed - exception caught: Application upload failed: com.abc.par - more detail at: /usr/sap/POD/JC30/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.abc.par.log
We got this error many times , but after some time , when we restart the portal it works,
this time it is not working even after I restarted the server many timeshi all, i have same problem with upload of .par file, it doesn't work both from the portal and from the NWDS,
here i post first part of log file:
this is sap-plugin.log :
[16.05.07 / 13:05] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > Upload Response: <?xml version="1.0" encoding="utf-8"?>
<query-result><info><type>1</type><message>Detected Portal Archive File: test.par</message></info><info><type>1</type><message>Deployment failed - exception caught: Application upload failed: test.par - more detail at: C:\usr\sap\SWB\DVEBMGS02\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\test.par.log</message></info></query-result>
this is test.par.log :
2007-05-16_12-03-10
Application upload failed: test.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: test.par
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException
Cannot assign a zero-length byte array to host variable 18.
at com.sapportals.portal.pcd.pl.PlFactory.handleUnexpectedSQLError(PlFactory.java:2490)
at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:652)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildOnPersistence(XfsContext.java:1360)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1118)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1076)
at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:846)
at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:185)
at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:188)
at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:244)
at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:133)
at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:500)
at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:425)
at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:426)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:446)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:460)
at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1317)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:501)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:663)
at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:668)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.updateObject(ApplicationRepositoryService.java:717)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeApplication(ApplicationRepositoryService.java:389)
at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:306)
... 34 more
Caused by: com.sap.sql.log.OpenSQLException: Cannot assign a zero-length byte array to host variable 18.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
at com.sap.sql.jdbc.common.dispatch.BlobHostVariable.setBinaryStream(BlobHostVariable.java:143)
at com.sap.sql.jdbc.common.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:776)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setBinaryStream(PreparedStatementWrapper.java:401)
at com.sapportals.portal.pcd.pl.AttributeHeadersTable.storeAttribute(AttributeHeadersTable.java:431)
at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:248)
at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:541)
at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:616)
at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:640)
... 54 more -
JDBC receiver adapter - Error processing request in sax parser
Hello,
I want to INSERT idoc data via JDBC adapter into a MS SQL database. After digging through SAP Help, numerous blogs and forum discussions on SDN and even posting an OSS message I still get the same error:
'Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)'
When testing my mapping in the Integration Repository the resulting XML message is:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee xmlns:ns0="http://prodrive.nl/xi/HRMasterdata/HRMD_A_2_d_bcommerp">
<STATEMENT>
<T_PD_Employees action="INSERT">
<access>
<KeyTag>00088888</KeyTag>
<PerNo>00088888</PerNo>
</access>
</T_PD_Employees>
</STATEMENT>
</ns0:Employee>
The connection to the database is fine, Sender adapter with a SELECT * works perfect.
Can anyone help me solve this problem? I'm lost.
Best regards,
Roelof Jan BouwknegtHi Bhavesh,
I have tried out the change you suggested. Without success. Message I get back is
- 2006-12-28 10:34:08 CET: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
structure in testtool:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee xmlns:ns0="http://prodrive.nl/xi/HRMasterdata/HRMD_A_2_d_bcommerp">
<STATEMENT>
<T_PD_Employees action="INSERT">
<ACCESS>
<KEYTAG>00088888</KEYTAG>
<PERNO>00088888</PERNO>
</ACCESS>
</T_PD_Employees>
</STATEMENT>
</ns0:Employee>
Somehow the SAX parser doesn't like the result of my mapping. Maybe there is something wrong with the structure cardinality. Let me describe what I have built:
XSD:
WA_T_PD_Employees - Complex Type
> STATEMENT - Element - Occurence = 1
>> T_PD_Employees - Element - Occurence = 1
>>> STATEMENT - Attribute - Occurence = optional
>>> access - Element - Occurence = 1..Unbounded
Best regards Roelof Jan and thanks for your quick response -
Error processing request in sax parser
Hi all,
I am doing an asynchronous interface.
It is an interface from IDOC to JDBC. While testing the interface,am getting the following error
"Error processing request in sax parser: Error when executing statement for table/stored proc. 'put_delivery' (structure 'Statement_Delivery'): java.lang.NumberFormatException: null"
Any kind of help is appreciated.
Regards,
Thireesha.Hello,
Please refer to SAP NOTE 801367.
In advanced tab, use logSQLQuery-->true. Tt will display the actual sql statement in audit log instead of xml format.
You can copy this sql statement and execute directly in database to check the problem.
-Rahul
Maybe you are looking for
-
Old codec no longer works with update to 7.1.3
The previous version of Quicktime 7 worked fine with an older codec (Accom Affinity) but now this newest version of Quicktime does not. Is there a way to go back to the earlier version of Quicktime 7 without having to reinstall all the system softwar
-
Seeburger: keyStorage: import chain of certificates
Hi guys, Have any of you imported on VisualAdmin Key storage a certificate which has a chain of certificates associated? Why does this question pops up? Well, I'm using Seeburger AS2 Adapter and I'm trying to receive a message from my external partne
-
Interactive reports do not execute with Z business role
Hi all, We have created interactive reports which are working fine and displaying results with a standard business role. However, the report does not even execute when we use a custom business role - no blank screen no error, but the report does not
-
Since an "upgrade" is appears that both Mac & Windows users no longer get a "Pending wheel" when sending IM's to someone who is offline. (Windows Topic: http://community.skype.com/t5/Windows-desktop-client/No-pending-logo-for-IMS/m-p/2366625/highligh
-
Help! Troubles with updating Lightroom 3.2 to 3.6 in order to import RAW files.
I am trying to import RAW files into Lightroom 3 from my Nikon D7000. I read that I need to update my Lightroom, so I downloaded the 3.6 version. I restarted my computer and reopened Lightroom and it is still showing the 3.2 version. How do I get