GRC PC Background jobs

Hi,
I would like to know which all background jobs are required for GRC PC 10
We would like to schedule it through SM36. Do we also need to create variants for the same?
Regards,
Atul

Hello Abdul,
Please find the below background jobs which should be scheduled periodically.
RAR
1. User/Role/Profile sync incremental jobs.
2. Batch risk analysi for user/role/profile incremental
3. Critical action/role/profile incremental
4. Management jobs.
Also if your client uses the Alert you can schedule a periodically job for that.
ERM
If client is making lot of changes in TCODES and auth objects on daily basis then you can schedule these job as well.
1. Org value sync
2. Transaction/object/field sync
3. Activity value sync.
SPM
/virsa/zvfatbak (log report) on hourly basis
CUP
All the jobs given in CUP Configuration->background jobs should be scheduled on periodically basis as per your client requirent.
You can skip few jobs like HR trigger, SOD and UAR if your client is not using this fucntionality.
Regards,
Shweta

Similar Messages

  • Problem in Background Job Scheduling in GRC 5.3

    Dear All,
    I am configuring GRC RAR 5.3 SP11. While scheduling background jobs, only one job is running at a time. If I am scheduling Management report for one client of system (XYZCLNT300) and another job for User, Role and Profile synchronization- Full Sync for other client of the same system (XYZCLNT400).
    So, only one job is running at one time and other job remains in Ready state. I have done following Config in GRC System:
    1) GRC system has 2 server nodes.
    2) Each Server node has 3 background job workers and 5 web service workers.
    While Running 2 job at sametime, one is in Running status and other is in Ready Status. But that time only 2 background job workers are occupied one from each node while others are in IDLE state.
    I am wondering if I have free background job workers then why other job is in Ready Status. Is there nay parameter that needs to be changed to run multiple background jobs in parallel ?
    Please suggest.
    Thanks
    Sunny

    Hi,
    As per SAP Note 1371501 - Multiple Batch Risk Analysis at a time, we cannot run multiple batch risk analysis at a time.
    Batch Risk analysis will run only on server0 node.
    Thanks
    Sunny

  • Background job requirement  in Systems like GRC

    Hi All,
    We will like to know periodic background job requirements in systems like GRC. May be rough volume of these jobs (defination) will help.
    Do these systems have process chains like BI and APO systems.
    Also do these systems have some interfaces with ECC / R/3 systems to transfer the data. (for e.g. in APO we have CIF interface)
    Thanks a lot for all your help.
    Best Regards,
    Vithal

    Hi all,
    I think I have some commun issues with Vithalprasad about scheduling GRC Control Access background jobs (especially the FireFighter jobs) with an external scheduler (we are also using SAP CPS).
    I have to specify that for now we are using the internal job scheduler of GRC to schedule both ABAP and Java jobs which are dependant the one from the others.
    But we would like to schedule all of them in SAP CPS: it is possible for the ABAP programs, but not (?) for the Java jobs (we have not any NetWeaver Java Scheduler, since we have the 7.0 version of NetWeaver).
    Please feel free to ask me precisions.
    Have anyone an idea about the way to make this work ?
    Thanks for your help,
    Regards,
    Yi Jiang

  • GRC AC 5.3 - Sync Mode background job running for days.

    We have the following performance issues on the GRC System.
    1- Please note that the sync mode background job has been running for DAYS.
    My question is if I  truncate table virsa_cc_prmvl;  (which stores all the analysis results), will my GRC system be effected.
    2- Secondly we have a job analysing roles, which causes the performance to go down. And due to we have a extremely high number of roles, we would like to know if there would be a way to improve the analysis for roles. Is there any parameter modification in GRC / J2EE/ backend related to roles?
    Details of our roles:
    - we have more than 60000 roles in our system
    - 75 % of the roles are not assigned to any user (is there a way to avoid these roles? these roles are not put in order so too tedious to choose roles individually or by range.
    3- We are running a job with four risks and it's taking more than two minutes per user (we've got 10.000 + users in total)
    How can I resolve this performance issue.
    4- What is the recommended size of the batch for user sincronization. Should I use 1000 or 10,000 (based on our above environment).
    Thanks,
    Haleem

    Hello, Abdul!
    How you have solved a problem?
    Thank you a lot.
    Best regards,
    Denis Gaykov

  • GRC Access Control 5.3: Background Jobs in RAR don't start

    Hi experts,
    I defined background jobs in RAR (configuration -> background jobs -> schedule jobs) for initial loading. and there are 3 background tasks defined. Unfortunately the jobs are never executed (jobtype= immediately).
    Any help to execute the job would be appreciated.
    Kind regards,
    Max

    Hello Max,
    Here is what you should be checking :
    1) Check if the Background job daemon is running :
    URL - http://<server>: port/sap/CCBgStatus.jsp
    2) Check if the analysis daemon manager is running :
    URL - http://<server>:<port>/sap/CCADStatus.jsp
    3) Follow SAP Notes 999785 and 1176262 .
    This should help you resolve the issue
    Harleen
    SAP GRC RIG

  • SAP GRC AC 5.3 RAR Background jobs are cancelled

    Hi Experts,
    we have newly implemented theS AP GRC AC 5.3 RAR  Help me in troubleshooting the Background jobs cancellation in SAP GRC AC5.3 RAR.. we have reported this issue to customersupport they asked us to upgrade the front end  patch level to Sp15, even we upgraded still i have the same problem.. later we upgraded the backend patch  according to the SAP Note. still the problem is not resolved.
    Latest recommendation they are asking us to uninstall the SMD agent.. and also my java control.exe is showing yellow color
    help me how to resolve the issue.??
    Edited by: n.s.k mohan on May 10, 2011 6:21 AM

    Hi,
    Could you please first change RAR log settings to Java logger then take a restart of the system. After that log for your background will start coming in RAR. Then schedule the job if it fails then paste background job log here.
    Also, in future, please raise GRC related issue in GRC forum so that you can get more replies.
    Thanks
    Sunny

  • CUP not pulling through Risks, linked to background jobs? GRC 5.3

    Hi guys,
    I have an annoying problem in GRC CUP, I am trying to set up the "Create Request" function for our Company.
    When I create a request for either a New User, or Change a User's Roles, then perform the Risk Analysis on this, the result is "0 Risk(s) found". I have added every single role in order to test, which should produce a risk, but still the same message.
    I therefore thought OK, maybe the risks are not loaded into CUP, so I had a look in the configuration, namely the background jobs. The SOD Review and the UAR review jobs were not setup, so I scheduled them for every day, roughly every hour. However, this produces an error on the system log as follows:
    2009-11-03 08:54:17,505 [Thread-8394] ERROR Service call exception; nested exception is:
    *     java.net.MalformedURLException: no protocol: 103*
    java.rmi.RemoteException: Service call exception; nested exception is:
    *     java.net.MalformedURLException: no protocol: 103*
    *     at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:90)*
    *     at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:99)*
    *     at com.virsa.ae.sodreview.SODReviewUserHandler.insertUsers(SODReviewUserHandler.java:123)*
    *     at com.virsa.ae.sodreview.SODReviewUserHandler.execute(SODReviewUserHandler.java:59)*
    *     at com.virsa.ae.sodreview.SODReviewBGTask.execute(SODReviewBGTask.java:69)*
    *     at com.virsa.ae.backgroundjobs.BackgroundTask.run(BackgroundTask.java:51)*
    *     at java.util.TimerThread.mainLoop(Timer.java:461)*
    *     at java.util.TimerThread.run(Timer.java:408)*
    Caused by:
    java.net.MalformedURLException: no protocol: 103
    *     at java.net.URL.<init>(URL.java:568)*
    *     at java.net.URL.<init>(URL.java:465)*
    *     at java.net.URL.<init>(URL.java:414)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.createHTTPSocket(HTTPTransport.java:110)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:319)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)*
    *     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1433)*
    *     at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:83)*
    *     ... 7 more*
    Can anyone point me in the right direction as what could be the problem here?
    Very much appreciated!! Cheers

    Hi, OK, I have done as suggested, however the log is huge. I will paste some sections of the log relating to ther Risk Analysis. there's an error at the bottom relating to EJB?
    2009-11-03 14:32:10,364 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@531:logRequest() : role_action_PE1CLNT100!#!KEY!#!1480!#!KEY!#!CCF-S:BSCU_CUSTOMIZATION_DISP!#!KEY!#!0:0::ADD#
    2009-11-03 14:32:10,364 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@531:logRequest() : role_validto_PE1CLNT100!#!KEY!#!1481!#!KEY!#!CCF-S:BSCU_MAINT_NO_RANGES!#!KEY!#!0_display:0::12/31/9999#
    2009-11-03 14:32:10,400 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@85:execute() : Current Module: |AE| Conversation: |cnvCreateRequest| Screen: |scrRequestDetails|
    2009-11-03 14:32:10,401 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@105:execute() :  Module#AE#Conversation#cnvCreateRequest#Screen#scrRequestDetails#Action#loadSODAnalysis#
    2009-11-03 14:32:10,401 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@261:execute() : Handler found:class com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction
    2009-11-03 14:32:10,418 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RoleValidityHelper.java@157:isExpiredAsOfToday() : INTO the method : dt : Fri Dec 31 00:00:00 CET 9999
    2009-11-03 14:32:10,418 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RoleValidityHelper.java@167:isExpiredAsOfToday() : OUT of the method : boolResult : false
    2009-11-03 14:32:10,440 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@272:execute() : Target returned by execute action: success
    2009-11-03 14:32:10,441 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@452:service() : forwarding to:scrRiskAnalysis.load.do
    2009-11-03 14:32:10,441 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@515:logRequest() :
    2009-11-03 14:32:12,818 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RequestDetailsHelper.java@731:isRiskAnalysisEligible() : Prov Action is eligible for Risk Analysis : CHANGE_USER
    2009-11-03 14:32:12,818 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RequestDetailsHelper.java@739:isRiskAnalysisEligible() : OUT of the method : boolEligible : true
    2009-11-03 14:32:12,847 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@130:findViolations() : Starting Risk analysis.....
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@140:findViolations() : RiskAnalysis________ DAO level System : PE1CLNT100
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@141:findViolations() : RiskAnalysis________ Include Cross System : PE1CLNT100
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO   SystemDAOFactory.java@73:getRiskAnalysisDAO() : EN
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO   SystemDAOFactory.java@74:getRiskAnalysisDAO() : Locale ID is :1
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO   SystemDAOFactory.java@75:getRiskAnalysisDAO() : Locale date time format is :MM/dd/yyyy HH:MM:SS
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AECacheUtil.java@882:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  SAPConnectorUtils.java@600:getConnectorInformation() : INTO the method : connectorId :PE1CLNT100
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO  com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() :   : cc version : 5.3_WS
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO  com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() :   : risk analysis dao is set to RiskAnalysisWS52DAO
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO  com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() :   : cc uri : http://cvifxpsol.ks.franke.world:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  SystemDAOFactory.java@221:getRiskAnalysisDAO() : OUT of the method
    2009-11-03 14:32:12,857 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@158:findViolations() : RiskAnalysis________ Visible Roles : [com.virsa.ae.accessrequests.po.RolesPO@200f200f[system=PE1CLNT100,systemShortDesc=Production System PE1 - 100,accessType=Select,searchValue=,roleProfName=0,roleProfDispName=CCF-G_BC_BASIS_ADMIN,roleProfDesc=Competence Centre System Administrator,roleProfType=C,roleApproverId=NB014,roleApproverName=Ben Neesom(NB014),roleCriticalLevel=,reqPathId=,status=OPEN,oldStatus=OPEN,actionFlag=ADD,validFrom=11/03/2009,validTo=12/31/9999,selected=true,isReadOnly=false,isNew=true,expanded=true,isSimpleRole=false,isRiskAnalysisonAccessChanged=false,isEditable=true,isApplicable=false,altRoleApproverId=,detailDesc=,reaffirmPeriod=0,isLead=false,lastReaffirmDate=,funcArea=,roleIndex=0,companydesc=,fucntionalAreaDesc=,isExistingRole=false,roleProfIndicator=R,comments=,validityType=NO,actualDate=,years=0,months=0,days=0,URL=,customBAPI=,responsibilityId=0,commentsMandatory=No
    2009-11-03 14:32:14,401 [SAPEngine_Application_Thread[impl:3]_32] 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: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.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:425)
         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:455)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-11-03 14:32:14,402 [SAPEngine_Application_Thread[impl:3]_32] 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: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.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:425)
         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:455)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by:
    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
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisWS53DAO.java@632:determineRisks() : OUT of the method : com.virsa.ae.service.sap.dto.RiskWithCriticalActionsDTO@deb0deb[listRisks=[],listCriticalActions=[]]
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@190:findViolations() : RiskAnalysis___ Completd successfully!
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@221:findViolations() : RiskAnalysis________ Risk List Size : 0
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@225:findViolations() : RiskAnalysis________ Critical Actions Size : 0
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  RiskAnalysisBO.java@227:findViolations() : Done Risk analysis.
    2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] INFO   MessagingHelper.java@99:addMessage() : @@@Adding msgValue: Code: 2200; Locale: en
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] INFO   MessagingHelper.java@109:addMessage() : @@@Creating new message list
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] INFO   MessagingHelper.java@119:addMessage() : Adding msg to msglist
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  NavigationEngine.java@272:execute() : Target returned by execute action: success
    2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  AEFrameworkServlet.java@452:service() : forwarding to:/sod_analysis.jsp
    2009-11-03 14:32:15,519 [SAPEngine_Application_Thread[impl:3]_32] DEBUG  PopupCalendarTag.java@180:doStartTag() : Date Format in PopUpCalendar Java :- M/d/yyyy

  • Background job not invoking in CC.

    hi,
    I am facing a problem in running background job in CC. Actually its invoking a wrong url and when i am checking in application deployed url is different.
    We are at CC SP9.
    Url invoked is "is http://hostname:51700/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=/usr/sap/FAP/DVEBMGS17/j2ee/cluster/server1/.&threadId=4&daemonType=WS
    As per deployment
    Url should be "http://chmsxp41.eame.syngenta.org:51700/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart"
    Please suggest.
    Thanks & Regards,
    Pravin

    Please check SAP Note 999785.
    Somewhere between SP04 and SP06 the URL changed, and you need to re-configure that on database level (change "virsa/ccappcomp" to "sap.com/grc~ccappcomp").
    Frank.

  • Error while opening the file in Background job in Virsa.

    We are using Virsa 5.2
    I click on the result tab to view the job results.(informer->Background job) I am getting this message.
    Mar 3, 2008 1:49:15 PM com.virsa.cc.comp.GenericRAReportView wdDoModifyView
    WARNING: .\virsa\bgJobSpool\16.i (The system cannot find the file specified)java.io.FileNotFoundException: .\virsa\bgJobSpool\16.i (The system cannot find the file specified)
    Can you please let me know?
    Nothing has been changed including my user profile.
    From,
    PT.

    Hi,
    Here are number of notes that I have listed out to sort some issues on SAP GRC 5.2 .
    There is a note for background daemon issue as well
    Installation
    Note 1009509 - VIRSANH 5.2 Support Packages for BASIS 700
    Note 1022187 - Compliance Calibrator 5.2 Support Pack
    Post Installation
    Note 1022187 - Compliance Calibrator 5.2 Support Pack
    Note 1008500 - VIRSA 4.0 Support Packages for Basis 700
    Note 1060673 - Configuration of SAP Adapter in CC 5.2
    Note 709140 - Recommended JDK and VM Settings for the WebAS630/640/7.0
    Note 1044173 - Recomended Netweaver Setting for Access Control 5.x
    Note 1044174 - Recommendation for CC 5.x running on Oracle 10G Database
    Note 1121978 - Recommended settings to improve peformance in CC 5x analysis
    Note 978536 - Language Configuration for Virsa Compliance Calibrator 5.2
    Issues
    Note 1008500 - VIRSA 4.0 Support Packages for Basis 700
    Note 999785 - CC Background Daemon will not Start
    Note 987386 - Graphics Rendering Issue in SAP Compliance Calibrator
    Note 1009267 - System ID is not available in drop down menu-CC5.1
    Note 1052455 - Error-No relevant language message available in database
    Note 1062037 - java.lang.NullPointerException error in Adapter activation
    Note 1088378 - CC 5.2 - Undeployment of ccappcomp from SDM fails
    Thanks,
    Uday

  • What data is stored in the CC Background Job Spool File?

    What information is stored in the location referenced in the CC Configuration/Miscellaneous setting of 'Background Job Spool File Location'?  Our test and production versions of this system are configured the same, with both pointing to the same location on their respective servers.  However the test location shows a virsa/bgJobSpool folder in it containing multiple files while our production system shows this location as empty.
    Both versions seem to be working OK.  We are running backgrounds jobs in each (risk analysis, management reviews, rule generation, etc.) and seeing results.
    We updated to the GRC 5.2 a few months ago and are currently on SP9.  This issue came up during a system audit, so we need to come up with an explanation for the differences.
    Thanks.

    I had reviewed that SAP note previously, but it does not seem to help any with our situation.  We are running ad hoc background risk analysis jobs frequently and can always see the results.  Everything seems to work fine from the application side, we just don't see the logs where we thought they should be over on the server.
    From the outside, it looks like maybe it is ignoring the configuration setting and is still using the default location for the log.  Does it need to be on the same drive as the application?  I believe our application and the default location are both on our E drive, but we want to put the location for this and the Alert Log on the D drive.
    Thanks.

  • Has anyone put the RAR Background Job Spool on a different server?

    We are on GRC 5.3 SP 13.
    Has anyone put the RAR Background Job Spool File Location (assigned in the Miscellaneous configuration section) on a server different than the one that the GRC Frontend/Java system is on?
    I currently have it assigned to a folder on the GRC server, but it is running out of space.  I am having a problem getting the users to delete old reports as they say they need to keep them for internal Audit controls.  They are also resisting downloading the reports (more work for them).  I have been told that we cannot easily increase the file space on the GRC server (would basically have to purchase more storage and rebuild the server).
    I was thinking about moving the folder over to our virtual storage area, were file size can be more easily expanded.  I haven't found any documentation that says the folder has to be on the GRC server, but I also haven't seen any examples of where it has been put on a different server.
    Has anyone done this, and did you run into any problems?
    Thanks.

    Hello Bob,
    I got your point. Probably there's no recommendation about this, because the recomended practise is to delete or archive the spools as suggested in note : Note 1511027 - Periodic clean up of spool files
    If you have a requirement to keep these files "online", I think the option to save them to a network drive is fine. I haven't tried it for this specific scenario. You have to take into account:
    - Specific user to connect to FileServer
    - Availability of the FileServer. If the FS is down, the RAR job will cancel.
    - Performance. I mean, write to a local disk is not the same to write to a network drive. This point is very difficult to measure,   because it depends on a lot of things like network speed, server load, etc.
    Maybe someone has already implemented it and gives you more hints.
    Cheers,
    Diego.

  • Critical Roles & RAR Background Jobs Question

    Hello,
    I have the following queries, related to GRC AC 5.3 RAR.
    1- I would like to include all roles starting with S* into critical roles.
    My question is can I say S* in critical roles, OR do I have to manually enter each & every role starting with S* (Please note that currently we have around hundreds of roles starting with S and entering each of them manually is a tedious task).
    2- We have several background jobs scheduled in RAR and when I click search button, I get a list of around 600 jobs executed in the past few months.
    My question is can I purge the background jobs history in such a way that, when I click "SEARCH" button, I get only those background jobs, which have been executed in the past 1 week?
    Thanks,
    Haleem

    Hi Varun,
    I created message with SAP in the component GRC-SAC-SCC and below is the response.
    Dear Customer,
    You have to manually enter each & every role in critical roles section and the exclude objects in management report section.
    SAP GRC AC 5.3 SP11 does not support wildcard operations in critical roles/ profiles and exclude objects of management reports. We will support the wildcard in future SAP Versions of GRC.
    Thanks
    Based on the above message, I understand that I will have to enter all the roles manually for critical roles in critical roles section of RAR -> rule architect and exclude objects  of management report section.
    Thanks,
    Haleem

  • Error message while runing the Synch Job in Background job after Patch Upgd

    Friends
    We are 5.3 GRC CC on Windows 2003 and ECC 6.0  BI 7.0
    We just upgraded the patches to 12 for GRC CC and ran the Synch job in background....
    Eveytime we run the Synch job for Usre Roles and profiles or Batch Risk Analysis in Background, job finishes until 99 percent and then gives "Error" Message...
    Heres is the job history..:
    2010-09-26 13:14:25 Started Incremental Batch Risk Analysis 09262010 started :threadid: 0
    2010-09-26 13:18:06 Failed Error while executing the Job for Object(s) :PPORTELLA:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot i... (see log for details)
    2010-09-26 13:18:14 Failed Error while executing the Job for Object(s) :RCHAPMAN:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot in... (see log for details)
    2010-09-26 13:18:02 Failed Error while executing the Job for Object(s) :OJONES:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:19:21 Failed Error while executing the Job for Object(s) :YPATEL:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:49:42 Failed Error Job not completed
    Did anyone has the same issue after the patch upgrade ?
    Pranav
    The version info for the GRC CC..
    Version: AC-RAR 5.3_12.0
    Build ID: 05140510

    Hi I do get a error while scheduling Background job in RAR 5.3 , Please help me out...........waiting for your reply
    Apr 13, 2012 7:38:59 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:00 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:01 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:02 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:03 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:04 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:14 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:15 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?dae

  • Background Job sceduled is taking a lot of time

    Dear GRC Gurus,
    I have scheduled a Background job from the Compliance Calibrator which is connecting to the DEV R3 and it is a Full Synch for the User Synchronisation.
    The DEV has got 429 GB of data and the number of Users are about 20 Users.
    The job is showing <b>"RUNNING"</b> in the Compliance Calibrator for the last 2 days.
    In ST11 Tcode we can see some reports also being generated. I am not sure where we can see the log. Please advice how we can see the log and also whether the time this job is taking is normal or not.
    Expecting for a reply soon. Thanks in anticipation.
    Best Regards
    Somnath and Chakra

    Hello Guys,
    Somnath is asking about Netweaver background jobs and not your r/3 sm37 jobs.
    in CC51 GRC create their own SM36. Remember their is not SM36 type functionality in Netweaver.
    So these are WEBDYNPRO jobs that are running.
    Well Somnath, yes it do take some time when you do Full Sync for first time. Two days is normal. But subsequent Incremental jobs will not take any time.
    Please do check that you have applied latest support pack of CC 5.1. Tell me name of CAR file you unzipped using SAPCAR command. Does it contain string SP02 or SP03.
    It should contain SP03. Also tell me on which WAS is you NW installed.

  • Background jobs multiple servers

    we have multiple servers in the GRC environment.  When you schedule a background job, can you pick which server it will run on?  or is it always the server that you are logged into?

    Jack,
      Do you mean servers or server nodes? GRC AC does not allow you to pick server/server nodes. If it is server then it will run on the server where you are logged on and if it is server node, it would be picked automatically by the cluster.
    Regards,
    Alpesh

Maybe you are looking for

  • Is there a way to view what is running on the Q10?

    I know about closing apps open in the HUB, but is there a way to see what processes or programs are running on a Q10? I am watching one of our phones drain slowly just from sitting. Only thing running is our phone network. Maybe its syncing too often

  • Can I recover Windows 8 as second OS in dual boot?

    OK, here was the plan: I plan to dual boot IdeaPad Z500 by adding Windows 7 on top of Pre-Installed Win8. But seems like it's impossible to do so since I can't get the Win 7 Installer to start on UEFI mode, and I can't install Win 7 into GPT drive in

  • Sorting photos by keyword - $ value

    I recently moved my data from a PC to a Mac.  I've got a series of photos of collectibles that had tags (which have converted over to keywords).  Each photo has two tags - one for price (e.g. $1, $1.5, $2, etc.) and one tag for year offered (05, 06,

  • No Sound in YouTube Videos in FireFox

    I've been fighting Firefox for the last 6 weeks or so, trying to get it to play YT videos. First, it wouldn't play them at all, until I disabled Realplayer. Then, it played fine for almost 2 weeks, but then it stopped playing sound. All the videos ar

  • Third level Menu CSS?

    HI folks, I'm working on a third level menu and I need a CSS fix for this, and I'm not sure I understand why it is dropping down  instead of flying out... To see the menu in action, go here : http://bendannie2.businesscatalyst.com/Sale  and hover ove