Risk anlaysis failed in CUP
Hi Everyone
I am trying to run risk analysis in CUP ( GRC AC 5.3) but I am getting the follwoing error
Risk analysis failed: Exception from the service : Invalid System
my connector works fine, and I have also changed the intial pasword for the websuer used in the Risk analysis tab in Configuration
Webuser have admin rights .
I guess I need have the same name for the connector as in RAR ... will try to chaneg and give it a try .
I mean the connector name in CUP and System Id for the connector in RAR should be the same right?
did anayone face simialr issue ?
any help would be appreacited .
Regards
PKK
Hi Harleen
I ceelted all the role attributes created all from scratch and editied the import file accordingly
we are on GRC aC 5.3 and SP level 7
belwo is log , might split into two
2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG NavigationEngine.java@85:execute() : Current Module: |CFG| Conversation: |cnvConfigImportRoles| Screen: |scrConfigImportRoles|
2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG NavigationEngine.java@105:execute() : Module#CFG#Conversation#cnvConfigImportRoles#Screen#scrConfigImportRoles#Action#saveConfigImportRoles#
2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG NavigationEngine.java@261:execute() : Handler found:class com.virsa.ae.configuration.actions.ImportRolesAction
2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG ImportRolesAction.java@56:execute() : INTO the method
2009-03-24 14:10:16,091 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@2752:getAELocaleCodeMapKeyAsLocaleId() : INTO the method
2009-03-24 14:10:16,091 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameCUSTOM_FIELD_NAME,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system High
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Low
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system High
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Low
2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system BE_MM
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system BE_MM
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Low
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system BE_SD
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system High
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system BE_SD
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,153 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system Meduim
2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR
Regards
PKK
Similar Messages
-
Hi,
We have same connector name in CUP and RAR but risk analysis failed and throws error "Risk analysis failed: ExceptionRisk Analysis failed"
have a look on detailed log as follows.
2012-01-03 17:54:54,044 [SAPEngine_Application_Thread[impl:3]_7] ERROR Ignoring exception : com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9923', Locale: 'en'
com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9923', Locale: 'en'
at com.virsa.ae.service.messaging.MessageFormatter.formatAsText(MessageFormatter.java:103)
at com.virsa.ae.commons.utils.JSValidationUtil.getMessage(JSValidationUtil.java:467)
at com.virsa.ae.commons.utils.JSValidationUtil.formatMessage(JSValidationUtil.java:523)
at com.virsa.ae.commons.utils.JSValidationUtil.formatMessage(JSValidationUtil.java:548)
at jsp_common_import_export1321962467821._jspService(jsp_common_import_export1321962467821.java:60)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
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.include(RequestDispatcherImpl.java:509)
at com.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.include(PageContextImpl.java:176)
at jsp_cfg_support1321962466399._jspService(jsp_cfg_support1321962466399.java:148)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
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
Thanks,
nayanaHi,
We have uploaded the latest xml files as per service pack still getting message risk analysis failed . Have a look on following log
and advice me.
2012-01-04 23:45:45,273 [SAPEngine_Application_Thread[impl:3]_32] ERROR com.virsa.ae.core.BOException: ExceptionRisk Analysis failed
com.virsa.ae.core.BOException: ExceptionRisk Analysis failed
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1167)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:381)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:118)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.virsa.ae.service.ServiceException: ExceptionRisk Analysis failed
at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:591)
at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
... 24 more
Thanks,
nayana -
Hello GRC Gurus,
SAP GRC AC CUP - 5.3
Support Pack - 07
When we perform risk analysis from CUP below mentioned error is coming
Risk analysis failed: Exception from the service : Risk Analysis failed
Please also find the System log as well
2010-05-11 15:32:13,067 [SAPEngine_Application_Thread[impl:3]_34] DEBUG com.virsa.ae.service.sap.RiskAnalysisWS53DAO : getViolations() : : into the method with userid : E66447, rolesToAdd : [Lcom.virsa.ae.service.sap.ws53.types.RoleToAddDTO;@48a4f072, rolesToDelete : [Lcom.virsa.ae.service.sap.ws53.types.RoleToDeleteDTO;@44a5f1a0, profilesToDelete : [Lcom.virsa.ae.service.sap.ws53.types.ProfileToDeleteDTO;@6a9a6295, mitigation : true, criticalAction : true, criticalRole : false, permissionDetail : false
2010-05-11 15:32:13,109 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisWS53DAO.java@166:getViolations() : riskAnaysisWS : [email protected]5ae0
2010-05-11 15:32:13,115 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisWS53DAO.java@170:getViolations() : webServicesURI : http://grcpdbci.mis.amat.com:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
2010-05-11 15:32:13,117 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisWS53DAO.java@175:getViolations() : username : virsaadm
2010-05-11 15:32:13,119 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisWS53DAO.java@183:getViolations() : setting socketTimeout to 900000 milli seconds
2010-05-11 15:32:13,121 [SAPEngine_Application_Thread[impl:3]_34] DEBUG AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
2010-05-11 15:32:13,123 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisWS53DAO.java@310:getViolations() : RiskAnalysis___ Calling excute Risk Analysis, Wait for the Results... (Note: Make sure that Compliance Calibrator background daemons are started)
2010-05-11 15:32:19,371 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisWS53DAO.java@312:getViolations() : RiskAnalysis___ Got the Risk Analysis Results
2010-05-11 15:32:19,373 [SAPEngine_Application_Thread[impl:3]_34] DEBUG RiskAnalysisBO.java@197:findViolations() : RiskAnalysis___ Failed with Exception : Exception from the service : Risk Analysis failed
2010-05-11 15:32:19,375 [SAPEngine_Application_Thread[impl:3]_34] DEBUG com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:582)
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.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java: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)
2010-05-11 15:32:19,378 [SAPEngine_Application_Thread[impl:3]_34] ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java: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.service.ServiceException: Exception from the service : Risk Analysis failed
at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:582)
at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
... 24 more
Please help me on this ASAP
Thanks,
JagatPlease also go throug this system log as well
2010-05-11 16:59:03,797 [SAPEngine_Application_Thread[impl:3]_50] ERROR Exception during EJB call, Ignoring and trying Webservice Call
com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : Exception in getting the results from the web service : Exception in initializing
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:522)
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.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java: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.service.ServiceException: Exception in getting the results from the web service : Exception in initializing
at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:309)
at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
... 28 more
Caused by: com.virsa.ae.service.ServiceException: Exception in initializing
at com.virsa.ae.service.sap.SystemDAOFactory.getCCRiskAnalysisEJBClient(SystemDAOFactory.java:1967)
at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:304)
... 29 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RiskAnalysis.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.virsa.ae.service -
Getting "Risk Analysis Failed " error while raising request from IDM
Hi friends,
Some of the User to Role mapping requests from IDM did not reach CUP (request ID = null) . When noticed the VDS log , we found the error from GRC webservice to be Risk Analysis Failed . We thought it might be an RAR issue , however , the request just got through CUP when submitted from GRC webservice directly . From RAR perspective also, everything looks ok .
Please provide your thoughts as to whether this error is pertaining to some other issue or suggest me what I can check in Identity center to correct this .
Thanks in advance for your help .The connector set up are all looking correct . However the requests are not getting raised in many cases .
At one point we identified that , since our SAP systems have been migrated to DB2, some of the systems were down .
So when the system is down we decided , Risk analysis is failing . however , now the systems are up and running and still the risk analysis is failing . -
Hi Experts,
We have upgraded our sandbox from GRC Access Controls v5.2 to version v5.3 SP7. I am now getting the following error when doing CUP Risk Analysis to RAR:
Risk analysis failed: Exception from the service : Risk Analysis failed
Any ideas?
The Connection Names are the same for CUP and RAR.
Here is the CUP log for the error:
2009-05-11 17:17:12,562 [SAPEngine_Application_Thread[impl:3]_36] ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(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.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:586)
at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
... 24 moreHello All,
I am having the same issue in CUP
EXCEPTION_FROM_THE_SERVICERisk Analysis failed
com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed.
The Password for the web service has not expired or the URI is the same as the CCRiskanalysis service and as well the connectors have the same name in RAR & CUP.
It worked till yesterday and stopped working suddenly. Any help is appreciated. -
CUP 5.3 (SP12) Risk Analysis Errors in CUP
Hello Experts,
When I run risk analysis in CUP for user provisioning. I get an error message:
Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.lang.Exception: Incorrect content-type found 'text/html'
Connector names are the same across all the components. We have a CUP test environment with SP11, and we did not have this kind of errors. I virtually tried everything I could.
If you can, please assist me.
HMHello HM,
I had this error when I first upgraded to SP12 but I don't know if it is a SP issue or not.
My CUP --> RAR SOD Analysis works for me on SP12.
You might try double checking the following:
1. Check all CUP configuration Web Service parameters in CUP --> Configuration --> 1) Risk Analysis & 2) Mitigation.
2. Check that you uploaded the latest UME roles that were delivered with SP12.
3. Check the UME user that is configured in CUP for risk analysis to make sure the password is still correct and that it has enough assigned roles.
4. Make sure you uploaded all the required XML configuration files to CUP --> Configuration --> Initial System Data. -
Risk analysis failed: Exception from the service : Invalid System
I'm trying to get the risk analysis performed for CUP requests. When I'm in the process of creating a request, and I add roles to the request and then click on the risk analysis button, I get the above error.
I checked the URI that I've included in the Risk Analysis section of the configuration and I believe it is correct:
http://<server>:<port>/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
I've selected 5.3 web service, and I have provided a user ID that has admin rights.
What do you think is the reason this error is being thrown?
The error in the log is:
2009-11-19 15:04:31,821 [SAPEngine_Application_Thread[impl:3]_39] ERROR com.virsa.ae.core.BOException: Exception from the service : Invalid System
com.virsa.ae.core.BOException: Exception from the service : Invalid System
Thanks,
SantoshFrank,
Thanks for your response. I was thinking along these lines already and so I have tried to do as you suggest. However it didn't work and the log indicated that it didn't like my connector name (even though the connector name is now the same as in RAR).
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SANDBOX' in the SLD. No such JCO destination is defined in the SLD.
However, I looked at one of the online post installation checklists for CUP and I gathered that it might be necessary to have the JCo itself renamed at the backend to reflect the name used in RAR, and that should populate into my connector list within CUP (when you click on the magnifying glass).
I'm waiting to try that out, but I'm not sure about any secondary impact of making a change to the JCo name.
Let me know what you think about that move.
Thanks,
Santosh -
Risk analysis failed: ExceptionInvalid System
Hi Gurus,
When I am doing risk analysis in CUP for work flow request I am getting following error"Risk analysis failed: ExceptionInvalid System"
And system log is as follows"
011-12-18 15:52:02,729 [SAPEngine_Application_Thread[impl:3]_2] ERROR
com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9940', Locale: 'en'
com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9940', Locale: 'en'
at com.virsa.ae.service.messaging.MessageFormatter.formatAsText
(MessageFormatter.java:103)
at com.virsa.ae.search.po.RequestHistoryPO.getDisplayString(RequestHistoryPO.java:112)
at jsp_show_audit_info1323336819278._jspService
(jsp_show_audit_info1323336819278.java:110)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
(JSPServlet.java:190)
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.include
(RequestDispatcherImpl.java:509)
at com.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.include
(PageContextImpl.java:163)
at jsp_request_review1323336807965._jspService(jsp_request_review1323336807965.java:703)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
(JSPServlet.java:190)
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.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.forward
(PageContextImpl.java:199)
at jsp_request_review_controller1323336806543._jspService
(jsp_request_review_controller1323336806543.java:18)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
(JSPServlet.java:190)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks,
NayanaHi,
Have you already checked this thread??
Error on calling RAR from CUP
Cheers,
Diego. -
Risk Analysis Failing in ERM 5.3
Hi All -
I would appreciate some assistance with pin-pointing an issue that I'm having with running Risk Analysis on roles in ERM. Currently I have RAR configured with the appropriate rule set and generating the expected risk/sod conflicts for users & roles. I have also added the appropriate Web Service Info. in th Misc section under the configuration tab (url, user, pwd) for all sections associate with RAR integration.
Now when I run a risk analysis on a particular role in RAR i get the correct conflicts however when I get the Risk Analysis stage with ERM I receive the following Error:
Risk analysis failed; Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID) VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
I also get this error when trying to run Mass Maintenance --> Risk Analysis:
Risk anaysis for role "XX:XXXXX" failed
Before I was getting error: "Risk Analysis performed successfully; No Risk Found" so I referenced SAP Note 1265964 and applied all solution steps.
Lastly here is the error log:
2010-01-14 14:59:28,768 [SAPEngine_Application_Thread[impl:3]_31] ERROR com.virsa.re.role.actions.RiskAnalysisAction
java.lang.Throwable: Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID) VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
at com.virsa.re.bo.impl.RiskAnalysisBO.saveObjViolations(RiskAnalysisBO.java:906)
at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:824)
at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:214)
at com.virsa.re.role.actions.RiskAnalysisAction.performRiskAnalysisOnMultipleRoles(RiskAnalysisAction.java:609)
at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
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.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
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)
Any help would be greatly appreciate it - Thanks in Advance!GOing to repost
-
Risk analysis failed; Risk Analysis failed
Hi,
Risk analysis failed in RE at object level but its working fine at transaction level, Any suggetion
ThanksHi,
Issue persist for only one solution rest all working fine, here is the log
-- Request dump for Action Path is scrLeftNav.linkConfigSysLog
2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG recordHistory:0::true#
2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG -- End Request dump for Action Path is scrLeftNav.linkConfigSysLog
2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG Current Module: |RE| Conversation: |cnvRole| Screen: |scrRiskAnalysis|
2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG Module#RE#Conversation#cnvRole#Screen#scrLeftNav#Action#linkConfigSysLog#
2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] ERROR Requested navigation control not found
java.lang.Throwable: Action not found - linkConfigSysLog
at com.virsa.framework.ScreenDefn.getActionDefn(ScreenDefn.java:62)
at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:125)
at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
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-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG Processing interrupted Caused by Redirecting to error recovery page
com.virsa.framework.InterruptProcessingException: Redirecting to error recovery page
at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:140)
at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
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-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG
-- Request dump for Action Path is scrTopNav.cfg
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG -- End Request dump for Action Path is scrTopNav.cfg
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Current Module: |RE| Conversation: |cnvRole| Screen: |scrRiskAnalysis|
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Module#RE#Conversation#cnvRole#Screen#scrTopNav#Action#cfg#
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Changing Screen: FROM: scrRiskAnalysis TO scrTopNav
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG com.virsa.framework.Context : clearScreenRep : : 4 entries cleared from screen repositiory
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Handler found:class com.virsa.re.actions.SuccessAction
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG forwarding to:CFG.cnvBusProc.scrBusProc.cfgSearchBusProc.do
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG
-- Request dump for Action Path is CFG.cnvBusProc.scrBusProc.cfgSearchBusProc
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG -- End Request dump for Action Path is CFG.cnvBusProc.scrBusProc.cfgSearchBusProc
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Current Module: |RE| Conversation: |cnvRole| Screen: |scrTopNav|
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Module#CFG#Conversation#cnvBusProc#Screen#scrBusProc#Action#cfgSearchBusProc#
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Changing Module: FROM: RE TO CFG
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG com.virsa.framework.Context : clearConversationRep : : 18 entries cleared from conversation repositiory
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG com.virsa.framework.Context : clearScreenRep : : 0 entries cleared from screen repositiory
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Handler found:class com.virsa.re.configuration.action.BusinessProcessAction
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG In LockedObjBO.deleteLockedObjBySession(String sessionID) starts.....
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG In LockedObjBO.deleteLockedObjBySession(String sessionID) ends.....
2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG forwarding to:/cfg_bus_proc_search.jsp -
Risk Analysis in a CUP request
Is there any way to run a Risk Analysis in a CUP request on different Rule Sets?
Letu2019s say you have 3 different Rule Sets like US - EU u2013 Global defined in RAR. Each one includes its own risks. In a CUP
request, it shows risks based on the u201CVirsaCCRiskAnalysisServiceu201D defined in your CUP config.
In our case we use the global Rule Set but the problem is for an EU request you can have US risks appearing that must be mitigated even if those risks are not relevant for EU.
It would be great if we could link the attributes Company or Functional Area directly to a specific rule set.
Please help/comment on this issue.
RegardsHi,
When we perform risk analysis on the request, ruleset for the risk analysis for CUP request is picked from RAR default values.
RAR-> Configuration-> Default Values-> Default rule set for risk analysis.
This rule set is picked by CUP to perform the risk analysis.
With the current design it is not possible to link the attributes Company or Functional Area directly to a specific rule set.
Kind Regards,
Srinivasan -
Hi experts!
I'm running risk analysis from AE... and after a while the result is this message: "Risk analysis failed: Exception from the service : Risk Analysis failed"
The connector IDs are the same and the web services configured is "http://server:port/VirsaCCRiskAnalysisService/Config1?wsdl&style=document"
Could any body help me please.I am getting the same error while running AE with AEApprover role.
ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
What could be the issue?
Thanks
Siri -
CUP : RISK ANALYSIS FAILED for Multi systems
Greetings,
Risk Analysis through CUP is failing on a request containing multi system access.
There are 2 systems requested on the same CUP request form. At the stage of Risk analysis is to be performed the risk analysis errors out as the risk analysis is performed on the entire request across both the systems, After the receiving the error when an individual system is selected the RA is performed with out any failure on both the systems independent of each other
I have check already check the below and they seem working fine without any issue
1. The admin passwords have been checked in both the systems (backend) as well as in the UME.
2. The risk analysis web service works as expected and there is no failure.
3. The connectors have the same name both in CUP & RAR no difference
4. SAPJCO connectors are appropriately setup in the SLD for both the systems and they work when tested out.
5. The URI is setup correct and no issue identified there.
6. Both the systems request have the same stage/path and the custom approver determination appropriately setup
When the approver tries to approve the request Risk analysis is setup as a mandatory task and when the RA is performed the system takes the default "ALL" and errors out, when you choose a specific system and perform you get the required results without any failure. Below is the java dump for the error.
Please let me know if I have missed anything?
Line: -
2011-03-09 10:16:11,264 [SAPEngine_Application_Thread[impl:3]_28] 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.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
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)
2011-03-09 10:16:11,278 [SAPEngine_Application_Thread[impl:3]_28] 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.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
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:
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)
... 28 more
2011-03-09 10:19:32,401 [SAPEngine_Application_Thread[impl:3]_28] ERROR com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
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.service.ServiceException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:587)
at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
... 24 more
Edited by: Angara Rao on Mar 9, 2011 5:15 PMGreetings,
Risk Analysis through CUP is failing on a request containing multi system access.
There are 2 systems requested on the same CUP request form. At the stage of Risk analysis is to be performed the risk analysis errors out as the risk analysis is performed on the entire request across both the systems, After the receiving the error when an individual system is selected the RA is performed with out any failure on both the systems independent of each other
I have check already check the below and they seem working fine without any issue
1. The admin passwords have been checked in both the systems (backend) as well as in the UME.
2. The risk analysis web service works as expected and there is no failure.
3. The connectors have the same name both in CUP & RAR no difference
4. SAPJCO connectors are appropriately setup in the SLD for both the systems and they work when tested out.
5. The URI is setup correct and no issue identified there.
6. Both the systems request have the same stage/path and the custom approver determination appropriately setup
When the approver tries to approve the request Risk analysis is setup as a mandatory task and when the RA is performed the system takes the default "ALL" and errors out, when you choose a specific system and perform you get the required results without any failure. Below is the java dump for the error.
Please let me know if I have missed anything?
Line: -
2011-03-09 10:16:11,264 [SAPEngine_Application_Thread[impl:3]_28] 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.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
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)
2011-03-09 10:16:11,278 [SAPEngine_Application_Thread[impl:3]_28] 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.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
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:
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)
... 28 more
2011-03-09 10:19:32,401 [SAPEngine_Application_Thread[impl:3]_28] ERROR com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
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.service.ServiceException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:587)
at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
... 24 more
Edited by: Angara Rao on Mar 9, 2011 5:15 PM -
Error in Provisioning Risk Update Request in CUP
Dear Experts,
I have configured all the required settings to configure Risk create/Update and change workflow in CUP.
I am even successfully generate the requests type Create Risk in CUP from RAR.But , not able to generate request type update risk from same path and recieving error provisioning request at stage -
Please provide any clue to resolve this issue.I am in SP12
Thanks,
MukeshPlease find..
I am trying to remove a function from the below risk ID in RAR.
getting this error when approving in CUP.
2011-04-19 09:15:29,943 [SAPEngine_Application_Thread[impl:3]_74] ERROR com.virsa.ae.accessrequests.bo.RequestExitServiceHelper : callExitService() : : Exception in calling the exit service, error code : -1, error message : ERROR: Risk: B001 has exceeded the maximum number of rules (46,655) that can be generated for a risk
2011-04-19 09:15:29,946 [SAPEngine_Application_Thread[impl:3]_74] DEBUG com.virsa.ae.accessrequests.bo.RequestBO : updateRolesForProvision() : : INTO the method for reqno : 1116
2011-04-19 09:15:29,946 [SAPEngine_Application_Thread[impl:3]_74] DEBUG com.virsa.ae.accessrequests.bo.RequestBO : updateRequestApplicationForProvisionStatus() : : INTO the method for reqno : 1116
2011-04-19 09:15:29,946 [SAPEngine_Application_Thread[impl:3]_74] DEBUG com.virsa.ae.accessrequests.bo.RequestBO : updateRequestApplicationForProvisionStatus() : : listApplicationDTOs : []
2011-04-19 09:15:29,946 [SAPEngine_Application_Thread[impl:3]_74] DEBUG com.virsa.ae.accessrequests.bo.RequestBO : insertRequestApplicationForProvisionStatus() : : INTO the method for reqno : 1116
2011-04-19 09:15:29,948 [SAPEngine_Application_Thread[impl:3]_74] ERROR Exception in calling the exit service, error code : -1, error message : ERROR: Risk: B001 has exceeded the maximum number of rules (46,655) that can be generated for a risk
com.virsa.ae.service.ServiceException: Exception in calling the exit service, error code : -1, error message : ERROR: Risk: B001 has exceeded the maximum number of rules (46,655) that can be generated for a risk
at com.virsa.ae.accessrequests.bo.RequestExitServiceHelper.callCCExitService(RequestExitServiceHelper.java:277)
Thanks,
Mukesh -
"Filter failed" in CUPS when using IPP (HP LaserJet 500 color M551)
I have two ArchLinux machines, one with HP LaserJet 500 color M551 connected over USB and another one on the same network. Printing over network (ipp) doesn't work: CUPS on the client says "Filter failed", so the job doesn't even reach the server. Printing directly from the server works perfectly fine, there's no "Filter failed" message and it just prints.
Both machines have the same ArchLinux installation, they are both x86_64, they have hpijs installed and the same PPD selected. This WiKi entry didn't help and the printer differs from the one discussed here, so it doesn't seem to be a well-known issue. :-(
I tried to reinstall the printer on the client many times, using both DNSSD and direct URI input. All this seems to work fine. The filter that fails is probably /usr/lib/cups/filter/hpps, but I have no idea how to get debugging info from it, i.e., why it fails etc. The same filter works just fine on the server.
I thought this might have something to do with the distinction between PostScript and the HP PCL variants. Enabling Adobe TBCP should fix this by adding the appropriate binary metadata and escaping things as needed... However, switching TBCP on in the CUPS printer settings stopped the printer from working. The printer appeared to be OK and responsive, but simply didn't print anything. Disabling TBCP fixed this on the server, but the client shows the "Filter failed" message, no matter what's happening on the server.I have similar problems with network printing (from various 32-bit and 64-bit Arch systems) producing 'Filter failed' messages, while directly printing from the CUPS server - with USB connection to the device - works as expected. My all-in-one device is an HP Photosmart C4480 and everything worked fine a few weeks ago. (Ironically, I can get network scanning using Xsane!) I've tried reinstalling, and various drivers to no avail.
It's very frustrating, and I think I've tried everything suggested in the Wiki.
Added later, after setting 'LogLevel debug' in cupsd.conf:
D [21/Aug/2013:22:19:57 +0100] [Job 18] Adding start banner page "none".
D [21/Aug/2013:22:19:57 +0100] [Job 18] Queued on "hpc4480" by "anonymous".
D [21/Aug/2013:22:19:57 +0100] [Job 18] File of type application/vnd.cups-raster queued by "anonymous".
D [21/Aug/2013:22:19:57 +0100] [Job 18] Adding end banner page "none".
D [21/Aug/2013:22:19:57 +0100] [Job 18] time-at-processing=1377119997
D [21/Aug/2013:22:19:57 +0100] [Job 18] 1 filters for job:
D [21/Aug/2013:22:19:57 +0100] [Job 18] hpcups (application/vnd.cups-raster to printer/hpc4480, cost 0)
D [21/Aug/2013:22:19:57 +0100] [Job 18] job-sheets=none,none
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[0]="hpc4480"
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[1]="18"
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[2]="anonymous"
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[3]="Test Page"
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[4]="1"
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[5]="job-uuid=urn:uuid:febcff1d-2cc5-3058-4c2f-c420e625e3ec job-originating-host-name=192.168.1.11 time-at-creation=1377119989 time-at-processing=1377119997"
D [21/Aug/2013:22:19:57 +0100] [Job 18] argv[6]="/var/spool/cups/d00018-001"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[0]="CUPS_CACHEDIR=/var/cache/cups"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[1]="CUPS_DATADIR=/usr/share/cups"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[2]="CUPS_DOCROOT=/usr/share/cups/doc"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[4]="CUPS_REQUESTROOT=/var/spool/cups"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[5]="CUPS_SERVERBIN=/usr/lib/cups"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[6]="CUPS_SERVERROOT=/etc/cups"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[7]="CUPS_STATEDIR=/run/cups"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[8]="HOME=/var/spool/cups/tmp"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[9]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/bin:/bin:/usr/bin"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[10]="[email protected]"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[11]="SOFTWARE=CUPS/1.6.3"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[12]="TMPDIR=/var/spool/cups/tmp"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[13]="USER=root"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[14]="CUPS_MAX_MESSAGE=2047"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[15]="CUPS_SERVER=/run/cups/cups.sock"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[16]="CUPS_ENCRYPTION=IfRequested"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[17]="IPP_PORT=631"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[18]="CHARSET=utf-8"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[19]="LANG=en_GB.UTF-8"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[20]="PPD=/etc/cups/ppd/hpc4480.ppd"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[21]="RIP_MAX_CACHE=128m"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[22]="CONTENT_TYPE=application/vnd.cups-raster"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[23]="DEVICE_URI=hp:/usb/Photosmart_C4400_series?serial=MY842FM2150557"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[24]="PRINTER_INFO=HP Photosmart C4480"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[25]="PRINTER_LOCATION=ninian"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[26]="PRINTER=hpc4480"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[27]="PRINTER_STATE_REASONS=none"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[28]="CUPS_FILETYPE=document"
D [21/Aug/2013:22:19:57 +0100] [Job 18] envp[29]="AUTH_I****"
D [21/Aug/2013:22:19:57 +0100] [Job 18] Started filter /usr/lib/cups/filter/hpcups (PID 8978)
D [21/Aug/2013:22:19:57 +0100] [Job 18] Started backend /usr/lib/cups/backend/hp (PID 8979)
D [21/Aug/2013:22:19:57 +0100] [Job 18] prnt/hpcups/HPCupsFilter.cpp 548: cupsRasterOpen failed, fd = 5
D [21/Aug/2013:22:19:57 +0100] [Job 18] PID 8978 (/usr/lib/cups/filter/hpcups) stopped with status 1.
D [21/Aug/2013:22:19:57 +0100] [Job 18] Hint: Try setting the LogLevel to "debug" to find out more.
D [21/Aug/2013:22:19:57 +0100] [Job 18] prnt/backend/hp.c 839: ERROR: null print job total=0
D [21/Aug/2013:22:19:57 +0100] [Job 18] PID 8979 (/usr/lib/cups/backend/hp) exited with no errors.
D [21/Aug/2013:22:19:57 +0100] [Job 18] End of messages
D [21/Aug/2013:22:19:57 +0100] [Job 18] printer-state=3(idle)
D [21/Aug/2013:22:19:57 +0100] [Job 18] printer-state-message="Filter failed"
D [21/Aug/2013:22:19:57 +0100] [Job 18] printer-state-reasons=none
Crucial error seems to be: prnt/hpcups/HPCupsFilter.cpp 548: cupsRasterOpen failed, fd = 5
Last edited by ninian (2013-08-21 21:28:58)
Maybe you are looking for
-
FF12 has "Improvements to "Find in Page" to center search result". How can I disable this centering?
FF12 came with new feature - centering of search result. This is rather annoying feature, when one searches for some small word or number on a bigger screen with at least 40-50 long lines of text, because it may be difficult to see the highlighted re
-
Attach .pdf exported from Pages
I have a very specific problem. I understand the reason that Pages files cannot be attached in an email, but even the .pdf's or .doc's that I export via Pages cannot be attached to my Hotmail account. They can be attached in my gmail, but I use my Ho
-
Table of Contents & Navigation
Hi, I note the Table of Contents allows navigation and navigation to completed slides only. Until my users have passed the assessment at the end of the course I want them to navigate only to those slides which they have read. The options in the TOC
-
New to LiveCycle - Submit Email problem
When I try to distribute a form LiveCycle wants to attach the form to my email. I'm using Yahoo mail. The LiveCycle attachment specifies the folder for the attachment but I've tracked it down to a hidden system folder. Is there a way to specify the f
-
I have a large number of documents that appear to have been scanned on grayscale. The background is white, but the text is gray and difficult to read. Is there an easy way to increase the contrast of the document in pdf form? So far, I have been able